On Thu, 2015-09-10 at 09:06 +0200, Wolfgang Karall-Ahlborn wrote: > 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
I suppose these domains all start just fine by hand, because the race is well over by then... Do you get anything further under /var/log/xen when this occurs? In particular the xl files associated with the domain and /var/log/xen/xen-hotplug.log What does the disk configuration look like in domU.cfg? It would also be useful to edit /etc/init.d/xendomains to change: out=$(xen create --quiet --defconfig "$file" 2>&1 1>/dev/null) to out=$(xen -vvv create --quiet --defconfig "$file" 2>&1 1>/dev/null) (adding -vvv before create) and maybe replace /dev/null with something like /tmp/xendomains.$(basename $file).log Hopefully something in there will give us some clue what is not ready yet. > 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. Whereabouts? Near the start I guess. Ian. >