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

virt-v2v can't convert sles10 guest with reiserfs filesystem from VMware

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

    • Icon: Bug Bug
    • Resolution: Won't Do
    • Icon: Undefined Undefined
    • None
    • rhel-10.1
    • virt-v2v
    • No
    • None
    • rhel-virt-tools
    • None
    • False
    • False
    • Hide

      None

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

      Description of problem:
      virt-v2v can't convert sles10 guest with reiserfs filesystem from VMware

      Version-Release number of selected component (if applicable):
      virt-v2v-2.8.1-1.el10.x86_64
      libguestfs-fssupport-10.1-3.el10.x86_64
      libguestfs-1.56.0-1.el10.1.x86_64
      guestfs-tools-1.54.0-2.el10.x86_64
      nbdkit-1.42.5-1.el10.x86_64
      libnbd-1.22.2-1.el10.x86_64
      libvirt-libs-11.4.0-1.el10.x86_64
      qemu-img-10.0.0-6.el10.x86_64

      How reproducible:
      100%

      Steps:
      1. Prepare a sles10 guest with  reiserfs on VMware

      # cat /etc/SuSE-release 
      SUSE Linux Enterprise Server 10 (x86_64)
      VERSION = 10
      # cat /etc/fstab 
      /dev/sda2            /                    reiserfs   acl,user_xattr        1 1
      /dev/sda1            swap                 swap       defaults              0 0
      proc                 /proc                proc       defaults              0 0
      sysfs                /sys                 sysfs      noauto                0 0
      debugfs              /sys/kernel/debug    debugfs    noauto                0 0
      devpts               /dev/pts             devpts     mode=0620,gid=5       0 0
      

       

      2. Convert the 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/vddk9.0.0  -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  esx8.0-sles10-x86_64-with-reiserfs
      [   0.1] 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 esx8.0-sles10-x86_64-with-reiserfs
      [   1.8] Opening the source
      [  17.5] Checking filesystem integrity before conversion
      [  18.0] Detecting if this guest uses BIOS or UEFI to boot
      [  18.2] Inspecting the source
      virt-v2v: error: inspection could not detect the source guest (or physical 
      machine) operating system.
      Assuming that you are running virt-v2v/virt-p2v on a source which is 
      supported (and not, for example, a blank disk), then this should not 
      happen.
      No root device found in this operating system image.
      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

       

              virt-maint virt-maint
              mxie@redhat.com Ming Xie
              virt-maint virt-maint
              Ming Xie Ming Xie
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: