HowTo??? convert from Hyper-V VMs to ESX 4.0

[sgloeckle]

Hi, perhaps posted a million times BUT:

I still haven`t succeeded in converting any Hyper-V VM to ESX 4.

Guests (W2K3, W2K8, W2K8R2)

I`ve tried

- WinImage

- Starwind

- MS VMM

- Vmware coldclone converter

- Vmware online converter

and still: If attached VMDK-File to OS in ESX VM does not boot from VDISK or even knows that there is a filesystem.

What is it I`m doing wrong?

many thanks...

Stefan

[continuum]

I would help if you give details - does not work is not useful 😉




___________________________________

VMX-parameters- Workstation FAQ -[ MOA-liveCD|http://sanbarrow.com/moa241.html] - VM-Sickbay

[sgloeckle]

ok

problem is still that the converted system always ran into a bluescreen when migrated to a SCSI target device.

Even with the manupulation of the registry key vor HKLM\p2v it didn't work.

Process:

- Starwind V2V: vhd -> vmdk for ESX

- vSphere 4: created VM without virtual disk for W2K8R2 OS type

- Uploaded vmdk-file to ESX and attached to VM

- booted VM from W2K8R2-CD-ISO file and started repair option

- loaded hive, changed key settings, unloaded hive and restarted system from virtual harddisk

-> bluescreen

[continuum]

what scsi0.virtualDev do you use ?

Does the key you edited match that ?

what type of BSOD do you get ?




___________________________________

VMX-parameters- Workstation FAQ -[ MOA-liveCD|http://sanbarrow.com/moa241.html] - VM-Sickbay

[sgloeckle]

hi continuum,

ok, I messed it up !!

changed the wrong registry all the time .... ouch!

now it works fine

thanks for reminding me of my lack of professionality

cheers, Stefan

[continuum]

good - then I can take it that my instructions basically work ?

please mark the question as answered then

Ulli




___________________________________

VMX-parameters- Workstation FAQ -[ MOA-liveCD|http://sanbarrow.com/moa241.html] - VM-Sickbay

[sgloeckle]

thx to all for helping

this has done the trick in the end:

http://sanbarrow.com/p2v2008r2.html

cheers, Stefan

[continuum]

more details ? - on what aspects.

Please tell me where it was unclear so I can improve it




___________________________________

VMX-parameters- Workstation FAQ -[ MOA-liveCD|http://sanbarrow.com/moa241.html] - VM-Sickbay

[sgloeckle]

I belive

- that I hat some trouble translating your instructions w/o useful pictures

- that I had missread some fractions of you instructions in the hurry

so it's not your fault

but

- you should update/correct the part with the windows 7 CD which did not work in my environment but W2K8R2 CD did (or should I have used th 64-bit version of W7?)

thanks a lot

Stefan

[continuum]

I used the Win7 64bit version - I used that one because I found a free download for it.

If I knew one for the 2008 R2 rescue CD I would have used that one.

But you sure need a 64bit CD to handle a 64bit guest




___________________________________

VMX-parameters- Workstation FAQ -[ MOA-liveCD|http://sanbarrow.com/moa241.html] - VM-Sickbay

[golddiggie]

How would you go about converting a Server 2008 R2 VM running on Hyper-V into something that ESX/ESXi 4 can handle? We have one last VM that we need to pull away from hyper-v and get it onto our ESX hosts.

If we cannot get a conversion to work properly, then I'll just create a new virtual server, on ESX, install the software (Act2010) and then move the database over to the new server and let it live in happiness.

Network Administrator

VMware VCP4

Consider awarding points for "helpful" and/or "correct" answers.

[MLC56]

I've been trying the http://sanbarrow.com/p2v2008r2.html procedure and failing. When I get to the stage of editing the hive I get "Cannot load d:\windows\system32\config\SYSTEM: Error while loading hive" message. (D: is the virtual disk for the W2K8R2 server). This is the correct hive to edit isn't it?

[vlho]

Hi all,

try new version VMware Converter Standalone 4.3

http://downloads.vmware.com/d/info/datacenter_downloads/vmware_vcenter_converter_standalone/4_0

[brhunt]

Continuum,

I am trying to follow the manual procedure for a Vista 32 bit VM running on Hyper-v R2, going to an ESXi4.1 server.

I used the Starwind converter on a cold VM.

I created a VM via vSphere Client and pointed it to the VMDK.

I booted up to a Vista installation ISO and followed the steps below:

On the target platform boot the newly created VM into the Windows Vista, selected repair.

After boot is finished click on the CMD-button and run regedit.

Select HKLM and then Menu > File > Load Hive.

Browse to the Windows-directory on the virtualdisk > system32\config and select the file SYSTEM.

When asked for a name enter p2v.

Then find the key

HKLM\p2v\ControlSet001\services\LSI_SAS

and set the start type to REG_DWORD 0
Then select HKLM\p2v and click Menu > File > Unload Hive.
You can close regedit now and restart.

On restart, I still get the 7B BSOD.

One note about the registry changes: In the LSI-SAS key, there was a 'start' dword and a 'type' dword.  The start dword was 0, the type dword was 1.  I was a little confused about the 'set the start type' statement in the instructions, but since the type was set to 1, I assumed that was the one you meant.

Any other ideas for me to try?

Thanks.

Bryan Hunt

[continuum]

that procedure only works if you also assign lsi-SAS controller to the VM - did you do that ?

[brhunt]

Yes, it was set to that.

Odd thing, after the 7B, I let the automatic repair run.  It said that it couldn't repair the disk.

Then I went back to the recovery console and ran regedit again.  Now the values were start=4 and type=1.  I left type alone and set start=0, rebooted and voila, it booted cleanly!!

Not sure why, but it seems as if the automatic repair actually did do something, then your methodology worked perfectly.

Thanks for the tip on repairing the 7B errors, I'm sure that it is not the last I'll see in this process.

Bryan Hunt

[continuum]

did you edit the system hive of the recovery cd first time ?

the hive to edit is in C: or 😧 - not in X:

[brhunt]

No, I was very careful there, as I saw an earlier post where the guy had edited the hive of the boot OS, not the VM OS.

[continuum]

then maybe it is different in Vista - I only  used this myself against win7 and 2008

maybe for Vista we should use the normal LSI ?

I would like to see the export of HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001
of that machine - not sure if Vista has LSI-SAS listed in the critical device database ?