3 ms·
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. I
by rwmj 8y ago
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 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/ https://www.qemu-advent-calendar.org/2016/
Edit 2: Don't confused nested KVM with nesting TCG. That's fine, albeit rather slow.
- andrewstuart 8y ago>> ability to crash the L0 hypervisor Prove it and you'll get a bug bounty from Doogle and Microsoft won't you?
- rwmj 8y agoWhy 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.