- 최신
- 최다 투표
- 가장 많은 댓글
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.
Thank you for answering this.
If my understanding is correct, ARMv8.3 or above has a support of nested virtualization in architecture level while Intel requires optional CPU feature, VT-x. It sounds to me that the answer of a post below implies nested virtualization would be available once Graviton has ARMv8.3 or above architecture. These are why I had a hope of running VM on a non-metal Graviton instance. Nested virtualization on Graviton, https://repost.aws/questions/QUEoabj2ZERq2P5QFL6d6-RQ/nested-virtualization-on-graviton
The answer is no, EC2 VMs do not support nested virtualization for any architecture. To run your own hypervisor on EC2, you have to use *.metal instances. From there you could do nested virtualization, but at that point there's no need as you have the entire machine to work with.
Thank you for clarifying the conclusion. We have a concrete reason to need nested VMs running on EC2. Hopefully AWS will continue to provide a1.metal for a long time as it's relatively reasonable price among all metal instances.
What are you trying to accomplish? If you want to run ARMv7 user space, you could use a container, as recommended in this question: https://repost.aws/questions/QU1e3ZeCmARWO1CMLTRrZA2Q/is-it-possible-to-import-a-debian-armhf-32-bit-arm-qemu-vm-and-run-it-on-a-t4g-small-graviton-instance
We need to use QEMU based virtual machine to run another ARMv8 system on it.