-
Bug
-
Resolution: Unresolved
-
Undefined
-
rhel-10.1
-
virt-v2v-2.8.1-8.el10
-
Yes
-
Moderate
-
rhel-virt-tools
-
None
-
False
-
False
-
-
None
-
None
-
Pass
-
RegressionOnly
-
Unspecified
-
Unspecified
-
Unspecified
-
-
x86_64
-
None
Description of problem：
If a guest has < 100 inodes free on a filesystem, virt-v2v has a check that rejects the conversion.
However the recent change that added XFS filesystem checks before conversion now fails on this guest (see below).
Version-Release number of selected component (if applicable):
virt-v2v-2.8.0-2.el10.x86_64
libguestfs-1.56.0-1.el10.1.x86_64
guestfs-tools-1.54.0-2.el10.x86_64
libguestfs-fssupport-10.1-3.el10.x86_64
How reproducible:
100%
Steps:
1. Prepare a guest with less than 100 inodes on VMware and convert the guest from Vmware by virt-v2v
# virt-v2v -ic vpx://administrator%40vsphere.local@10.73.213.102/data/10.73.212.38/?no_verify=1 -it vddk -io vddk-libdir=/home/vddk7.0.3 -io vddk-thumbprint=86:25:2F:5E:74:5C:43:D9:28:62:31:E0:1F:BB:1F:FD:AC:18:A5:93 -ip /home/passwd Auto-esx7.0-rhel8.7-less-than-100inodes [ 0.0] Setting up the source: -i libvirt -ic vpx://administrator%40vsphere.local@10.73.213.102/data/10.73.212.38/?no_verify=1 -it vddk Auto-esx7.0-rhel8.7-less-than-100inodes [ 2.3] Opening the source [ 32.6] Checking filesystem integrity before conversion virt-v2v: error: libguestfs error: xfs_repair: /dev/rhel/root: Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... - scan filesystem freespace and inode maps... - found root inode chunk Phase 3 - for each AG... - scan (but don't clear) agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 1 - agno = 2 - agno = 3 Phase 6 - check inode connectivity... - traversing filesystem ... If reporting bugs, run virt-v2v with debugging enabled and include the complete output: virt-v2v -v -x [...]
Actual result:
As above description
Expect result:
Fix the bug
Additional info
1. The error info is correct when converting the guest by virt-v2v on rhel9
# virt-v2v -ic vpx://administrator%40vsphere.local@10.73.213.102/data/10.73.212.38/?no_verify=1 -it vddk -io vddk-libdir=/home/vddk7.0.3 -io vddk-thumbprint=86:25:2F:5E:74:5C:43:D9:28:62:31:E0:1F:BB:1F:FD:AC:18:A5:93 -ip /home/passwd Auto-esx7.0-rhel8.7-less-than-100inodes [ 0.0] Setting up the source: -i libvirt -ic vpx://administrator%40vsphere.local@10.73.213.102/data/10.73.212.38/?no_verify=1 -it vddk Auto-esx7.0-rhel8.7-less-than-100inodes [ 1.9] Opening the source [ 36.2] Inspecting the source [ 50.2] Checking for sufficient free disk space in the guest virt-v2v: error: not enough available inodes for conversion on filesystem ‘/’. 63 inodes available < 100 inodes needed If reporting bugs, run virt-v2v with debugging enabled and include the complete output: virt-v2v -v -x [...]
- depends on
-
-
- Release Pending
-
- links to
-
RHBA-2025:149949
virt-v2v bug fix and enhancement update
