Microsoft Hyper-V Leaves Linux Out In The Cold
whitehartstag writes to mention that Microsoft has announced their new Hyper-V as feature-complete. Unfortunately the list of supported systems is disappointingly short. "No offense to SUSE Enterprise Server crowd, but only providing SUSE support in Hyper-V is a huge mistake. By not supporting Red Hat, Fedora, CentOS, and BSD, Microsoft is telling us Hyper-V is a Microsoft only technology. More Mt. Redmond, Microsoft center of the universe thinking. That's disappointing. Sure, if you are a Microsoft only shop, Hyper-V will be an option for virtualization. But so will VMware and XenServer. But if you run a mixed shop, Hyper-V won't solve your problems alone — you'll have to also add VMware or Xen to your virtualized data center portfolio. Or just go with VMware and Xen and forego Hyper-V."
Are they only supporting SUSE E.S. as an ongoing policy? Or is it just the only one they've certified as of the first release?
Shouldn't any distribution based on a kernel build that doesn't require anything more or significantly different from the underlying hardware, relative to SUSE E.S. work just as well?
Bantam Dominique roosters crow a four-note song. Once you've heard it as "Happy BIRTHday" you can't NOT hear it that way
Microsoft can choose to support whichever companies that they want. AFAIK, only Novell has signed the Munich Agreement with Microsoft, so it makes sense for Microsoft to exclude the others. At a recent Launch event for Windows Workstation 2008, Visual Studio 2008 and SQL 2008, I saw only Novell was present (with a large booth) showing off Linux products and virtualized Windows environments. (Though it was funny listening to Steve B. try and pronounce SUSE.)
The Kai's Semi-Updated Website Thingy
Notice that these are supported systems. That doesn't mean that other OS's will not work.
Novell probably agreed to help Microsoft support Suse Enterprise. Redhat isn't playing nicley with Microsoft so Microsoft isn't going to play nice with Redhat.
Fedora? Not a chance. Fedora is cutting edge code. I have no idea why people use this for servers when there are better distros to use on a server.
CentOS? Well this is a better distro to use on server than Fedora but it is Redhat without the support and price tag.
Finally BSD? BSD is dieing..... Just kidding. I just don't think Microsoft feels that it is worth the time.
What I didn't see is if Solaris is on the list.
So buy VMWare or use Xen folks.
Really if you want to be a Microsoft shop and run Linux then you now have an option of a Microsoft blessed Linux. If you are not a "Microsoft" shop then you can use VMWare, Xen, or VirtuaBox and have a lot more options.
I guess on the bright side they are supporting a Linux distro. It could have been a Windows only vm system.
See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.
It also shows they're out of sync with the current server setups that people have. The number of Microsoft-only shops are dwindling, and they're purposely leaving themselves out of the mixed market.
Aren't they supposed to dominate a market before cutting off interoperability (like IE for mac)?
Why would you go to the trouble when other solutions just work? Trusting Microsoft to run Linux ... there is no propper analogy for such a stupid thing.
http://slashdot.org/comments.pl?sid=216934&cid=17629948
Stop letting off hot air on the dumbass article. See installing fedora core 8 on hyper-v . Even Ubuntu server is being used by people on HyperV. SUSE is supported in the sense of calling up MS's support desk and talking to them about it. But Linux distributions work just fine. This is just MS's way of telling people that they're on their own if they try other distributions(this is usually true for Linux servers anyway).
In the Microsoft world, "unsupported" means literally "we do not support this." i.e. "if you call us for support on this, we won't answer your question." There are a million things that Microsoft doesn't support, but still work perfectly-- Microsoft doesn't support typing in an IP address to Windows Remote Desktop Client, to use a particularly strange example I came across a few years ago, and yet it works fine and always has.
I don't know what Linux people think "unsupported" means, but they have the wrong idea whatever it is.
Comment of the year
While I agree with you that most of this is FUD, the fact that the other distros "work just fine" is irrelevant. "Not supported" means, to the enterprise world, not doable. Meaning, Microsoft VM ain't gonna happen in the big shops.
I think that there is a valid overall point to this submission, regardless of its hyperbole. It is that Microsoft's arrogance to think that they don't have to support other distros is exactly a fall back to their old ways. And this time, giving it away for free or making it a part of the Windows operating system isn't going to save Hyper-V like it did to save so many of their other products. For this fight of the hypervisor (essentially the new OS of the data center), VMWare has all the market share and lock in.
Sure, go ahead and choose Microsoft. The problem is that Microsoft has proven again and again that if you choose them, you can choose nothing else, ever. If you're fine with tying all your company's infrastructure to the whims of a convicted monopolist, feel free to do so, but sane people aren't ok with that. If Microsoft says your bug isn't important enough (if they even deem you worthy of acknowledgment), you are fucked, period. You can't switch to a competitor, you have too much invested in your infrastructure and if you have to change one thing, you get to change everything.
I'm not against having Microsoft as a choice. I just think people should realize WHAT they're choosing when they choose Microsoft, which is basically becoming their bitch and paying for the privilege.
My blog. Good stuff (when I remember to update it). Read it.
Sorry, but although the original article does exhibit some characteristics of an overblown rant, the main point is still valid. Most companies bigger than a mom-and-pop operation simply cannot use something that is "unsupported," regardless of whether it anecdotally "works just fine" or not.
If a user cannot call the Hyper-V tech support regarding an issue they are having running RHEL on Hyper-V and receive a proper response other than "we don't support that," then it is effectively useless and cannot form any part of that company's virtualization strategy. It may work just fine, but there are many companies with specific corporate policies prohibiting use of unsupported software, and in some cases, running into a serious problem with unsupported software can be seen as a violation of Sarbanes-Oxley and may be construed as negligence.
Whether it works OK or not with other linux distributions is irrelevant. Without real support, it's a non-starter for most businesses. That's not MS-bashing or Linux-fanboyism, it's just plain fiscal responsibility.