Slashdot Mirror
Microsoft to Work with Xen on Virtualization
suso writes "Microsoft has released a statement to the press, saying that they are to work with Xensource on making Windows Server work with Xen through Microsoft's own hypervisor technology." Coverage available from Reuters as well. From that article: " As a result of the collaboration, the next version of Windows Server, code-named 'Longhorn,' will provide customers with a virtualisation system that promises to help run both Windows and Linux on the same machine more cost-effectively. Microsoft said it expects to conduct a public trial of Windows Server virtualisation by the end of this year and to release a commercial version of the software within 180 days of the date when Windows Server 'Longhorn' is released. Microsoft aims to release 'Longhorn' by the end of 2007, it said."
Faced with the threat of VMware, they'll cooperate with another underdog in the virtualization market, even if that underdog is a GPL hippie.
There will be plenty of time to finish off the hippie once VMware is contained, I'm sure they think to themselves.
Not only does this make M$ money due to the licensing charges, but it also gets its foot in the door in an otherwise Linux/UNIX shop.
There is no "I disagree" mod for a reason. Flamebait, Troll, and Overrated are not substitutes.
I don't really trust Microsoft's latest version of anything. Most people I know don't either.
I really prefer Windows Server 2000...and if I can't get that, then the next best thing is 2003. Longhorn is right out.
Then there's also the matter of Windows Genuine Spyware Disadvantage(TM), which you don't have installed on the old OSes.
If my option to run Xen is to buy the latest from Microsoft, I'd rather buy those Intel VT chips that will eventually be able to allow Xen to run Windows unmodified.
Mod me down and I will become more powerful than you can possibly imagine!
Will Windows run nicely under Xen (and also VMware)
That's what I want.
Microsoft plans to catch up with Linux when it comes to running a Xen host.
This will of course benefit Microsoft because without this, people who wanted to run both Linux and Windows on the same hardware using Xen had to use Linux as the host. (they also of course have to have hardware capable of full virtualisation)
Actually, this _may_ swing things in favour of running windows as the host because for older hardware Xen requires a modified guest. Running linux in Xen on windows allows this because xen modified linux is widely available. Microsoft in the other hand have not and probably will not release Xen-guest enabled windows, despite claiming to support interoperability. It's actually Microsoft style interoperability they want, and as many of us know that only works one way.
-- MartinG To mail me: echo kewyjlcxyzvjfxbqwh | tr bcefhjklqvwxyz
Why would I want to virtualize Linux under Microsoft Windows? The main benefit of linux is a stable kernel versus an unstable kernel (microsoft). I would rather virtualize Windows under Linux, not the other way around.
No longhorn is the codename for Vista. Blackcomb is the codename for Vienna (Vista server) if I remember correctly. The codename for Win95 was chicago, also if I remember correctly.
So MS realises that not all people will migrate from Linux to Windows. So should they offer a MS Linux?
Nah!
Instead they will offer a hypervisor. And make sure that most Linux distributions run fine under that. To help you make the decision to run Linux under a MS hypervisor, the hypervisor will offer better access to some hardware (wireless, modems, 3D graphics, DRM stuff, etc) that has no OS drivers.
Once people get used to running Linux under Windows, MS has a half victory. Now they can control how well Linux solutions run compared to running "natively on Windows".
*shudder*
)9TSS
It seems like the logical direction of Xen's progression.
d ex.html
From the creator of Xen's website "A port of Windows XP was developed for an earlier version of Xen, but is not available for release due to licence restrictions"
http://www.cl.cam.ac.uk/Research/SRG/netos/xen/in
The only thing standing in the way of Xen's running Microsoft's products is Microsoft.
This is interesting from the standpoint that Xen is a hypervisor. So what does exactly does "between Xen(TM)-enabled Linux and the new Microsoft® Windows® hypervisor technology-based Windows Server® virtualization". Does this mean that the Xen hypervisor will boot a MS hypervisor or am I missing something? Shouldn't MS strive to make Longhorn a proper Xen-aware guest O/S? Maybe this is just marketing speak, but it doesn't sound correct.
There's a pdf on the Xensource website with information on how to install Windows Server 2003 right now. You do need a VT enabled Intel or AMD-V system though:
xensource
Advertising Software
Wolf to work with sheep on dinner.
try { do() || do_not(); } catch (JediException err) { yoda(err); }
Nono... Its the other way around. The Linux community can now make the GNU/Linux kernel, with Xen technology, Hypervisor aware. This allows Windows to host Linux based platforms much easier.
Think of it in terms of getting the Xen folks to make sure that the next Linux kernel works 100% inside "VirtualPC 2007" by allowing them direct access to the Hypervisor subsystem of a Windows Longhorn machine.
The intention being that Windows Longhorn will host a Linux based server better than VMWare. This forces VMWares hand significantly. Its one thing to give away a product for free. This is a whole 'nother level.
Given Bill Gates is a poker lover, you could almost call this is a raise and a call.
Actually, it's the first thing I hear from them in a long time that seems to care about what the customer needs.
No, MS has always been good about listening to its customers; sometimes they are slower than customer like, but they do listen. People wouldn't stick with software that wasn't doing what they required of it.
I said it before and I'll obviously have to say it hundreds more, the OS wars are over.
Microsoft is a software bussiness. All they care about is that you have and are paying for their software.
People in the past could only run one OS at a time. Multibooting doesn't count. Even if you multibooted you were still running the same OS 95% of the time. Multibooting was an alternative to buying multiple machines. Now with virtualization microsoft no longer competes with any other operating system, be it Linux or Mac OS. They will all run side by side.
You ain't seen nothing yet, just wait until microsoft creates more windows versions and they each become more distinct such as (gasp!) windows server without a GUI interface.
All they need now is one application you can't live without to compel you buy the OS. In fact computer 'games' literally are right now the killer app for windows but I don't expect that to remain so for long. You'll probably need a seperate version of Media Center edition if you want to play DRM'd music and movies. Microsoft can now tailer make versions of windows bundled with their own software that will appeal to dozens of market segments. The one key advantage of virtualization is that they can give up on trying to keep windows so compatable in the future. Vista will in a sence be the last version of windows burdened by legacy compatability issues. It also means a quicker release schedule and more upgrade versions.
It's just a completely different game. Get your mind out of the past and wrap you mind around the future.
> Server 2k3 is far more advanced that 2000
Oh? In what way is 2k3 better than 2000 for server duties? Of course I'd ask how any competent admin can deploy either in an Internet facing role but that is one of those questions "That Must Not Be Asked(TM)" lest Microsoft strike you down. Thankfully I'm one of that 1% who are lucky enough to be operating in a 99% Microsoft Free environment so I can ask such questions with relative impunity. Of course the more correct formulation of the question is "How can an admin be considered 'competent' after deploying a Microsoft OS in an Internet facing environment considering their awful security track record."
> > Longhorn is right out.
> You haven't even seen it yet, and you're deciding against it?
It really isn't required to to see the final version, it will be a subset of the betas (expect more defeaturing before final RTM) and they are bad enough. There isn't anything there for an Enterprise IT shop to even consider a feature, so we can't even move to the part of the sales pitch where features can be sold as a benefit to the customer. Seriously, if Microsoft thinks Enterprise IT depts are going to forklift their entire existing workstation inventory for the dubious 'benefits' of Aero Glass they are stark raving insane. And as for servers, Eh? Tell me again why I want Shorthorn?
> > Then there's also the matter of Windows Genuine Spyware Disadvantage(TM), which you don't have installed on the old OSes.
> Funny, as you don't have to install it. It comes as a Automatic update, I uncheck the box to tell it not to install, then I check
> another box telling me not to bother me again. Haven't heard from it since.
And you also won't get updates. And next comes the part where you get 0wn3d. Then comes the suffering. And even that probably won't be an option with shorthorn, I really don't expect them to be giving you a choice in the matter unless you are a major corporate install and considering how widely Corporate XP was pirated they will probably be turning the screws there as much as they can get away with.
Democrat delenda est
> This is not the first time Microsoft has collaborated with Xen.
No, you were right in your next statements, Cambridge had an XP source license. Microsoft didn't 'collaborate' with Xen except in the sense AT&T 'collaborated' with UCB in creating BSD.
This is all about Microsoft coming to terms with the coming sea change of hardware virtualization. UP to now they could simply deny teh right to redistribute the updated device drivers and HAL bits to allow NT based kernels to run in Xen, problem solved. But now comes hardware that rewrites the equation. Before it was "Is it in Microsoft's interest to allow NT based kernels to run in Xen?" and the answer was no. But now it will be running in Xen whether Microsoft wants it to or not, but hardware virtualization is going to be slower than running a modified kernel. Linux already has such a modified kernel. So now the question is "Do we allow the benchmarks for XP and Shorthorn running in Xen to suck compared to Linux?"
> This is just Microsoft trying to ensure that Windows can run as Domain 0, ensuring that you need one more Windows license
> for something that NetBSD would do better.
Most certainly, as other posters have pointed out this initial effort is aimed at running Linux-Xen atop Windows, and takes great pains to make clear the opposite stacking order is not being considered. But they will, it is just taking them a bit of time to yield to reality. Corporate behemoths the size of Microsoft don't turn quicky unless BillG or The Embalmer does another "We are gonna fucking kill Netscape". (Yea I know I am mangling two different events for comedic value.)
Democrat delenda est
No, you're wrong. We have W2k3 running inside a Xen-enabled FC5 kernel. Try the instructions at http://www.xensource.com/files/xen_install_windows .pdf.
That's one of the major reasons why VT hardware support is so exciting.