Hi Mohamed, On 18.02.26 04:27, Mohamed Mediouni wrote:
On 18. Feb 2026, at 02:51, Alexander Graf <[email protected]> wrote:Add a machine model to spawn a Nitro Enclave. Unlike the existing -M nitro-enclave, this machine model works exclusively with the -accel nitro accelerator to drive real Nitro Enclave creation. It supports memory allocation, number of CPU selection, both x86_64 as well as aarch64, implements the Enclave heartbeat logic and debug serial console. To use it, create an EIF file and run $ qemu-system-x86_64 -accel nitro,debug-mode=on -M nitro -nographic \ -kernel test.eif or $ qemu-system-aarch64 -accel nitro,debug-mode=on -M nitro -nographic \ -kernel test.eif Signed-off-by: Alexander Graf <[email protected]>Hi, The separation between -M nitro and -M nitro-enclave looks potentially confusing to users. Could it potentially make sense to share the name or is that an option not on the cards?
I originally built all of this inside the nitro-enclave machine, but that turned out super awkward as well, because its complete initialization is different. The nitro-enclave machine is derived from the MicroVM machine type, which is not at all what we need for the accel based variant. And on top of that makes it super difficult to enable aarch64 support.
So I opted to go with the separate machine name instead. Alex Amazon Web Services Development Center Germany GmbH Tamara-Danz-Str. 13 10243 Berlin Geschaeftsfuehrung: Christof Hellmis, Andreas Stieger Eingetragen am Amtsgericht Charlottenburg unter HRB 257764 B Sitz: Berlin Ust-ID: DE 365 538 597
