Created attachment 1200941 [details] libvirt debug output Description of problem: virt-v2v -v -x -ic 'xen+ssh://root.3.4' G1BATCH -o local -os /v2vconvert/ virsh -c xen+ssh://root.3.4 list --all Both commands fail. Version-Release number of selected component (if applicable): CentOS 7.2 libvirt-1.2.17-13.el7_2.5.x86_64 virt-v2v-1.28.1-1.55.el7.centos.4.x86_64 How reproducible: Run above mentioned commands. Steps to Reproduce: 1. Run commands. 2. Observe output. Actual results: [root@kvm1 tmp]# virsh -c xen+ssh://root.3.4 list --all 2016-09-14 19:40:30.072+0000: 21571: info : libvirt version: 1.2.17, package: 13.el7_2.5 (CentOS BuildSystem <http://bugs.centos.org>, 2016-06-23-14:23:27, worker1.bsys.centos.org) 2016-09-14 19:40:30.072+0000: 21571: debug : virLogParseOutputs:1091 : outputs=1:file:virsh.log 2016-09-14 19:40:30.074+0000: 21573: debug : virFileClose:102 : Closed fd 3 2016-09-14 19:40:30.074+0000: 21573: debug : virFileClose:102 : Closed fd 5 2016-09-14 19:40:30.074+0000: 21573: debug : virFileClose:102 : Closed fd 6 2016-09-14 19:40:30.074+0000: 21573: debug : virFileClose:102 : Closed fd 7 2016-09-14 19:40:30.074+0000: 21573: debug : virFileClose:102 : Closed fd 9 error: failed to connect to the hypervisor error: End of file while reading data: 2016-09-14 19:40:30.074+0000: 21573: debug : virFileClose:102 : Closed fd 8 2016-09-14 19:40:30.074+0000: 21573: debug : virFileClose:102 : Closed fd 10 2016-09-14 19:40:30.074+0000: 21573: debug : virLogParseOutputs:1091 : outputs=1:file:virsh.log: Input/output error [root@kvm1 tmp]# virt-v2v -v -x -ic 'xen+ssh://root.3.4' G1BATCH -o local -os /v2vconvert/ 2016-09-14 19:44:17.948+0000: 21646: info : libvirt version: 1.2.17, package: 13.el7_2.5 (CentOS BuildSystem <http://bugs.centos.org>, 2016-06-23-14:23:27, worker1.bsys.centos.org) 2016-09-14 19:44:17.948+0000: 21646: debug : virLogParseOutputs:1091 : outputs=1:file:virsh.log virt-v2v: libguestfs 1.28.1 (x86_64) [ 0.0] Opening the source -i libvirt -ic xen+ssh://root.3.4 G1BATCH input_libvirt_xen_ssh: source: scheme xen+ssh server 1.2.3.4 2016-09-14 19:44:17.954+0000: 21647: debug : virFileClose:102 : Closed fd 3 2016-09-14 19:44:17.954+0000: 21647: debug : virFileClose:102 : Closed fd 5 2016-09-14 19:44:17.954+0000: 21647: debug : virFileClose:102 : Closed fd 7 libvirt: XML-RPC error : End of file while reading data: 2016-09-14 19:44:17.954+0000: 21647: debug : virFileClose:102 : Closed fd 6 2016-09-14 19:44:17.954+0000: 21647: debug : virFileClose:102 : Closed fd 8 2016-09-14 19:44:17.955+0000: 21647: debug : virLogParseOutputs:1091 : outputs=1:file:virsh.log: Input/output error virt-v2v: error: internal error: invalid argument: cannot open libvirt connection 'xen+ssh://root.3.4' If reporting bugs, run virt-v2v with debugging enabled and include the complete output: virt-v2v -v -x [...] Expected results: Connect and be able to convert. Additional info: Remote xen server is: Ubuntu 12.04.2 LTS libxen-4.1 4.1.6.1-0ubuntu0.12.04.11
Is libvirtd running on the remote host?
You are right, there could have been a message for that... Another issue now: libvirt does not allow to convert a running virtual server, what is understandable, however when you shut it down (xen shutdown G1BATCH) - it does not find a machine. virt-v2v -v -x -ic 'xen+ssh://root.3.4' G1BATCH -o local -os /v2vconvert/ virt-v2v: libguestfs 1.28.1 (x86_64) [ 0.0] Opening the source -i libvirt -ic xen+ssh://root.3.4 G1BATCH input_libvirt_xen_ssh: source: scheme xen+ssh server 1.2.3.4 virt-v2v: error: internal error: invalid argument: cannot find libvirt domain 'G1BATCH': Domain not found: xenUnifiedDomainLookupByName
Thank you for reporting this issue to the libvirt project. Unfortunately we have been unable to resolve this issue due to insufficient maintainer capacity and it will now be closed. This is not a reflection on the possible validity of the issue, merely the lack of resources to investigate and address it, for which we apologise. If you none the less feel the issue is still important, you may choose to report it again at the new project issue tracker https://gitlab.com/libvirt/libvirt/-/issues The project also welcomes contribution from anyone who believes they can provide a solution.