Yeah, most of us also went from dos->win31->linux... but some of us actually went back to Windows after Windows stopped sucking so damned much, and started being a reasonable multitasking/internet/memory protection platform. Oops, I just got myself burned at the stake, didn't I?
Anyway, Umm, I think Xen paravirtualization is, although maybe a lot of the techniques they use are no longer quite so relevant now that VT cpu's are mainstream, paravirt is still important because device drivers in general perform better when they are working via hypercall instead of some crappy emulated hardware interface.
I'm so lost.
Here, in the Programming room, when I see 'UML', I can only think of the Unified Modeling Language.
But, I think you guys are talking about the User Mode Linux.
KVM is an equally unfortunate choice of acronym. KVM= Keyboard, Video, Mouse (switch.)
biggest problem with virtualbox: if a VM is running, my laptop crashes instead of going to sleep.
ahh, they claim this is already fixed for the next major release.
When you guys typed 'KVM', I was actually thinking of Keyboard, Video, Mouse... figures I didn't quite get what you're talking about.
Nov 23 2008 11:02pm from Bryon Roche @uncnsrd
What if the hypercall is implemented with the same API as a hardware
interface? I like the way KVM goes with that..
A hypercall is not an emulated interface. A hypercall is a hypercall, and it requires fewer CPU cycles.
Ford, did you play with russian dolls as a kid? You did, didn't you?
you know? I forgot about those.
the ppc branch died with nt4 and was dug out again for the XBox2
(as did the mips & alpha branch)
xbox2 isn't WinCE?
don't think so, wince just has an arm port plus x86 afaik.
the mipsel port was dropped way back in 2k3
It was a PC that was connected to the server by an IOP. The Xseries system ran windoze, but on an actual intel proc.