Converter Hyper-V to Vmware

[fborges555]

Hi guru

I would like to know what the heck am I doing wrong:

I have a windows 2008 R2 enterprise in Hyper-v that I would like to convert to a VMware Virtual server.

I have tried to do the standalone converter install on the source machine and all is cool but the virtual machine created in Vcenter require to be fix using windows Installation disk, so it does not boot up.

Has anyone here been lucky converting 2008 r2 ent. to vm server that converter correctly?

Thanks for any help on this matter

[Rosen Tomov]

The information you shared is insufficient, please attach log bundle.

[fborges555]

poceh.

as you can tell very new to vmware and still learning, where do I get this log bundle to troubleshoot this issue.

Thanks a bunch for jumping in

[Rosen Tomov]

From Converter UI, select job, right mouse click, invoke export log bundle.

HTH

[fborges555]

Poceh.

I just retake this project again , hopefully you can still help on this , The job got stuck on 10% and it says the remaining is 6 days, this cant be correct?

thoughts?

Thanks

[Fire07]

Check your network settings,

To improve the speed of the transfer need use the same lan or network between both machines.

what version of vmware converter use?

what version of windows or hyper v need to export?

[fborges555]

Fire

Thanks a bunch for jumping in

1)VM converter 6.2

2) 2008 r2

as yo can see I am new to all this, but I have fail to ask, what happen to the VM machine once the VM converter finish with the conversion, I still need the source machine working after the conversion.

Thanks

[patanassov]

The source machine is mostly unaffected by the conversion. The probably only meaningful difference is whether you do powered on or powered off conversion. In the first case, Converter agent is installed in the source machine (and could be uninstalled after conversion); it is not in the second case.

The logs can be found at %ALLUSERSPROFILE%\VMware\VMware vCenter Converter Standalone\logs. The above difference is important in that case, too. For powered off conversion - look for agent log in the Hyper-V machine (named 'vmware-converter-agent##.log), for powered on - worker log in the source machine (similar naming pattern).

HTH,

Plamen

[NathanosBlightc]

No need to worry about your source machine. You can configure to power it off after ending synchronization between source and destination. After all everything may be cause of your interruption anyway, so you still need to upload at least a bunch of error lines inside the bundle log if you can find anything related to this issue (last lines of the log file will help you). Then other people can help you better

[Rosen Tomov]

Could you upload logs?

Usually network throughput is the bottleneck but it also depends on ESX workload - the data must be written on its disk and could also be slow operation.