[Pkg-xen-devel] Feedback on merge of Xen-4.8.0

[Stefan Bader]

Hi Ian,

first thanks for picking up so many things in your upload. Unfortunately it took
me a while to merge this back into Ubuntu. So it is a bit late for the feedback
but I hope it still helps a bit.

Sadly I think that by picking up the grub default file, you picked up some
trouble. It is not the contents but the packaging. Logically it belongs to the
hypervisor, but that is versioned in Debian to be able to have 2 versions
installed in parallel. But that breaks now with the same config file being in
both. I get away with that in Ubuntu because we do support only one version
installed and I add transitional hypervisor packages. I believe the right move
would be to have a xen-hypervisor-common but am not sure how one would make a
safe transition there. Maybe together we can work something out.

Other than that, there are two (and maybe a haf) things that might be beneficial
for Debian:

1. Users have noticed with Ubuntu's Xen-4.7 (still true with 4.8) that some
   tools (mainly gdbsx, but also some flask-* commands) are missing from the
   xen-utils-4.x package. This is because those end up outside the libexec
   path. The attached diff fixes this (a bit hackish) by simply copying all
   those into usr/lib/xen-$(VERSION)/bin/

2. Splitting up xen.init. Initially driven by systemd in Ubuntu trying to
   unmount everything on shutdown/reboot. And with xenstore still running
   this would always lead to error messages. So I split the init scripts
   into a xenstore.init and xen.init part. The additional benefit is that
   this allows to separate the init scripts clearly into one that is re-
   started on upgrade (xen.init) and one which is not (xenstore.init). And
   both parts will stop on shutdown/reboot allowing xenfs to be unmounted.
2.5 Part of those script split is some adjustments to the LSB headers. Most
   importantly the reference to libvirtd. The became important because in
   Ubuntu (maybe now also true in Debian) the helpers that create the sysv
   init S/K-script links ignore the numbers passed in by dh_installinit and
   now re-number everything based purely on the dependencies defined. So we
   had the problem that libvirtd would potentially be starting in parallel
   with Xen, leading to cases where libvirt would not detect the hypervisor.

-Stefan


-------------- next part --------------
A non-text attachment was scrubbed...
Name: maybe4debian.diff
Type: text/x-patch
Size: 8356 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-xen-devel/attachments/20170125/11508937/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-xen-devel/attachments/20170125/11508937/attachment.sig>