Re:Xen hypervisor memory corruption due to x86 emulator flaw
by detaro on Tuesday March 10, 2015 @01:22PM
(#9179041)
(from memory, there are some design docs for Qubes OS floating around that discuss this) Xen is relatively small and contained, KVM sits on top of a full Linux kernel and potentially can access all of it, making it harder to tell what is accessible/exploitable and what is not. KVM also uses Qemu running as a process on the host linux for interfacing the VM, again exposing more potential attack surface. And I think Xen is better at isolating drivers, which for Qubes OS is a fundamental principle.
[ Parent
| on HN ]
Re:Xen hypervisor memory corruption due to x86 emulator flaw
by cthalupa on Tuesday March 10, 2015 @11:53PM
(#9182504)
>And I think Xen is better at isolating drivers
Xen allows for creating an entire stub domU solely for running the driver, then giving a running guest access via ring buffer in a shared memory segment.
(So, yep, you're correct in your thinking)