Virt-V2V failing with Didn't receive full volume message

Latest response

I am evaluating RHEV 3.0 for installation at my organization.   Unfortunately I am having issues converting VMs from VMware to RHEV.   The conversion begins and files are written to the export domain, but them the message "Didn't receive full volume. Received 7085617704 of 12884901888 bytes" appears on the screen and the virt-v2v process removes the files it started to write to the export domain.   I have a case with Red Hat on this, but was wondering if anyone else has seen this.

 

Thanks.

 

Frank

FG
Log in to join the conversation

Responses

DY Guru 5340 points
15 October 2012 3:18 PM

Hi,

 

As it stands, this error was reported before, but it seems to be quite rare and we couldn't reproduce it in house. The suspected issue is on the ESXi side, as it fails to provide access to the full length of the disk images of the VMs being exported. If you can look at the service logs on the ESXi side and locate a failure there, it might help with investigating this issue

FG Active Contributor 165 points
15 October 2012 3:48 PM

Hi Dan,

 

I apologize for not updating this , but I found that I needed to add some switches to the virt-v2v command to make it work without getting the "Didn't receive full volume" error.   The switches and values I added were: "-of qcow2 -oa sparse".   No errors and the import went just fine.

David Powles's picture Red Hat 25369 points
16 October 2012 4:35 AM

Great to hear, Frank. Thanks for following up.

da Active Contributor 169 points
5 February 2013 10:07 AM

hi everyone

       i faced the the same problem while converting windows server2008 machine on Esxi 

      Virt-V2V failing with Didn't receive full volume error message and

      then i added the two switches that you mentioned above 

     " -of qcow2 -oa sparse " but i still have the same error  can any one help me to solve this issue

thanks 

GS Expert Active Contributor 1269 points
5 February 2013 11:40 AM

This may explain those errors.  Maybe. 

I did some ESXi virt-v2vs a couple years ago and found that if the ESXi systems have snapshots, the V2V won't work.  We all know this, it's documented.  The part not so well documented was, if the ESXi VM **ever** had any snapshots, even if it doesn't have any now, you can still run into problems. 

Apparently what happens is, when you snapshot a VMWare VM, ESX makes a bunch of .VMDK files to map all the snapshots.  But then when you collapse or get rid of the snapshots, there are still lots of little .VMDK files for each virtual disk.  But the vCenter client presents it all as one big .VMDK file.  You think you're V2Ving one VMDK file for each logical disk, but in fact there are several files all linked together and the V2V process doesn't deal with them very well. 

The workaround I came up with was, log into the vCenter manager, go to storage, and copy the .VMDK files for your source VMs to a whole different directory.  This creates one new VMDK file for each virtual disk in the source VM.  Provision a brand new VMWare VM using your newly created .VMDK files.  So now you have your original source VM, plus a working copy of it on the VMware side. 

Boot the newly provisioned VM from the VMware side, making sure you either disconnect it from any network connections, or keep the original source VM offline.  On the newly provisioned VM, get rid of any and all VMWare tools.  You won't be able to get rid of them once it's V2V'd, so get rid of them before V2Ving it. 

Shut down the VM, V2V it, and now you should be OK on the RHEV side.

- Greg Scott

da Active Contributor 169 points
5 February 2013 12:33 PM

Hi Greg

       thanks for your help but i am sure that my Vm do not have any snapshots i just installed it on ESXI and then i tried to convert it to KVM .... so i have not any snapshots in it 

thanks 

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.