Package: xen-utils-common Version: 4.4.1-9+deb8u1 Severity: important Dear Maintainer,
After upgrading to Debian 8, auto-starting of domUs via /etc/xen/auto fails with errors like this Sep 09 09:29:21 host xendomains[948]: Starting Xen domain domU (from /etc/xen/auto/domU.cfg)...failed. Sep 09 09:29:21 host xendomains[948]: libxl: error: libxl_exec.c:129:libxl_report_child_exitstatus: /etc/xen/scripts/block add [-1] died due to fatal signal Killed Sep 09 09:29:21 host xendomains[948]: libxl: error: libxl_exec.c:129:libxl_report_child_exitstatus: /etc/xen/scripts/block add [-1] died due to fatal signal Killed Sep 09 09:29:21 host xendomains[948]: libxl: error: libxl_exec.c:129:libxl_report_child_exitstatus: /etc/xen/scripts/block add [-1] died due to fatal signal Killed Sep 09 09:29:21 host xendomains[948]: libxl: error: libxl_create.c:1054:domcreate_launch_dm: unable to add disk devices Services seem to get started in the correct order according to LSB headers in the init scripts: Sep 9 09:28:49 host systemd[1]: Starting LSB: Xen daemons... Sep 9 09:28:49 host xenstored: Checking store ... Sep 9 09:28:49 host xenstored: Checking store complete. Sep 9 09:28:49 host xen[880]: Starting Xen daemons: xenfs xenstored xenconsoled init-dom0. Sep 9 09:28:49 host systemd[1]: Started LSB: Xen daemons. Sep 9 09:28:49 host systemd[1]: Starting LSB: Start/stop secondary xen domains... Inserting a 'sleep 10' into /etc/defaults/xendomains solves the issue, so it seems to be some timing problem. Cheers Wolfgang