Done
RTNETLINK answers: Device or resource busy
++ fatal ip link set vif1.0 name 'tapc32a6b48-25 failed'
++ _xenstore_write backend/vif/1/0/hotplug-error 'ip link set vif1.0 name tapc32a6b48-25 failed' backend/vif/1/0/hotplug-status error
++ log debug 'Writing backend/vif/1/0/hotplug-error' 'ip link set vif1.0 name tapc32a6b48-25 failed' backend/vif/1/0/hotplug-status 'error to xenstore.'
++ local level=debug
++ shift
++ logger -p daemon.debug -- /etc/xen/scripts/vif-bridge: 'Writing backend/vif/1/0/hotplug-error' 'ip link set vif1.0 name tapc32a6b48-25 failed' backend/vif/1/0/hotplug-status 'error to xenstore.'
++ xenstore-write backend/vif/1/0/hotplug-error 'ip link set vif1.0 name tapc32a6b48-25 failed' backend/vif/1/0/hotplug-status error
++ log err ip link set vif1.0 name 'tapc32a6b48-25 failed'
++ local level=err
++ shift
++ logger -p daemon.err -- /etc/xen/scripts/vif-bridge: ip link set vif1.0 name 'tapc32a6b48-25 failed'
++ exit 1
Boris.
> Subject: Re: [Xen-devel] Ongoing issue with libvirt-xen driver for Openstack Nova
> From: ian.campbell@xxxxxxxxxx
> To: bderzhavets@xxxxxxxxxxx
> CC: anthony.perard@xxxxxxxxxx; xen-devel@xxxxxxxxxxxxx
> Date: Thu, 16 Apr 2015 10:27:09 +0100
>
> On Thu, 2015-04-16 at 05:14 -0400, Boris Derzhavets wrote:
>
> Please can you not top post.
>
> > Done
> >
> > /var/log/xen/xen-hotplug.log:-
> >
> > RTNETLINK answers: Device or resource busy
> >
> > Thank you.
>
> My usual technique for debugging these sorts of hotplug script issues is
> to insert near the top of vif-bridge:
> exec >> /tmp/hotplug.log 2>&1
> echo `date` running vif-bridge $@
> set -x
> I hope I recalled the syntax correctly. The "set -x" makes it quite
> noisy but gives pretty good clues.
>
> Ian.
>
