Hello, I’m using virt-p2v tool to do some VM migrations from unsupported hypervisors and stumbled across the need of a virt-v2v dedicated server to handle conversions. My first action was: rpm -qa on oVirt Node and found virt-v2v already installed. So the natural ideia was to use oVirt Node as the conversion server, it already have everything needed: virt-v2v and the export domain. So why not? Well, it turns out it doesn’t work. After pointing to oVirt Node within virt-p2v tool, the conversion procedure hangs at the begging, requesting an username and password for libvirt that I’m unaware. And even if I was aware it is impossible to input the values since there’s no escape from the console to put the values nor any form on the GUI to do so. libguestfs: libvirt version = 4005000 (4.5.0) libguestfs: guest random name = guestfs-sf2i0jl3mmcxtwly libguestfs: connect to libvirt libguestfs: opening libvirt handle: URI = qemu:///system, auth = default+wrapper, flags = 0 libvirt needs authentication to connect to libvirt URI qemu:///system (see also: http://libvirt.org/auth.html http://libvirt.org/uri.html) Please enter your authentication name: Please enter your password: I eventually gave up and spun a VM with virt-v2v and the conversion is running. The question is: wasn’t a good ideia to use oVirt Node as the conversion server? Why it failed? I still have a lot of conversions to do, and if I can use the node installation it would be great. Thanks, Sent from my iPhone