Hide Forgot
Description of problem: When use virt-v2v to convert guest,there is error:set_autosync: this function can only be called in the config state at /usr/share/perl5/vendor_perl/Sys/VirtConvert/GuestfsHandle.pm line 107. Version-Release number of selected component (if applicable): virt-v2v-0.8.7-1.el6.x86_64 libvirt-0.9.10-3.el6.x86_64 libguestfs-1.16.6-1.el6.x86_64 How reproducible: always Steps to Reproduce: # virt-v2v -ic qemu+ssh://10.66.72.122/system -os default -b breth0 kvm-rhel5.7-i386 kvm-rhel5.7-i386.img: 100% [======================================================================================]D 0h02m20s set_autosync: this function can only be called in the config state at /usr/share/perl5/vendor_perl/Sys/VirtConvert/GuestfsHandle.pm line 107. Actual results: virt-v2v failed and message printed:set_autosync: this function can only be called in the config state at /usr/share/perl5/vendor_perl/Sys/VirtConvert/GuestfsHandle.pm line 107. Expected results: It should convert successfully. Additional info: Tested with libguestfs-1.16.5-1.el6.x86_64,virt-v2v can convert successfully.
There are actually two issues here: - the fix for bug 796520 is wrong: set_autosync affects the close call and does not need to be called only in the config state. - autosync is the default (since libguestfs 1.6 / RHEL 6.1) and so virt-v2v does not need to set this.
(In reply to comment #6) > There are actually two issues here: > > - the fix for bug 796520 is wrong: set_autosync affects the > close call and does not need to be called only in the config state. > > - autosync is the default (since libguestfs 1.6 / RHEL 6.1) and so > virt-v2v does not need to set this. Thanks,rjones. Reassign the bug to libguestfs and add the regression keywords.
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: No Documentation needed
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHSA-2012-0774.html