No written verdict yet. Here is what commenters said.

5recommend
1warn against
Dec 30, 2025first mention
Sep 13, 2026latest mention
Nov 25 – Oct 26
Used forpci passthrough in qubeshypervisor

Why people recommend it

“ripping off the best ideas from xen/Qubes”

“was running Xen happily more than two decades ago”

Show 3 more

“the attack surface of the Xen hypervisor itself is fairly minimal”

“We've had this in Xen since forever!”

“high-quality practical implementations [2]”

Caveats and dissent

No one in these comments warned against it.

Often compared with

All comments 12

> Honestly, I wish there was a Qubes/KVM variant. Relayed Issue: https://github.com/QubesOS/qubes-issues/issues/7051

“They use Xens pci passthrough, you can setup a pci device to be assigned to a vm.”

“ripping off the best ideas from xen/Qubes”

“was running Xen happily more than two decades ago”

“It is more secure than Xen, which it relies on”

“the attack surface of the Xen hypervisor itself is fairly minimal”

“Then they talked Xen, which at least has a security boundary. Now everybody switched to kvm with none.”

“We've had this in Xen since forever!”

You know that Xen is just a hypervisor right? Dom0 (the admin Qube) is running the Linux kernel and is vulnerable like any other Linux system. DomU (App Qubes) also run the Linux kernel and are just as vulnerable. You can check your DomU kernels using this guide: https://doc.qubes-os.org/en/latest/user/advanced-topics/managing-vm-kernels.html If your Dom0 or DomU is running kernel < 6.18.22, or between 6.19.0 and 16.

“I used to run Xen back in the early hardware-virt days”

“high-quality practical implementations [2]”

Threads where it came up

Data: xen.json. Quotes are verbatim; the verdict and theme labels are written by a model from these comments, and every clause links to its sources.

Keyboard shortcuts
j / kNext / previous item
o or EnterOpen selected item
/Search
g hHome
g tTop
g rRising
g cCategories
tToggle dark mode
?This help