-
Bug
-
Resolution: Unresolved
-
Critical
-
None
-
None
-
None
Following the upgrade of the MTV operator from version 2.10.0 to 2.10.1, virtual machine migrations that were previously successful are now failing. The migrations result in the following error message being recorded in the virt-v2v container logs:
... command: mount '-o' 'ro' '/dev/vgroot/lvroot' '/sysroot/' [ 19.636552] SGI XFS with ACLs, security attributes, scrub, quota, no debug enabled nbdkit: file.3: debug: file: flush [ 19.641783] XFS (dm-1): Deprecated V4 format (crc=0) not supported by kernel. command: mount returned 32 command: mount: stderr: mount: /sysroot: wrong fs type, bad option, bad superblock on /dev/mapper/vgroot-lvroot, missing codepage or helper program, or other error. dmesg(1) may have more information after failed mount system call. ocaml_exn: 'mount_ro' raised 'Failure' exception guestfsd: error: mount exited with status 32: mount: /sysroot: wrong fs type, bad option, bad superblock on /dev/mapper/vgroot-lvroot, missing codepage or helper program, or other error. dmesg(1) may have more information after failed mount system call. guestfsd: => mount_ro (0x49) took 0.28 secs libguestfs: trace: v2v: mount_ro = -1 (error) libguestfs: trace: v2v: umount_all ...
The failing virtual machines are VMs that use XFS V4 format. Example of such a virtual machine:
$ uname -a Linux dv0629d 4.18.0-553.82.1.el8_10.x86_64 #1 SMP Thu Oct 23 16:05:55 EDT 2025 x86_64 x86_64 x86_64 GNU/Linux
$ xfs_db -r /dev/mapper/vgroot-lvroot xfs_db> version versionnum [0xb4b4+0x8a] = V4,NLINK,DIRV2,ATTR,ALIGN,LOGV2,EXTFLG,MOREBITS,ATTR2,LAZYSBCOUNT,PROJID32BIT
Virtual machines utilizing the XFS V5 format were migrated without any issues.
After reverting to MTV 2.10.0 and re-executing the migrations, the virtual machines using XFS V4 format were successfully migrated.
- is related to
-
RHEL-143673 Add new xfs_info2 API to expose XFS version information
-
- Integration
-
