Hi, I am using V2V to convert VMware machine to Hyper-V. I powered off the VMware VM. I provided the remote source VCenter, and remote destination Hyper-V server, and Virtual Machine Path. I click 'Finish' and the conversion starts. The 'Converting' screen displays and shows 0%. Then, a few seconds later it jumps to 100%, and the 'Conversion Log' displayed on screen shows these four time stamped events:
1. Started
2. Opening Image File
3. Success
4. Creating Image File / Error creating image / Invalid parmeter. / Conversion failed.
I checked the log file and I see 'INFO' entry "...pathOutput: D:\VMs\Test-AsbCoLWca01\Virtual Hard Disks\Test-AsbCoLWca0.vhd". then, a few lines later I see 'ERROR' entry "...CVHDXFile::NewFile: File extension is not VHDX."
So, why does the PathOutput list a VHD extension, but as per the error it seems like it wanted a VHXD extension? Does this have anything to do with the failure? Any help is appreciated. Thanks.
1. Started
2. Opening Image File
3. Success
4. Creating Image File / Error creating image / Invalid parmeter. / Conversion failed.
I checked the log file and I see 'INFO' entry "...pathOutput: D:\VMs\Test-AsbCoLWca01\Virtual Hard Disks\Test-AsbCoLWca0.vhd". then, a few lines later I see 'ERROR' entry "...CVHDXFile::NewFile: File extension is not VHDX."
So, why does the PathOutput list a VHD extension, but as per the error it seems like it wanted a VHXD extension? Does this have anything to do with the failure? Any help is appreciated. Thanks.
Statistics: Posted by tommytwotone — Fri Feb 28, 2025 11:49 pm