-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
rhel-9.6
-
None
-
No
-
None
-
1
-
rhel-virt-core-libvirt-1
-
None
-
False
-
False
-
-
None
-
Libvirt in planning
-
None
-
None
-
Unspecified
-
Unspecified
-
Unspecified
-
None
What were you trying to do that didn't work?
During testing of the BTRFS we found that that when running without the LIBGUESTFS_BACKEND=direct the v2v fails inside the container with error:
What is the impact of this issue to you?
MTV needs to use LIBGUESTFS_BACKEND=direct
Please provide the package NVR for which the bug is seen:
virt-v2v 2.8.1rhel=10,release=3.el10 (x86_64)
How reproducible is this bug?:
100%
Steps to reproduce
- Create container with v2v
- Do not use the LIBGUESTFS_BACKEND=direct
- Run the container
Expected results
Actual results
libguestfs: guest random name = guestfs-9hvgvfrjaoxhlo6s libguestfs: connect to libvirt libguestfs: opening libvirt handle: URI = qemu:///session, auth = default+wrapper, flags = 0 libguestfs: clear_socket_create_context: setsockcreatecon failed: NULL: Permission denied [you can ignore this message if you are not using SELinux + sVirt] libguestfs: trace: v2v: launch = -1 (error) virt-v2v-in-place: error: libguestfs error: could not connect to libvirt (URI = qemu:///session): Cannot create user runtime directory '/.cache/libvirt': Permission denied [code=38 int1=13] rm -rf -- '/tmp/v2vnbdkit.UOf1bo'
- is related to
-
MTV-3035 Switch MTV LIBGUESTFS_BACKEND to libvirt
-
- New
-
-
-
- Closed
-
