Uploaded image for project: 'Migration Toolkit for Virtualization'
  1. Migration Toolkit for Virtualization
  2. MTV-1613

[Test Only] Failed to create win 2019 VM during cold migration (UEFI+BIOS both are set)

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Critical Critical
    • 2.7.5
    • 2.7.2
    • None
    • False
    • None
    • True

      Description of problem:

      Cold migrate win2019 VM from RHV to remote cluster, during VirtualMachineCreation phase, hit firmware.bootloader setting error:
      "admission webhook "virtualmachine-validator.kubevirt.io" denied the request: spec.template.spec.domain.firmware.bootloader has both EFI and BIOS configured, but they are mutually exclusive."
      

      Version-Release number of selected component (if applicable):

      MTV 2.7.2, CNV 4.17.0

      Step1: Create RHV provider, select the VM and create the cold migration plan to migrate VM to remote cluster

      Step2: Check the migration pipeline: DiskTransfer succeeded, hit error below during the "VirtualMachineCreation". Checked the VM setting on RHV:"Chipset/Firmware Type: Q35 Chipset with BIOS"
      admission webhook "virtualmachine-validator.kubevirt.io" denied the request: spec.template.spec.domain.firmware.bootloader has both EFI and BIOS configured, but they are mutually exclusive.

      Actual results:

      In step2: Hit error during the VirtualMachineCreation

      Expected results:

      In step2: Create VM successfully

       

            [MTV-1613] [Test Only] Failed to create win 2019 VM during cold migration (UEFI+BIOS both are set)

            Errata Tool added a comment -

            Since the problem described in this issue should be resolved in a recent advisory, it has been closed.

            For information on the advisory (MTV 2.7.5 Images), and where to find the updated files, follow the link below.

            If the solution does not work for you, open a new bug report.
            https://access.redhat.com/errata/RHBA-2024:10679

            Errata Tool added a comment - Since the problem described in this issue should be resolved in a recent advisory, it has been closed. For information on the advisory (MTV 2.7.5 Images), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2024:10679

            Chenli Hu added a comment -
            • Reproduced on MTV 2.7.3 with CNV 4.17.0:

            Hit the error in "VirtualMachineCreation" phase: "admission webhook "virtualmachine-validator.kubevirt.io" denied the request: spec.template.spec.domain.firmware.bootloader has both EFI and BIOS configured, but they are mutually exclusive."

            • Tested on MTV2.7.5(IIB: 873881) with CNV 4.17.2(IIB: 871049):

            Create cold migration plan to migrate win2019 vm(firmware:BIOS) from vsphere7 to Openshift Virtualization cluster,

            migration plan executed succeeded without error and VM is running on target cluster, test PASSED

            Steps:

            1) Create cold migration plan: mtv-win2019-79 to migrate win2019 vm(firmware:BIOS): mtv-win2019-79 from vsphere7 to Openshift Virtualization cluster

            2) Check the plan is executed succeeded without error

            3) Check the VM is running on target cluster, can login to VM

            Chenli Hu added a comment - Reproduced on MTV 2.7.3 with CNV 4.17.0: Hit the error in "VirtualMachineCreation" phase: "admission webhook "virtualmachine-validator.kubevirt.io" denied the request: spec.template.spec.domain.firmware.bootloader has both EFI and BIOS configured, but they are mutually exclusive." Tested on MTV2.7.5(IIB: 873881) with CNV 4.17.2(IIB: 871049): Create cold migration plan to migrate win2019 vm(firmware:BIOS) from vsphere7 to Openshift Virtualization cluster, migration plan executed succeeded without error and VM is running on target cluster, test PASSED Steps: 1) Create cold migration plan: mtv-win2019-79 to migrate win2019 vm(firmware:BIOS): mtv-win2019-79 from vsphere7 to Openshift Virtualization cluster 2) Check the plan is executed succeeded without error 3) Check the VM is running on target cluster, can login to VM

            Chenli Hu added a comment -

            Tested on MTV2.7.5(IIB: 873881) with CNV 4.17.2(IIB: 871049)

            Cold migrate VM: mt-win2019-79(Boot firmware: BIOS) from RHV provider(with CA certificate) to remote Openshift Virtualization cluster,

            the migration executed successfully, the vm is created on target cluster, start vm, the vm is running on target cluster, test PASSED.

            More details:

            Step1: Create RHV provider with CA certificate, select the VM:  mt-win2019-79 and create the cold migration plan to migrate VM to remote cluster

            Step2: Check is migration plan succeeded, no error

            Step3: Start the VM, check the VM is running on target cluster

            Chenli Hu added a comment - Tested on MTV2.7.5(IIB: 873881) with CNV 4.17.2(IIB: 871049) Cold migrate VM: mt-win2019-79(Boot firmware: BIOS) from RHV provider(with CA certificate) to remote Openshift Virtualization cluster, the migration executed successfully, the vm is created on target cluster, start vm, the vm is running on target cluster, test PASSED. More details: Step1: Create RHV provider with CA certificate, select the VM:  mt-win2019-79 and create the cold migration plan to migrate VM to remote cluster Step2: Check is migration plan succeeded, no error Step3: Start the VM, check the VM is running on target cluster

            chhu@redhat.com I was able to reproduce the issue in 4.17.0 but it passed in 4.17.1, could you please try again if it is still an issue?

            Martin Necas added a comment - chhu@redhat.com I was able to reproduce the issue in 4.17.0 but it passed in 4.17.1, could you please try again if it is still an issue?

            The validator message is quite clear: UEFI and BIOS are both set, but only one must be set.

            Fabian Deutsch added a comment - The validator message is quite clear: UEFI and BIOS are both set, but only one must be set.

              mnecas@redhat.com Martin Necas
              chhu@redhat.com Chenli Hu
              Chenli Hu Chenli Hu
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: