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

[J1mbo]

With the Hyper-V VM running, using vmware converter to "P2V" it to the ESX host.

Please award points to any useful answer.

[sgloeckle]

Hi J1mbo,

thx, but how exactly?

online or offline, which version of converter, cause I belive to have tryied this already

Stefan

[J1mbo]

Have both your Hyper-V and ESX hosts running. Start the VM you want to convert and let it boot.

Next install vmware converter standalone edition version 4 to another PC.

Select the Hyper-V VM as the source, enter the credentials.

Select vmware infrastructure as the destination, enter ESX server's IP and username/password.

Then start the process. Once it's done shutdown the VM running on Hyper-V and start it on ESX.

Please award points to any useful answer.

[Borja_Mari]

Hi,

to convert successfuly from a hyper-v vm to a vmware esx 4.0 the easy way is install the vmware converter 4.0 in a third windows machine. Then configure the migration task configuring the source as a power on machine (the source IP and user/password with administration rights in that system) and the destination as Virtual Infraestructure virtual machine. It should work without any problem.

Anyway, i would recommend you using the best practices in vmware conventer to eliminate o minimize the possible migration issues.

Hope this helps you

Regards/Saludos,
Pablo

Please consider awarding

any helpful answer. Thanks!! -

Por favor considera premiar

las respuestas útiles. ¡¡Muchas gracias!!

[sgloeckle]

Hi,

just tried again with W2K8R2: could'nt install the agent remotely. When installed locally and started converting locally I got this error:

FAILED: Unable to create a VSS snapshot of the source volume(s). Error code:

2147754754 (0x80042302).

stefan

[RParker]

ALL of those products you mentioned most likely are converting them as VM Ware 1.x/2.x version vmdk. ESX is slightly different, and you can't bring them up directly on ESX. So you have to FIRST create them as stand alone VM's, point VM Converter at them THEN use VM Converter to transfer / convert to ESX.

OR you can boot the images on Hyper-V and point VM converter to their individual IP address, and treat them as if they were physical machines.

[RParker]

Convert the *.vhd as a vmdk using Winimage.

Install VM Ware server (if not already).

Create a NEW VM Server VM (standalone) and use existing drive created with Winmage.

Doesn't matter the parameters or the name, you can change it later.

Then use VM Converter to convert that VM Server image to ESX. The problem is the file is not compatible with ESX. I have used this on Winimage, never had a problem. Its 2 steps, but at least it works.

[Borja_Mari]

Hi,

convert W2K8R2 maybe doesn't work because isn't officially supported by vmware converter 4.01.

But converting W2K8 and W2K3 should work. Try it.

If this 2 conversions work (i personally prefer install converter in a third machine, not in the source machine to convert) then we will think how V2V the W2K8R2 system

Regards/Saludos,
Pablo

Please consider awarding

any helpful answer. Thanks!! -

Por favor considera premiar

las respuestas útiles. ¡¡Muchas gracias!!

Virtually noob blog

[continuum · Accepted solution]

V2V of 2008 R2 from HyperV to VMware is pretty easy - you do not even need VMware Converter ...

read my notes here

http://sanbarrow.com/p2v2008r2.html




___________________________________

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

[Borja_Mari]

Hi continuum,

you're always making excellent annotations. Thank you very much! (again)

And i remember what you told me some time ago, people that uses self-made P2V converter CD's plays in a higher league

Regards/Saludos,

Pablo

Please consider awarding any helpful answer. Thanks!! - Por favor considera premiar las respuestas útiles. ¡¡Muchas gracias!!

Virtually noob blog

[continuum]

for Hyper V to VMware you do not need to create a coldclone CD yourself.

You only need Starwind V2V Converter plus a Windows 7 rescue CD for a Coldclone - or

Sysinternals Disk2VHD plus Starwind V2V converter plus a Windows 7 rescue CD for a Hotclone




___________________________________

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

[sgloeckle]

Hi continuum,

I've already tried the method Starwind V2V + Windows 7 rescue disk (which does not work, but W2K8R2 does) and done the sanbarrow.com/p2v2008r2.html patching.

I still get a bluescreen!

I'll try the VM-Server method next.

many thanks,

Stefan

[continuum]

Hi Stefan

can you explain what you have done exactly ?

Ulli




___________________________________

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

[VMXTROOPER]

The solution that I use is very easy and doesn't require the convoluted methods. On the server that you want to convert install Vmware Convereter 3.0.3 build-89816. The 4.0 version causes some issues but its a good converter too. You are going to treat your Hyper-V machine as Physical Machine for the conversion process. Go through the 4 Steps in the conversion wizard. Ensure you turn off any HP & SQL services before launching the VM Convereter. Ensure your Firewall is not interuppting port 902 bewteen the Hyper-V & ESX Host i.e If a Firewall is involved -IF NOT Disregard!!).

The conversion *doesn't need* a 3rd party machine or any of the other 3rd party software converters. This is a straightforward process and I haven't had any issues except some services that may need to be shut off 1st. Please let me know if this works.

[continuum]

I assume you talk about 2003 VMs only




___________________________________

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

[J1mbo]

Not too sure reading this if the original issue is resolved or not, however I just remembered something I posted a while back using converter for Windows 7 hosts, here.

"using converter build 161434 with Windows 7 V2V needs the source VM OS type to be Vista (otherwise it fails "unable to obtain hardware information") and any USB controllers removed (otherwise the transfer fails "operation not supported")."

Please award points to any useful answer.

[sgloeckle]

Hi @ll,

thanks for you offered help!!!

I at least managed to migrate my W2K8R2 machines as follows:

- WinImage: VHD -> VMDK (target IDE)

- Vmware Server 2.0.2: created new machine and attached VMDK as IDE device

- Vmware vCenter Converter Standalone 4.0.1: converted offline VM to ESX (target IDE)

- vSphere 4 Server: set correct OS type, started and installed VM-Tools

Next Step I'm going to try: Replace the IDE virtual disk with a SCSI virtual disk

cheers, Stefan

[continuum]

read the link I posted - you can directly go to SCSI if that is what you want




___________________________________

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

[sgloeckle]

Hi continuum,

I've tried several times but didn't work properly. Never succeeded in migrating to SCSI target when done all the listed steps.

no idea why