| ▲ | JoshTriplett 2 hours ago | |||||||||||||||||||||||||||||||||||||||||||||||||
> I have yet to hear a compelling use case for nested virtualization. AWS instances are slow to launch; they take whole seconds. Nested virtualization allows running something like firecracker/crosvm/rust-vmm atop a normal AWS instance, without needing a bare-metal one. | ||||||||||||||||||||||||||||||||||||||||||||||||||
| ▲ | tptacek 2 hours ago | parent [-] | |||||||||||||||||||||||||||||||||||||||||||||||||
If you're segregating internal workloads, by all means use nested virtualization on EC2 or DO or something. Your threat model is different and you probably have a lot more room to maneuver when a KVM escape is announced, because you have some level of trust in all your workloads. If you're running multitenant for mutually-untrusting customers, that excuse goes out the window. | ||||||||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||||||||