here is a nice example that demostrates how easy it is to convert Hyper V VMs to VMware
download demo Hyper V VM here : convert the VHD with Starwind V2V converter to a vmdk
create a new VM as 2k8 64bit and add the converted vmdk to a LSI-SAS controller
boot into a win7 64 bit rescue CD and load the system hive of the 2k8 - set the startup type for the LSI-sas driver to 0 - it is 4 right now
without the last step you would get a 7B BSOD on first boot ...
thats it - now you can boot the VM ...
takes about 30 minutes for the V2V converter and 3 minutes with the win7 boot CD
super easy - no VMware Converter required at all ...
thanks for your tipps, but I didn't suceed - when I load the hive the LSI_SAS start key is already set to 0 and the type key is set to 1 - so the vm machine starts always with a blue screen - Do you have any hint for me ... would be a great help
BTW I'tried it with the IW RTM demo
sure that you loaded the correct hive ?
in the VM I tried start was set to 4
post screenshot of regedit please
I'm wondering if I understand what you guys are saying -- I'm a bit new at this:
1. Do you back up the registry of the IW RTM first, in order to get the system hive to restore? I don't have a running IW RTM yet, I just downloaded the one from msft site. Where do you get the system hive that you're going to restore?
2. What does it mean to "add the converted vmdk to a LSI-SAS controller"? I converted the image as you say to, using the Starwind V2V, and now I'm sloooowly importing it into my ESXi datastore. Am I on the right track?
This is my second try -- the first time, after I imported the image and created a Win2K8 machine in ESXi, it looked like it was going to boot up, but then BSOD. And the BSOD happens so quickly that I can't tell what the problem is! I was able to bring up some sort of little Windows 2008 Server command prompt though, which I guess is where the rescue operation (restoring the hive, etc) can take place -- is that correct?
Sorry to be so lost -- Thanks for your help!
if the bsod is flashing up to fast - boot the VM into a 2008 recovery CD and then disable automatic reboot after a crash.
The entry - like in all other Windows is here
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CrashControl where there should be a subkey named autoreboot
0 means = no auto reboot
1 = means teh system will automatically reboot after a crash - leaving you no time to see the BSOD error message.
Do you know the procedure to load a hive ?
Read my notes http://sanbarrow.com/p2v2008r2.html
OK, now we're cookin
I wasn't understanding the fundamentals of editing a registry hive - I read up about Load and Unload hive, and then went and followed your patching instructions.
I didn't use the system restore boot disk, because when Windows Server 2008 R2 has a BSOD at startup, it offers a "Launch Startup Repair" in addition to "Start Windows Normally" -- and in that startup repair environment, you can run REGEDIT.
I (stupidly) did the registry patches on the SYSTEM hive of the startup system several times, before realizing that I should go to the c: drive and load the hive from Windows\System32\config THERE, instead of the one on the startup repair boot drive (duuh)
Thanks again for these great instructions!