ESXi on Azure VM

omar adel 0 Reputation points
2026-10-14T18:24:24.39+00:00

Hello everyone,

I'm trying to install VMware ESXi 8.0 Update 3e as a nested hypervisor inside Hyper-V, which is running on a Windows Server VM in Microsoft Azure. However, the ESXi installation consistently gets stuck during boot at the following messages:

Shutting down firmware services

Using simple offset UEFI RTS mapping policy

Relocating module and starting up the kernel

The VM does not seem to progress beyond this point.

My environment:

Azure VM size: Standard F4ams v6

Azure VM resources: 4 vCPUs and 32 GiB RAM

Operating system: Windows Server with the Hyper-V role enabled

Nested VM name: ESXi1

Hyper-V VM generation: Generation 2

ESXi version: VMware-VMvisor-Installer-8.0U3e-24677879.x86_64

Memory assigned to the nested ESXi VM: 20,971,520,000 bytes (approximately 19.5 GiB)

Virtual processors assigned: 2

Dynamic Memory: Disabled

Secure Boot: Disabled

  • ExposeVirtualizationExtensions: True

Is it actually possible to have an EXSi running inside Azure?!

Azure Virtual Machines
Azure Virtual Machines

An Azure service that is used to provision Windows and Linux virtual machines.

0 comments No comments

Answer accepted by question author
Baraniwala Chamali Lalanthi Liyanage 0 Reputation points
2026-10-14T18:36:27.9666667+00:00

Hi Omar,

To answer your main question directly: No, it is not officially supported, and in practical terms, running ESXi as a nested hypervisor inside a Windows Hyper-V VM on Azure will not work.

Here is why you are getting stuck: While Azure VMs (like your Standard F4ams v6) absolutely support nested virtualization, Microsoft engineered this feature specifically to run Hyper-V inside Hyper-V (for Windows or Linux guest VMs).

VMware ESXi has incredibly strict hardware and CPU instruction requirements. It requires direct, low-level access to virtualization extensions (VT-x/AMD-V), specific hardware timers, and memory management units. Even though you correctly enabled ExposeVirtualizationExtensions in Hyper-V, the virtualized hardware presented by Azure's host > to your Windows Server > to Hyper-V > to ESXi lacks the exact hardware hooks the ESXi kernel needs to initialize. This is the exact reason it hangs indefinitely at the "Relocating module and starting up the kernel" step.

What are your alternatives?

Azure VMware Solution (AVS): If you need to run enterprise VMware workloads in Azure, Microsoft offers this service. It provides actual, dedicated bare-metal servers running VMware in Azure datacenters, bypassing nested virtualization entirely.

Local Labs: If you are just trying to build a learning lab, you will save yourself a lot of time by using a local physical PC with VMware Workstation, or a local bare-metal machine running ESXi, where nested VT-x features can be passed through natively.

It's a great experiment, but unfortunately, the Azure hypervisor abstraction layer just won't let ESXi boot!

Was this answer helpful?

1 person found this answer helpful.

0 additional answers

Sort by: Most helpful

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.