Uploaded image for project: 'RHEL'
  1. RHEL
  2. RHEL-97600

Virt-v2v fails to convert some guests with libguestfs error: e2fsck

Linking RHIVOS CVEs to...Migration: Automation ...SWIFT: POC ConversionSync from "Extern...XMLWordPrintable

    • virt-v2v-2.8.1-8.el10
    • Yes
    • Moderate
    • rhel-virt-tools
    • None
    • False
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • Unspecified
    • Unspecified
    • Unspecified
    • x86_64
    • None

      Description of problem:
      Virt-v2v fails to convert some guests with libguestfs error: e2fsck

      Version-Release number of selected component (if applicable):
      virt-v2v-2.8.0-1.el10.x86_64

      How reproducible:
      100%

      Steps:
      1. Prepare a ubuntu guest on VMware env, here is disk info of the guest

       

      # lsblk
      NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
      loop1    7:1    0 104.6M  1 loop /snap/core/17210
      sda      8:0    0    16G  0 disk 
      ├─sda1   8:1    0     1M  0 part 
      └─sda2   8:2    0    16G  0 part /
      sr0     11:0    1  1024M  0 rom  
      # cat /etc/fstab 
      UUID=6f5defa0-784a-11e8-90a7-005056ac79a7 / ext4 defaults 0 0
      /swap.img    none    swap    sw    0    0
      # df -h
      Filesystem      Size  Used Avail Use% Mounted on
      udev            462M     0  462M   0% /dev
      tmpfs            99M  1.7M   97M   2% /run
      /dev/sda2        16G  8.5G  6.4G  58% /
      tmpfs           493M     0  493M   0% /dev/shm
      tmpfs           5.0M     0  5.0M   0% /run/lock
      tmpfs           493M     0  493M   0% /sys/fs/cgroup
      tmpfs            99M   28K   99M   1% /run/user/120
      tmpfs            99M   28K   99M   1% /run/user/1000
      tmpfs            99M     0   99M   0% /run/user/0
      /dev/loop1      105M  105M     0 100% /snap/core/17210
      

       

      2. Virt-v2v fails to convert the guest from VMware

      # 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-ubuntu18.04LTS-x86_64-bug168388
      [   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-ubuntu18.04LTS-x86_64-bug168388
      [   1.9] Opening the source
      [  17.2] Checking filesystem integrity before conversion
      virt-v2v: error: libguestfs error: e2fsck: e2fsck 1.47.1 (20-May-2024)
      Warning: skipping journal recovery because doing a read-only filesystem 
      check.
      Pass 1: Checking inodes, blocks, and sizes
      Deleted inode 786440 has zero dtime.  Fix? no
      Inodes that were part of a corrupted orphan linked list found.  Fix? no
      Inode 921404 was part of the orphaned inode list.  IGNORED.
      Pass 2: Checking directory structure
      Pass 3: Checking directory connectivity
      Pass 4: Checking reference counts
      Pass 5: Checking group summary information
      Block bitmap differences:  -296064 -(1133118--1133130)
      Fix? no
      Free blocks count wrong (2003043, counted=2000892).
      Fix? no
      Inode bitmap differences:  -786440 -921404
      Fix? no
      Free inodes count wrong (836696, counted=836693).
      Fix? no
      
      /dev/sda2: ********** WARNING: Filesystem still has errors **********
      /dev/sda2: 211880/1048576 files (0.2% non-contiguous), 2190493/4193536 
      blocks
      If reporting bugs, run virt-v2v with debugging enabled and include the 
      complete output:
        virt-v2v -v -x [...]
       
      

       

      As above description

      Expect result:
      Fix the bug

      Additional info
      Can't reproduce the bug on rhel9

      # rpm -q virt-v2v libguestfs guestfs-tools nbdkit libnbd
      virt-v2v-2.7.1-12.el9.x86_64
      libguestfs-1.54.0-8.el9.x86_64
      guestfs-tools-1.52.2-5.el9.x86_64
      nbdkit-1.38.5-10.el9.x86_64
      libnbd-1.20.3-4.el9.x86_64
      
      # 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-ubuntu18.04LTS-x86_64-bug168388
      [   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-ubuntu18.04LTS-x86_64-bug168388
      [   1.8] Opening the source
      [   7.9] Inspecting the source
      [  10.9] Checking for sufficient free disk space in the guest
      [  10.9] Converting Ubuntu 18.04.2 LTS (ubuntu18.04) to run on KVM
      virt-v2v: warning: could not determine a way to update the configuration of 
      Grub2
      virt-v2v: The QEMU Guest Agent will be installed for this guest at first 
      boot.
      virt-v2v: This guest has virtio drivers installed.
      [  67.5] Setting a random seed
      [  67.6] SELinux relabelling
      [  67.7] Mapping filesystem data to avoid copying unused and blank areas
      [  69.0] Closing the overlay
      [  69.3] Assigning disks to buses
      [  69.3] Checking if the guest needs BIOS or UEFI to boot
      [  69.3] Setting up the destination: -o libvirt
      [  71.0] Copying disk 1/1
      █ 100% [****************************************]
      [ 338.8] Creating output metadata
      [ 338.8] Finishing off

              rhn-eng-rjones Richard Jones
              mxie@redhat.com Ming Xie
              virt-maint virt-maint
              Ming Xie Ming Xie
              Votes:
              0 Vote for this issue
              Watchers:
              12 Start watching this issue

                Created:
                Updated: