[Pkg-xen-devel] Bug#798510: Bug#798510: xen-utils-common: xendomains domU auto-starting fails after upgrade to Debian 8

[Francois Lesueur]

Hi,

I face a very similar bug since I upgraded to stretch, but related to
network bridges :

xendomains[1361]: libxl: error:
libxl_device.c:1225:device_hotplug_child_death_cb: script: Could not
find bridge device brdmz

It of course works well when I launch domus after boot. Seems that
networking bridges are not up when xendomains start.

In my case, adding a dependency on $network in /etc/init.d/xendomains
seems to solve this issue. Should this dependency be added in the
package or do you think it will introduce other problems ?

Cheers,
Francois



On Thu, 12 Nov 2015 18:10:26 +0100 Wolfgang Karall-Ahlborn
<lists+debian-bugs at karall-edv.at> wrote:
> Hi Ian,
> 
> On 15-11-05 10:43:56, Ian Campbell wrote:
> > I suppose these domains all start just fine by hand, because the race
> > is well over by then...
> 
> Indeed they do.
> 
> > 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
> 
> Specifically xen-hotplug.log isn't modified at all, it's actually pretty
> old while both the dom0 and also the domU were restarted a couple of
> times today.
> 
> -rw-r--r-- 1 root adm    6735 Sep  9 10:13 xen-hotplug.log
> 
> The domU log files in /var/log/xen only seem to contain the shutdown
> sequences, all start with lines like
> 
> Waiting for domain test-inetng1 (domid 1) to die [pid 1336]
> 
> but nothing related to the start of the domU.
> 
> > What does the disk configuration look like in domU.cfg?
> 
> $ sed -n '/^disk/,/]/p' /etc/xen/test-inetng1.cfg
> disk        = [
>                   'phy:/dev/inetng1/test-inetng1-disk,xvda2,w',
>                   'phy:/dev/inetng1/test-inetng1-swap,xvda1,w',
>                   'phy:/dev/inetng1/test-inetng1-data,xvdb,w',
>               ]
> 
> > 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.
> 
> I've changed it to
> 
>   out=$(xen -vvv create --quiet --defconfig "$file" 2>&1 | ts "%b %d %H:%M:%.S" 1>/tmp/xendomains.$(basename $file).log)
> 
> to get some timestamps into the log with the help of moreutil's ts.
> 
> Also, I've added
> 
>   exec 5>> /tmp/xen-script-block-$1-$$.log
>   BASH_XTRACEFD="5"
>   PS4='+ \011$(date "+%b %d %H:%M:%S.%N"): $LINENO: '
>   set -x
> 
> to the top of the helper script in /etc/xen/scripts/block.
>