Been migrating from Vmware to Hyper-V after my server crash. I was pretty damn impressed with Hyper-V. It’s extremely fast and easy to manage. It’s a great hypervisor, with the only draw back being the base OS taking just under 1GB of RAM. But that’s what you pay for to get a highly versatile virtualisation OS that will install onto any hardware.
Just a tip for those migrating from VMware to Hyper-V. It’s highly documented on the net that VMware uses SCSI hard drives to boot off (as this is what VMware suggests). Hyper-V only boots off IDE (even Hyper-V in 2008 R2).
To not get a STOP 0x0000007b BSOD error, you have to add a IDE hard drive into the virtual machine whilst it’s still running in VMware. Make sure you choose IDE Channel 1:0 or 1:1 as this installs the Primary IDE Channel. You probably already have a Secondary IDE Channel from the CDROM drive.
Last but not least, for me anyway I had to go to Computer Management and initialise the newly created IDE Hard Drive in VMware. I found that if I didn’t do this I’d end up with a BSOD in Hyper-V after the migration.
To summarise the steps in full (it’s been done a million times on the net already – but this is for those who want a one stop shop)
- Uninstall VMware tools
- Shutdown virtual machine whilst it’s still in VMware
- Install an IDE hard drive on channel 1:0 or 1:1
- Startup the virtual machine
- Initialise the disk in Computer Management
- Shutdown virtual machine
- Convert from vmdk to vhd using the tool of your choice (I had most success with VDMKtoVHD from http://vmtoolkit.com/)
- Mount the image into Hyper-V
- Using the Legacy Network Card will allow the network to work without drivers but restricts you to 10/100.
- Otherwise, use the standard Network Card but make sure you install the Integration Services (requires SP2 or higher if you’re running Windows 2003 Server)
- You’ll probably get Service Failed to Start errors, so you’ll have to check in Event Viewer and teeth through those issues. Nothing is perfect right? Just keep in mind that it may be caused by some of the VMware Services still installed on the system (check in Service.msc). For some reason, the VMware Tools uninstall does not get rid of them all.