News for hackers. Stuff that matters.
Re:The Firecracker virtual machine monitor by rwmj on Friday January 04, 2019 @03:41AM (#18822704)
Nested KVM has been buggy since forever. Although a wonderful thing when it's working I'm not surprised Amazon doesn't allow it on their production systems. It has a nasty combination of: ability to crash the L0 hypervisor, different behaviour depending on features and family of the processor, and requiring very specialized skills to understand and debug.

Edit: If you do want to try testing nested KVM, then try my supernested project: http://git.annexia.org/?p=supernested.git;a=summary and Day 13 of the 2016 QEMU Advent Calendar https://www.qemu-advent-calendar.org/2016/

Edit 2: Don't confused nested KVM with nesting TCG. That's fine, albeit rather slow.

Re:The Firecracker virtual machine monitor by andrewstuart on Friday January 04, 2019 @03:56AM (#18822760)
>> ability to crash the L0 hypervisor

Prove it and you'll get a bug bounty from Doogle and Microsoft won't you?

Re:The Firecracker virtual machine monitor by rwmj on Friday January 04, 2019 @04:06AM (#18822786)
Why would Microsoft be interested? (no idea what "Doogle" is - do you mean Google? Why would they care about nested KVM?) Anyway when I find bugs in nested KVM I have reported them to the kernel developers or QEMU in the usual way and help any way I can to get them fixed.