Skip to content

TODO Buster

Ian

Documentation things:

  • NEWS.Debian: write some text about meltdown/spectre

Important Buster issues:

  • Talk to release team about getting Xen 4.12 in Buster, so another half a year of security support upstream. There aren't many disrupting changes, and all the work listed on the rest of this page is still relevant.
  • Otherwise, we might want to ship 4.11.2~pre.2019MMDD.0123456789-1 at next upload?
  • 912381 pygrub is borken
  • 862236 architecture dependent path in common package
  • 921187 QEMU package still depends on libxenmisc4.11 which complicates doing buster-backports
  • 851654 Change init script in xen-utils-common to stop issuing start/stop init commands if it's called by a xen-utils-4.X pre/post script and the running Xen version is different than the util package version. This solves xenconsoled being stopped when removing xen-utils-4.old after upgrade. However, there seem to be more weird hard to reproduce cases in which xenconsoled disappears. Maybe ask users to report ASAP if this happens so we can ask for logs etc? :|
  • 798510 xendomains init script should depend on network, race condition
  • 826871 domU with disk on NFS fails to stop because NFS connection is shut down before stopping domU
  • Improve error message "[warn] Not running within Xen or no compatible utils ... (warning).", but maybe if a xen-utils-X other than the running hypervisor is doing inst/rm scripts, just don't say anything at all? The reported problem here was aptitude full-upgrade which already did autoremove and the message was actually correct in that case?
  • We ship /etc/default/xen again, but the packaging has complicate machinery to get rid of it. Woops! Also, all our other conffiles are also not managed by ucf? Do we want to choose some standard consistent way of doing things here?

Other / Nice to have / Later:

  • 922033 Ship driver domain init script (also, FTR, don't ship watchdog) <- Bug submitter wants to help testing domU side!
  • 909667 This can be closed I guess?

Actually for Stretch, but we also discussed this one:

  • 900746 segfaults on hardware with AVX

Hans

Documentation stuff:

  • #25 File bug against release-notes to ask for including Xen information.
  • NEWS.Debian: write some text about PVH + grub
  • README.Debian: write some text about reporting bugs, to set expectations. This should include the standard text that we can use to reply on new bugs about upstream problems.
  • README.Debian: include "known issues" section, about e.g. 880554 max frames, 821254 xendomains timeout because systemd wrapper.
  • Look what Xen related stuff is on wiki.debian.org, send a mail to the list about cleaning up.

Important Buster issues:

  • 768005 Ship improved version
  • Test /etc/default/grub.d/xen functionality to generate different console= with/without Xen.
  • Switch to ocaml xenstored
  • Ship interesting content in /etc/default/xen. See upstream sysconfig.xencommons.in, and remove everything stubdom related. Hm, this also means making sure init script DTRT, e.g. providing option to switch between xenstored and oxenstored? Note: apparently we had /etc/default/xen before and it's abandoned, so it's good we replace it with something again? Also, if extra options can be set for XENSTORED, then they also need to be applied in the init script...
  • Ask for more info on 903494. "If I do something, the behavior is more weird" style report is not something we can work with.
  • 866380 xen-bugtool does seem to use some python lib which does not exist at all any more, upstream PATCH to remove it?
  • 506407 Close this one, it's by design that xenstored is never stopped. It needs to be kept running because it has in-memory state. Also, xenconsoled is properly stopped/started nowadays (ahem).

Upstream stuff:

  • 768005 Have bash completion patch sent upstream.
  • salsa issues #23 #22 shlibs dependencies: send make file patches upstream to reduce warnings here

For later, init scripts

  • Merge Debian and upstream init scripts, discuss with upstream. E.g. use lsb log_message_progress_blah.
  • Actually ship systemd units.
  • 920221 Think of selinux users when adding systemd unit thingies.
  • 821254 xendomains systemd stuff
Edited by Hans van Kranenburg