Unfortunately even your solution isn't immune to vulnerabilities, as kvm can be leveraged to gain access to the host by means of exploits like Januscape (CVE-2026-53359) or Zapscape (CVE-2026-64561).
A more secure option would be to avoid kvm completely and just run the container under an isolated kernel space using mklinux. The other advantage of mklinux is performance, there's no virtualisation tax to pay. See: https://lore.kernel.org/lkml/ao34RJ7aZ2BLd67S@pop-os.localdo...
Unfortunately even your solution isn't immune to vulnerabilities, as kvm can be leveraged to gain access to the host by means of exploits like Januscape (CVE-2026-53359) or Zapscape (CVE-2026-64561).
A more secure option would be to avoid kvm completely and just run the container under an isolated kernel space using mklinux. The other advantage of mklinux is performance, there's no virtualisation tax to pay. See: https://lore.kernel.org/lkml/ao34RJ7aZ2BLd67S@pop-os.localdo...
Nice work!
[dead]