Xen High-Performance x86 Virtualization Released 316
The Xen team continues: "Xen requires guest operating systems to be ported to run over it. Crucially, only the kernel needs to be ported, and all user-level application binaries and libraries can run unmodified. We have a fully functional port of Linux 2.4.22 running over Xen, and regularly use it for running demanding applications like Apache, PostgreSQL and Mozilla. Any Linux distribution should run unmodified over the ported kernel. With assistance from Microsoft Research, we have a port of Windows XP to Xen nearly complete, and are planning a FreeBSD 4.8 port in the near future.
"Visit the project homepage to find out more, and download the project source code or the XenDemoCD, a bootable 'live iso' image that enables you to play with Xen/Linux 2.4 without needing to install it on your hard drive. The CD also contains full source code, build tools, and benchmarks. Our SOSP paper gives an overview of the design of Xen, and evaluates the performance against other virtualization techniques.
"Work on Xen is supported by UK EPSRC grant GR/S01894, Intel Research Cambridge, and Microsoft Research Cambridge via an Embedded XP IFP award."
Re:I bet it's not Open Source... (Score:5, Interesting)
They won't release the source for XP, but you can probably get a compiled binary. I just wonder if you'll have to re-register every time you change your virtual hardware.
MOL for x86? (Score:5, Interesting)
The biggest problem with emulators/virtualisation has always been speed. If a system can be set up that runs Linux but can boot XP easily and run fast, that will be a big improvement.
Of course it's not going to be much good for gamers (doesn't look like it can use hardware accelaration) but it's still pretty promising.
Re:Pfff (Score:5, Interesting)
"The Windows XP port is nearly finished. It's running user space applications and is generally in pretty good shape thanks to some hard work by the team over the summer. Of course, there are issues with releasing this code to others. We should be able to release the source and binaries to anyone that has signed the Microsoft academic
source license, which these days has very reasonable terms. We are in discussions with Microsoft about the possibility of being able to make binary releases to a larger user community. Obviously, there are issues with product activation in this environment which need to be
thought through."
It would be a bitch if it was ported, worked perfectly, but then nobody was able to use it.
The only thing I'm wondering... (Score:2, Interesting)
Re:Pfff (Score:4, Interesting)
No, VMware runs unmodified binaries.
What they do provide is ready made installations of various operating systems you can just install, although you have to pay for these (well, the MS ones at least).
Re:MOL for x86? (Score:1, Interesting)
Re:Pfff (Score:5, Interesting)
I'm surprised that this was possible at all with Windows XP. Microsoft's Shared Source program doesn't seem to be as useless as I thought.
Of course, there are issues with releasing this code to others. We should be able to release the source and binaries to anyone that has signed the Microsoft academic source license, which these days has very reasonable terms. We are in
discussions with Microsoft about the possibility of being able to make
binary releases to a larger user community.
I think there are two possibilities to do this. First, Microsoft incorporates the changes into their main trunk or releases patches for it. Second, Microsoft allowes a group of hackers to distribute modified Windows binaries. Both alternatives don't seem very probable.
User Mode Linux (Score:3, Interesting)
Re:Pfff (Score:3, Interesting)
Why Microsoft+Intel? NGSCB backward compatibility! (Score:5, Interesting)
As I have stated before about Microsoft's purchase of Connectix's Virtual Server technology [oreillynet.com]
The Electronic Frontier Foundation [eff.org] are about to publish a paper [com.com] criticizing a component of the "trusted computing" technology promoted by Microsoft, IBM and other technology companies, calling the feature a threat to computer users..Source code not available (Score:3, Interesting)
Re:Not really like VMWare (Score:3, Interesting)
I believe more information is needed on this before I make any decision as to whether it's better or worse than VMware.
GJC
Re:Nice jab at Mozilla! (Score:3, Interesting)
How many licenses per machine? (Score:5, Interesting)
If you only have a single computer with a single CPU, how many copies of WinXP do you need? That one is rhetorical of course, and the answer is One.
Can you run whatever software on that legitimately licensed WinXP machine that you like, assuming it was also legitimately licensed? That one is also rhetorical and the answer is Yes.
Now install VMware on that machine, WinXP as the host OS. By adding VMware you have not increased the number of CPUs or physical machines. If you created three virtual machines (if you had enough RAM and hard drive space, not a stretch at all) and wanted to run WinXP in each of those virtual machines simultaneously - do you need 1 license of WinXP or four licenses of WinXP (one for the host OS, and one for each VM)?
Granted the activation and active license management in XP may not allow this to happen even if in theory it should be allowed according to the 1 license / physical machine license in the EULA - but swap it with Windows 2000 or whatever
I am just curious.
NomadBIOS (Score:2, Interesting)
Re:Pfff (Score:5, Interesting)
Right. The OS'es we "support." Not the OS'es "we're able to run." And those "concessions" are mostly performance trade-offs, not correctness.
It's still true that some OS'es don't run; but that's because our software has bugs. OS'es sometimes have bugs, too, though if the OS is important enough, we'll work around it. The bugs that prevent you from running the OS that some drunken Swede cooked up for course credit are admittedly less important to fix than the bugs that, say, prevent you from running Linux. However, in the long run, we try to fix even the bugs exposed only by drunken Swedes.
That's why AtheOS, OpenStep, BeOS, NetBSD, FreeDOS, B-Right, Plan9, QNX, and myriad other commercially unimportant OS'es run ok. Not because they're important to our customers (man, oh man, they aren't), but because they enable us to be sure our x86 virtualization layer is reasonably correct. That way, when Ingo Molnar decides to start using 80286-style 16-bit tasks with lots of grow-down and conforming code segments to do system calls in Linux 2.6, we won't get caught out too badly.
Xenify, anyone? (Score:3, Interesting)
How extensive and how non-trivial are the necessary changes?