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

win10 x86 32 bit uefi guest can't boot into OS after v2v conversion

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • rhel-10.0.beta
    • virt-v2v
    • None
    • None
    • Moderate
    • rhel-sst-virtualization
    • ssg_virtualization
    • 8
    • False
    • Hide

      None

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

      Description of problem:
      win10 x86 uefi guest can't boot into OS after v2v conversion

      Version-Release number of selected component (if applicable):
      virt-v2v-2.5.6-1.el10.x86_64
      libguestfs-1.52.2-2.el10.x86_64
      guestfs-tools-1.52.0-6.el10.x86_64
      libnbd-1.20.2-2.el10.x86_64
      nbdkit-1.40.0-2.el10.x86_64
      libvirt-libs-10.5.0-5.el10.x86_64
      qemu-img-9.0.0-7.el10.x86_64
      kernel-6.11.0-0.rc3.19.el10.x86_64

      How reproducible:
      100%

      Steps to Reproduce:
      1. Convert a win10-x86-efi 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/vddk8.0.2 -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-win10-i386-efi
      [   0.3] 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-win10-i386-efi
      [   2.1] Opening the source
      [   8.9] Inspecting the source
      [  14.8] Checking for sufficient free disk space in the guest
      [  14.8] Converting Windows 10 Enterprise to run on KVM
      virt-v2v: Fixing UEFI bootloader.
      virt-v2v: This guest has virtio drivers installed.
      [  27.9] Mapping filesystem data to avoid copying unused and blank areas
      [  29.3] Closing the overlay
      [  29.6] Assigning disks to buses
      [  29.6] Checking if the guest needs BIOS or UEFI to boot
      virt-v2v: This guest requires UEFI on the target to boot.
      [  29.6] Setting up the destination: -o libvirt
      [  31.3] Copying disk 1/1
      █ 100% [****************************************]
      [ 296.3] Creating output metadata
      [ 296.3] Finishing off
      

      2. Check the guest after v2v conversion but found guest can't boot into OS after powering on, please check screenshot 'win10-x86-efi-cannot-boot.png'

      Actual results:
      As above description

      Expected result:
      Fix the bug 

      Additional info:
      There was a similar Bug 1434737 - Win10 x86 guest will BSOD after converting to rhv by virt-v2v sometimes that has been fixed before

        1. esx8.0-win10-i386-efi-1.log
          7 kB
          Ming Xie
        2. v2v-convert-win10-i386-efi-guest.log
          2.18 MB
          Ming Xie
        3. win10-x86-efi-guest-after-v2v.png
          49 kB
          Ming Xie

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

                Created:
                Updated: