Hello,
trying to migrate an HyperV server to ESX 3.5 I am stuck with two HyperV virtual machine.
On both of them, when I try to launch the conversion with VMware Converter 4.0.1, I get in the Application Log of the virtual machines those two errors:
Volume Shadow Copy Service information: The COM Server with CLSID {faf53cc4-bd73-4e36-83f1-2b23f46e513e} and name VSSEvent cannot be started.
Volume Shadow Copy Service error: Unexpected error calling routine CoCreateInstance. hr = 0x80029c4a.
I confirm that the "vssadmin list writers" command list the VSS providers in the "Stable" state.
Anyone has got stuck in this situation?
Anyone?
Are you trying to migrate them hot? If so try shutting them down first.
I have never tried it before but you may be able to use the converter boot CD on the VM. Don't know if that will work though.
Unfortunately VMware Converter doesn't still support HyperV virtual machines conversion from their files - they must be converted ah physical.
Yes, I've tried the Converter boot cd, but it dumps during boot time, saying that it has to be run from inside a virtual machine. I think it too doesn't support HyperV
Yes, I've tried the Converter boot cd, but it dumps during boot time, saying that it has to be run from inside a virtual machine.
What ??? - that should not happen - can you post exact error message or post a screenshot ?
___________________________________
VMX-parameters- VMware-liveCD - VM-Sickbay
I've tried with the latest VMware Converter Coldboot CD (4.0.3 u4).
Now at least it boot, but then stop with a popup which say "No network adapter found" 😕
try this one
http://sanbarrow.com/phpBB2/viewtopic.php?t=1544
___________________________________
VMX-parameters- VMware-liveCD - VM-Sickbay
Have you tried Starwind's product?
http://starwindsoftware.com/converter
Jase McCarty
Co-Author of VMware ESX Essentials in the Virtual Data Center
(ISBN:1420070274) from Auerbach
Please consider awarding points if this post was helpful or correct
thanks Jase - goot tip
___________________________________
VMX-parameters- VMware-liveCD - VM-Sickbay
---
Hi,
I've successfully converted the disk using StarWind Converter.
Now I have the VM, but it dump at boot, because it hasn't the drivers.
I've used the Qui Hong fixvmscsi with BartPE, but they don't seem to fix the issue (www.rtfm-ed.co.uk/?page_id=17)
Some suggestion about this?
Some suggestions?
run the configure option of converter against the new VM
___________________________________
VMX-parameters- VMware-liveCD - VM-Sickbay
Tried it, still no luck.
Well, I did in another way.
I put in the HyperV a second disk, did an NTBackup saving it on this disk, created on ESX a new VM, attached the HyperV data disk converted with Starwind Converter, and boot from Windows 2003 CD doing an ASR.
Bye