upvote
KVM maintainer here. On one hand it's true that nested is the single biggest attack surface in the hypervisor, on the other hand it will be over relatively soon. Considering the LLMs have ~15 years of nested virtualization to catch up with, it's not in an awful state. These bugs are extremely complicated to exploit, which means that the past ten years of fuzzing with syzkaller have already found the low hanging fruit.
reply
Certain Windows features need it unfortunately. Virtualization-Based Security (VBS), Credential Guard, Hyper-V (obviously), and I'm going to say WSL2(?)
reply
Right, sorry, that's a fair point (and Josh Triplett made another fair point earlier). I'm sort of implicitly locked in to the "hosting company" use case here: services running mutually-untrusting isolated workloads for customers.
reply