Hi.
I have to convert one Hyper-V's VM to vSphere, it is a windows server 2008 r2 (both HV and VM) and HV have simple default installation.
First step: with source as Hyper-V I had got a problem at 1% such "FAILED: An error occured while opening a virtual disk. Verify that the Converter server and the running source machines have a network access to the source and destination ESX/ESXi hosts.". I think it is not commonly problem at HV, because neighboured test VM converted ok, but it is very pure in environment - have no software as MSSQL and big vhd. And I think if I make google-search more then I can resolve problem (or write additionaly here:). Commonly, one thought was that raid-5 was degraded at that moment, and maybe in fast reading via HV it was timeouts, dont know. (I brought disk to raid 5 just yesterday and try again HV convert tonight.)
Second step: with source as physical (yep, why not) it converted ok, despite that I forgot or can't turn off programs/processes to give VM easy way for convert.
And now I have a question:
Is I should to try convert from HV directly or it enough to do as physical?
Is a principal difference in resulted VM (more clear virtualization layer or windows in VM) when I do one or enother thing?
Finaly I didnt understand a principal need of HV conversion as it. Except several situations: when we can't run source VM for physical conversion (f.e. havnt free CPU/RAM/etc or it is like archive and not for run to prevent state change); when we need fast conversion (without virtual layer from source VM to HV); and when we want to exclude VM's process works effect.