-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On Tue, Sep 06, 2016 at 12:38:59AM -0700, Jan Betlach wrote:
> Looks like Open BSD implemented Xen PHVM drivers in 6.0. How exactly does it help to run OpenBSD guest in Qubes?
PHVM drivers itself (disk/net) simply improve performance. But based on
this (or rather some parts used by those drivers), it is possible to
build drivers exposing some xen interfaces to user space, which allows
porting Qubes-specific integration.
Those drivers are required to port:
- qrexec agent (used to control VM from dom0 - for example start
applications - mostly qvm-run tool
- gui agent (seamless GUI integration)
Both of them use libxenvchan library, which itself rely on shared memory
interface and even channels. On Linux this is about those drivers:
- xen-gntalloc
- xen-gntdev
- xen-evtchn
I haven't read what parts are really implemented in Open
BSD. "Xen PHVM drivers" is rather broad term - may include just a
disk/network drivers, or just kernel part - without exposing it to
userspace. Release notes include only this:
"The xen(4) driver now supports domU configuration under Qubes OS.",
which links to:
xen driver performs HVM domU guest initialization, provides
abstraction for virtual Xen interrupts, access to the XenStore
configuration storage as well as a device probing facility for
paravirtualized devices such as disk and network interfaces.
So, it looks promising. But don't know if that's all what is required.
- --
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQEcBAEBCAAGBQJXzp+GAAoJENuP0xzK19csLjAH/jW6KRs0cASgFbRVOcJR10Q3
vjzWhZyf60aPRBOM/izOVUExbmmVtjtmQ4JIpoTplXYfTVAqHhiIqvWT7GzhotIP
20JUCV8SjrvLNYCGl7CKIRuiOVUx85tdM3OIZBcqexL+Z/YpFX40odpkIlAY9nax
PM+gGzCEsSe9FjnZUma6nA4h5iJ8Jz7tcHm83NJywcF9UR9BFeRs21n224xCqWQX
23PrRNaKyEHshI/5WHUx9ImDIPNliHC9H+DerMWQzphOtivNCwKvcJ8AteImKW/H
7w4lXQ7wJEX9eyZQGwKuNz/FozVZNfxIwGvpz18vZvZVk0VTUwd5b1iIwiOmQZI=
=qzuF
-----END PGP SIGNATURE-----