topic Cannot boot new VM when migrate from VMware to HPE VM Essentials Software cluster in HPE Morpheus VM Essentials Software

Cannot boot new VM when migrate from VMware to HPE VM Essentials Software cluster

tungxp — Wed, 10 Sep 2025 05:20:33 GMT

We have just migrate our RHEL 8.8 from ESXi 8 - vCenter 8 to HPE VM Essentials Software cluster but the new VM stuck at booting.

We followed HPE VM Essentials Software migration guide.

Below is our configuration:

Virtual Image:

New instance configure:

Re: Cannot boot new VM when migrate from VMware to HPE VM Essentials Software cluster

dccolpitts — Mon, 08 Sep 2025 11:18:10 GMT

Couple of things I see. First your screenshots seem to show you are creating new VM, as opposed to having migrated one from VMware to VME (which is what you stated you did). Second, why is nestled virtualization checked - is your HVM host virtualized as well?

Was your VM configured for BIOS or UEFI under VMware? That's my initial guess, that it was previously set to UEFI and is was migrated as BIOS based. The process for converting was covered last week in a different thread here, or you can go look at my blog post where I detail it as well: https://blog.jbgeek.net/2025/09/04/howto-convert-a-hpe-vme-vm-from-uefi-to-bios-and-back/

dcc

Re: Cannot boot new VM when migrate from VMware to HPE VM Essentials Software cluster

tungxp — Tue, 09 Sep 2025 02:33:42 GMT

Thank you for your reply, dccolpitts

We followed HPE VM Essentials Software migration guide (page 21), it guides us "Deploy an HPE VM instance type using the virtual image created" .

We also try to uncheck nestled virtualization but nothing change.

Here is our XML configuration for new VM:

We see that our source VM using EFI as screenshots below:

So we try to followed your guide convert from BIOS to UEFI by add some line as below:

<os> <type arch='x86_64' machine='pc-i440fx-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/New_HVM_Instance_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>

but it show error:

error: unsupported configuration: Secure boot is supported with q35 machine types only Failed. Try again? [y,n,f,?]:

we couldn't save that configuration

How to solve that? Thank you !

Re: Cannot boot new VM when migrate from VMware to HPE VM Essentials Software cluster

jimy395nue — Thu, 11 Sep 2025 04:24:08 GMT

Hello,

Have you confirmed that the VM’s hardware compatibility settings (CPU, RAM, virtual NIC, etc.) match the requirements?

Re: Cannot boot new VM when migrate from VMware to HPE VM Essentials Software cluster

Arnout_Verbeken — Wed, 10 Sep 2025 15:11:48 GMT

You are using the "old migration method" which had some flaws.

You should upgrade/install VME 8.0.9 and use the new Migration Tool under "Tools".

The new migration whitepaper can be found here:

https://www.hpe.com/psnow/doc/a50013873enw?from=app%C2%A7ion=search&isFutureVersion=true

Re: Cannot boot new VM when migrate from VMware to HPE VM Essentials Software cluster

tungxp — Thu, 11 Sep 2025 07:04:57 GMT

Thank you Arnout_Verbeken

Finally we found out our mistake was loading the missing vioscsi.inf driver. In the "HPE Morpheus VM Essentials Software Migration Guide 8.0.8" guide there is only viostor.inf, in the "HPE Morpheus VM Essentials Software Migration Guide 8.0.9" guide there is an additional vioscsi.inf file. We have removed both drivers and the windows has been migrated successfully.

Thanks to the HPE support team and everyone

Re: Cannot boot new VM when migrate from VMware to HPE VM Essentials Software cluster

victor-mx — Thu, 09 Oct 2025 23:35:58 GMT

Hello,

Based on the migration file, check the supported OS versions.
For example, for Windows, it mentions that it is 2022 or later, which means that migrating VMs from earlier versions is not possible, or if it is possible, it is not supported.

I hope you can help me with this question. Based on your experience.