-
Bug
-
Resolution: Unresolved
-
Undefined
-
rhel-9.7
-
None
-
libvirt-11.4.0-1.el10
-
No
-
Low
-
rhel-virt-core-libvirt-1
-
ssg_virtualization
-
24
-
3
-
False
-
False
-
-
None
-
None
-
Unspecified
-
Unspecified
-
Unspecified
-
-
x86_64
-
11.3.0
-
None
Description of problem：
Improve virt-v2v error info when libvirt daemons that provide various services are not running
Version-Release number of selected component (if applicable):
virt-v2v-2.7.1-8.el9.x86_64
libvirt-client-10.10.0-9.el9.x86_64
qemu-img-9.1.0-17.el9.x86_64
How reproducible:
100%
Steps:
1.Prepare a newly installed RHEL server and install virt-v2v. The virtqemud-ro socket is not started yet.
#yum install virt-v2v -y
2, Use virsh to connect vsphere client, the connection is successful
# virsh -c vpx://non-admin%40vsphere.local@10.73.212.129/data/10.73.212.36/?no_verify=1 Enter non-admin@vsphere.local's password for 10.73.212.129: Welcome to virsh, the virtualization interactive terminal. Type: 'help' for help with commands 'quit' to quit virsh #
3. Convert a guest from VMware by virt-v2v
# virt-v2v -ic vpx://non-admin%40vsphere.local@10.73.212.129/data/10.73.212.36/?no_verify=1 -it vddk -io vddk-libdir=/home/vddk8.0.3 -io vddk-thumbprint=CB:9F:B1:9D:33:49:6C:60:AD:3C:A5:16:77:91:5F:CD:1B:24:B1:43 -ip /home/passwd 'Auto-esx8.0-rhel9.4-0-efi-test-%-\\-m' virt-v2v: error: exception: libvirt: VIR_ERR_OPERATION_UNSUPPORTED: VIR_FROM_REMOTE: Operation not supported: Cannot use direct socket mode if no URI is set. For more information see https://libvirt.org/kbase/failed_connection_after_install.html If reporting bugs, run virt-v2v with debugging enabled and include the complete output: virt-v2v -v -x [...]
4. virtqemud-ro socket can't start automatically so start it manually
# systemctl start virtqemud-ro.socket
5. Convert a guest from VMware by virt-v2v again
# virt-v2v -ic vpx://non-admin%40vsphere.local@10.73.212.129/data/10.73.212.36/?no_verify=1 -it vddk -io vddk-libdir=/home/vddk8.0.3 -io vddk-thumbprint=CB:9F:B1:9D:33:49:6C:60:AD:3C:A5:16:77:91:5F:CD:1B:24:B1:43 -ip /home/passwd 'Auto-esx8.0-rhel9.4-0-efi-test-%-\\-m' -o null [ 0.2] Setting up the source: -i libvirt -ic vpx://non-admin%40vsphere.local@10.73.212.129/data/10.73.212.36/?no_verify=1 -it vddk Auto-esx8.0-rhel9.4-0-efi-test-%-\\-m [ 1.8] Opening the source [ 19.2] Inspecting the source [ 24.8] Checking for sufficient free disk space in the guest [ 24.8] Converting Red Hat Enterprise Linux 9.4 Beta (Plow) (rhel9.4) to run on KVM virt-v2v: This guest has virtio drivers installed. [ 55.5] Setting a random seed [ 55.6] SELinux relabelling [ 68.5] Mapping filesystem data to avoid copying unused and blank areas [ 69.0] Closing the overlay [ 69.2] Assigning disks to buses [ 69.2] Checking if the guest needs BIOS or UEFI to boot virt-v2v: This guest requires UEFI on the target to boot. [ 69.2] Setting up the destination: -o null [ 70.6] Copying disk 1/1 █ 100% [****************************************] [ 191.3] Creating output metadata [ 191.3] Finishing off
Actual result:
As above description
Expect result:
Fix the bug
Additional info
Similar problem have been fixed in https://bugzilla.redhat.com/show_bug.cgi?id=2182024 before
- is blocked by
-
RHEL-71662 Rebase libvirt in RHEL-10.1
-
- Release Pending
-
- links to
-
RHBA-2025:148139
libvirt bug fix and enhancement update