[Xen-devel] [PATCH v2 0/5] Fix QEMU startup protocol

[Wei Liu <wei.liu2@xxxxxxxxxx>]

This patch series tries to reason about various hardcoded "/local/domain/0" in
libxl and 1) replace them with something sensible, 2) fix QEMU startup
protocol.

Please apply a patch to QEMU traditional first, squash the update to Config.mk
into "libxl: use new QEMU xenstore protocol" to keep the tree bisectable.

The new protocol is introduced in "libxl: use new QEMU xenstore protocol".
Basically it replaces hardcoded "/local/domain/0" with
"/local/domain/$dm_domid".

For both QEMU upstream and traditional running in Dom0, the new protocol is
compatible with the old one, because in those cases $dm_domid is 0.

For QEMU traditional running in stubdom, this protocol is incompatible with
old one. However this is acceptable because we always ships QEMU traditional
with Xen. For Xen 4.5 we should backport Paul's workaround.

For QEMU upstream running in stubdom, there is no compatibility issue because
there is no QEMU upstream stubdom yet. This patch series is also a good start
to avoid making the same mistake in QEMU upstream stubdom.

Wei.

Wei Liu (5):
  libxl: introduce libxl__device_model_xs_path
  libxl: remove device model path in libxl__device_model_destroy
  libxl: use LIBXL_TOOLSTACK_DOMID
  libxl: use new QEMU xenstore protocol
  Revert "x86/hvm: wait for at least one ioreq server to be enabled"

 tools/libxl/libxl.c              |  6 ++---
 tools/libxl/libxl_device.c       |  4 ++-
 tools/libxl/libxl_dm.c           | 55 +++++++++++++++++++++++++++++++++++++---
 tools/libxl/libxl_dom.c          | 54 ++++++++++++++++++++++++---------------
 tools/libxl/libxl_internal.c     | 22 ++++++++++++++++
 tools/libxl/libxl_internal.h     |  5 ++++
 tools/libxl/libxl_pci.c          | 22 ++++++++--------
 xen/arch/x86/hvm/hvm.c           | 21 ---------------
 xen/include/asm-x86/hvm/domain.h |  1 -
 9 files changed, 130 insertions(+), 60 deletions(-)

-- 
1.9.1


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel