On 11/02/14 04:34, Lei Cui wrote: > The bug is still new status, please wait for developer's response
We've had several reports of this bug from several sources, so we're aware of it. Unfortunately we've never managed to reproduce it. We've analysed the code. At the time of the failure, the virt-v2v is sitting in a small and very simple loop, so it's unlikely, but not impossible, that the virt-v2v code is the direct cause. It's also possible that it's a bug in a library used by virt-v2v, but as we can't reproduce it we haven't been able to examine that possibility. It's also possible that it isn't a local problem at all, and it's an issue with the sender. In fact, if we discount a bug in an external library, this looks quite likely. In any case, this is happening quite reliably for you, but never happens on our test systems. Assuming the software is the same, there's presumably a critical difference in either the network or ESX configuration which triggers the bug. Can you think of anything? The data is transferred in a single HTTP transaction. Could there be some network management which kills the connection at 7% of the total disk size? What is 7% of the total disk size? Is it some magic figure which might correspond with a value in a configuration file somewhere? The other place we've asked people to look, so far without success, is on the ESX server itself. Is there anything in the logs about the terminated connection? Unfortunately I don't know which ESX service is responsible for serving this data, so I can't offer any specific pointers. If you can ask somebody on your VMware team, we use the web interface to the datastore browser to retrieve the information. If you can help us get to the bottom of this we'd be very grateful. Thanks, Matt > > ----- Original Message ----- > From: "Maurice James" <[email protected]> > To: "Lei Cui" <[email protected]>, "Matthew Booth" <[email protected]> > Cc: [email protected] > Sent: Tuesday, February 11, 2014 11:17:40 AM > Subject: RE: [Users] virt-v2v failing > > The command that I ran was:virt-v2v -ic esx://hostname/?no-verify=1 -o rhev > -os hostname:/var/lib/exports/in --network ovirtmgmt vmname > The progress went to 7% at most then:Did'nt receive full volume > >> Date: Mon, 10 Feb 2014 22:10:36 -0500 >> From: [email protected] >> To: [email protected]; [email protected] >> CC: [email protected] >> Subject: Re: [Users] virt-v2v failing >> >> Hi, Maurice >> Would you please provide detail info to Mattew Booth, who is the developer >> of virt-v2v. >> there is a exist bug https://bugzilla.redhat.com/show_bug.cgi?id=872301, >> which develop would not reproduce the issue locally. >> Thanks for your information. >> >> Regards, >> Lei >> >> ----- Original Message ----- >> From: "Maurice James" <[email protected]> >> To: [email protected] >> Sent: Tuesday, February 11, 2014 9:58:02 AM >> Subject: [Users] virt-v2v failing >> >> Im trying to import an image from esx and virt-v2v is failing with "Didnt >> receive full volume" any ideas? >> >> _______________________________________________ >> Users mailing list >> [email protected] >> http://lists.ovirt.org/mailman/listinfo/users > > -- Matthew Booth, RHCA, RHCSS Red Hat Engineering, Virtualisation Team GPG ID: D33C3490 GPG FPR: 3733 612D 2D05 5458 8A8A 1600 3441 EA19 D33C 3490 _______________________________________________ Users mailing list [email protected] http://lists.ovirt.org/mailman/listinfo/users
