I picked the first line from “Groovy kind of love” by Phil Collins as a title for this article because it all has to do with feeling blue. Today I attended a Microsoft TechNet Virtualization workshop. I was curious about the Hyper-V thing and thought let’s give it a try. I discovered that Microsoft still has a long way to go before they even can tip to the same features and stability as VMware has to offer. When I got home I installed Hyper-V on my client's lab and stored the Windows Server 2008 Hyper-V files in a CIFS/SMB file share just like Jose Barreto's describes in his TechNet article.
As explained in my previous blog post you can store your Windows Server 2008 Hyper-V files in a CIFS/SMB file share. This additional storage option can be used for the VM configuration, VHDs, snapshots and ISOs. That post explains the required permissions, describes in detail how to do it and also offers some performance tips.
Here is the video:
When I’m feeling blue from Eric Sloof NTPRO.NL on Vimeo.
I think it shows that Hyper-V isn't stable and that it's easy to break. Now CIFS is officially unsupported, but this was a recommendation on TechNet, and the point is not really about CIFS, it's about how easy it is to get it to blue screen.
Red Hat ditched them for good. Now they all but admit Xen is becoming little more a management tool for H-V.
If I'm going to play with dead tech, it should at least be fun like an old Atari.
2008 indicating that Microsoft does not support storing VHD files on
file shares.
The same is described here:
http://social.technet.microsoft.com/Forums/en-US/windowsserver2008r2virtualization/thread/2007eb67-191a-4576-813d-9ef6330e4b1a/
Although I'm not thrilled about Hyper-V, the discussion should remain fair.
Just think…what would happened if someone compromised your Windows Hyper-V host and wanted to bring it down. All they would need to do is create a VM on a CIFS. It would be that easy! I know I know there could be permission issues on the CIFS, but you see my point.
http://www.youtube.com/watch?v=XlLPmWwzHzM
Another BSOD from Hyper-V.