Hi all,
this patch series changes libxl to start QEMU as device model with the
new xsrestrict option (http://marc.info/?l=xen-devel&m=143341692707358).
It also starts a second QEMU to provide PV backends in userspace (qdisk)
to HVM guests.
Changes in v4:
- update xenstore-paths.markdown
- add error message in case count > MAX_PHYSMAP_ENTRIES
- add a note to xenstore-paths.markdown about the possible change in
privilege level
- only change permissions if xsrestrict is supported
Changes in v3:
- use LIBXL_TOOLSTACK_DOMID instead of 0 in the commit message
- update commit message with more info on why it is safe
- add a limit on the number of physmap entries to save and restore
- add emulator_ids
- mark patch #3 as WIP
- use LIBXL_TOOLSTACK_DOMID instead of 0 in the commit message
- change xs path to include the emulator_id
- change qdisk-backend-pid path on xenstore
- use dcs->dmss.pvqemu to spawn the second QEMU
- keep track of the rc of both QEMUs before proceeding
Stefano Stabellini (6):
libxl: do not add a vkb backend to hvm guests
[WIP] libxl: xsrestrict QEMU
libxl: allow /local/domain/$LIBXL_TOOLSTACK_DOMID/device-model/$DOMID to
be written by $DOMID
libxl: change xs path for QEMU
libxl: change qdisk-backend-pid path on xenstore
libxl: spawns two QEMUs for HVM guests
docs/misc/xenstore-paths.markdown | 30 ++++++++--
tools/libxl/libxl.c | 2 +-
tools/libxl/libxl_create.c | 58 +++++++++++++------
tools/libxl/libxl_device.c | 2 +-
tools/libxl/libxl_dm.c | 115 +++++++++++++++++++++++++++++++++----
tools/libxl/libxl_dom.c | 19 ++++--
tools/libxl/libxl_internal.c | 19 ++++--
tools/libxl/libxl_internal.h | 15 ++++-
tools/libxl/libxl_pci.c | 14 ++---
tools/libxl/libxl_utils.c | 10 ++++
10 files changed, 225 insertions(+), 59 deletions(-)
Cheers,
Stefano
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
