dertl: Did you ever figure something out for this?
I'm using one of the latest AWS Windows Server 2019 Hyper-V AMIs and am encountering the same error in the event log.
"Hypervisor launch failed; Either VMX not present or not enabled in BIOS."
In my case my end goal is really to run Linux Docker containers on Windows Server 2019 in an AWS EC2. (although in reality I really only care about building them)
Currently, you can only run nested virtualisation on a *.metal instance type. There's some documentation available here:
I have successfully managed to get a Windows Server 2019 Hyperv image up and running on an m5d.metal instance type, and launched a Windows Server 2016 guest OS on that.
Please note that only bare metal[1,2] EC2 instances provide direct access to cpu of the underlying server and its' features like Intel VT-x required to run your own hypervisor. The other types of instances does not expose the hardware requirements to install and run another virtualization layer on top of an EC2 instance which itself is a virtual machine.
Please let me know should you have any other questions or need assistance.
Introducing Five New Amazon EC2 Bare Metal Instances: https://aws.amazon.com/about-aws/whats-new/2019/02/introducing-five-new-amazon-ec2-bare-metal-instances/
Unable to Create a new Instance on a mac1 Dedicated Hostasked 8 months ago
Can't download to my EC2 windows instance through Internet Explorerasked a year ago
EC2 - Windows 2019 with containers: call service on hostasked 3 years ago
Error connecting to a Windows Server with Puttyasked a year ago
Nested Virtualization with HyperV on EC2 instanceasked 4 years ago
Install virtualization software on EC2Accepted Answerasked 5 years ago
EC2 Windows Server integrated with Docker (Linux)?asked 5 months ago
Nested virtualization on Gravitonasked 2 years ago
HyperV on Cluster migration supportasked 3 years ago
joining an ec2 instance to a customers network/domainasked 5 months ago