Re: [Users] virt-v2v failing

On 11/02/14 04:34, Lei Cui wrote: 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 -- Matthew Booth, RHCA, RHCSS Red Hat Engineering, Virtualisation Team GPG ID: D33C3490 GPG FPR: 3733 612D 2D05 5458 8A8A 1600 3441 EA19 D33C 3490