Source: xen Severity: normal Dear Maintainer,
Driver domain running Debian buster does not work, because
xendriverdomain service is missing. Upstream xen have
/etc/init.d/xendriverdomain (and equivalent xendriverdomain.service)
that starts `xl devd` process responsible for setting up backend
devices.
Source package contains related comment in debian/not-installed:
# It is not clear why we have our own init scripts etc. in Debian.
# We should probably transition to using the upstream ones and
# fix any bugs we encounter.
etc/init.d/xendriverdomain
etc/init.d/xencommons
etc/init.d/xen-watchdog
etc/init.d/xendomains
etc/default/xencommons
I think this should be fixed exactly this way - switch to upstream
startup scripts, instead of Debian-specific ones.
Also, upstream provide systemd startup files.
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 4.14.74-1.pvops.qubes.x86_64 (SMP w/2 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
--
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?
signature.asc
Description: PGP signature
