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.
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)
Re:Xen hypervisor memory corruption due to x86 emulator flaw
by rwmj on Tuesday March 10, 2015 @01:18PM
(#9178989)
My guess would be a couple of things: small Xen hypervisor vs potentially large Linux kernel, and driver domains. The latter involves putting each driver into its own domain (ie. Xen VM or process equivalent) and it means that bad drivers can do less damage to the rest of the system.
Does anyone know why KVM would be considered less secure than Xen?