VMware Migration to HPE VME Boot error (appliance using legacy boot)

[specfiedinfo]

Multiple VM's migrated to HPE VM that are using legacy boot (appliance based) was unable to boot in the HPE VME. VME instance settings are very generic. Is there an option to select and set VM boot option to BIOS instead of UEFI after the migration as this appliance unable to boot using UEFI. 

[dccolpitts]

I actually did some testing on this last week under 8.0.8.  While it is possible to accomplish, this is very unsupported by the VME team as you need to manually edit the .xml definition file (which they do not support).  That said, I'm guessing you don't care and just want your VM to boot...

Please note:  Use any tips, tricks, or scripts I post at your own risk.

From the HVM host console that hosts the VM, ensure the VM is shut off and then run:    virsh edit VMNAME

(Note - VMNAME is case-sensitive throughout these instructions)

Approximately 24 lines down, you will see the following two sections for <os> and <features> (if the VM is UEFI based):

<os>
   <type arch='x86_64' machine='pc-q35-8.2'>hvm</type>
   <loader readonly='yes' secure='yes' type='pflash'>/var/morpheus/kvm/OVMF_MVM.fd</loader>
   <nvram template='/var/morpheus/kvm/OVMF_VARS.fd'>/var/lib/libvirt/qemu/nvram/VMNAME_VARS.fd</nvram>
   <bootmenu enable='no'/>
   <smbios mode='sysinfo'/>
</os>
<features>
   <acpi/>
   <apic eoi='on'/>
      <hyperv mode='custom'>
      <relaxed state='on'/>
      <vapic state='on'/>
      <spinlocks state='on' retries='8191'/>
      <vpindex state='on'/>
      <synic state='on'/>
      <stimer state='on'/>
   </hyperv>
   <smm state='on'/>
</features>

To convert this VM to BIOS based, delete the following two lines from <os>:

   <loader readonly='yes' secure='yes' type='pflash'>/var/morpheus/kvm/OVMF_MVM.fd</loader>
   <nvram template='/var/morpheus/kvm/OVMF_VARS.fd'>/var/lib/libvirt/qemu/nvram/VMNAME_VARS.fd</nvram>

Also delete the following line from <features>:

   <smm state='on'/>

To delete lines in virsh edit, you can just put your cursor on the line to delete and press the letter d twice quickly.  To save the configuration in virsh, press Esc, : (colon), and enter wq! and hit enter.  Assuming you did not mess the editing up, the file will save.  If you see "Failed. Try again? [y,n,i,f,?]", then press N to completely discard the changes you made and start again.  Pressing Y will take you back to the configuration with your changes still present, but unless you know exactly what you did wrong, I do not recommend doing this.

Remove the now unrquired NVRAM file:   rm /var/lib/libvirt/qemu/nvram/VMNAME_VARS.fd

Now you should be able to start your VM  (virsh start VMNAME)

If need to convert from BIOS to UEFI, use the same method, except in virsh edit, press the letter i (eye) to enter insert mode and update the <os> and <features> sections to mirror above.  Take note that you need to update the NVRAM file name, and then back in the console will you need to:

cp /var/morpheus/kvm/OVMF_VARS.fd /var/lib/libvirt/qemu/nvram/VMNAME_VARS.fd

Then you should be able to start your VM.

dcc

[specfiedinfo]

Hi @dccolpitts ,

I already check the xml, which the migrated appliance based on Rocky linux don't have and have experienced editing this on other kvm solution. I just followed the migration procedure based on the version 8 documentation which uses the migration tool. Migrating the linux quite straight forward and i have a working ubuntu using the migration tool but this appliance still does not boot and unable to recognize bootable device.

[mattie236]

---

@specfiedinfo hha exchangewrote:

Multiple VM's migrated to HPE VM that are using legacy boot (appliance based) was unable to boot in the HPE VME. VME instance settings are very generic. Is there an option to select and set VM boot option to BIOS instead of UEFI after the migration as this appliance unable to boot using UEFI. 

---

Yes, you can change the VM's boot mode in HPE VME. The issue you're facing, where legacy-boot VMs fail to start after migration, is common because the destination hypervisor often defaults to UEFI mode. To fix this, simply access the VM's settings within the HPE VME management interface, find the **Boot Options** or **Firmware** section, and change the setting from **UEFI** to **BIOS** or **Legacy Boot**. After saving the changes and rebooting the VM, it should boot correctly.

[specfiedinfo]

Hi @mattie236 ,

Can you share screenshot on this option ? I have not found that VM options like VMware since doing testing in instance VME Management UI.