From mboxrd@z Thu Jan 1 00:00:00 1970 From: Boris Derzhavets Subject: Re: Ongoing issue with libvirt-xen driver for Openstack Nova Date: Thu, 16 Apr 2015 06:26:45 -0400 Message-ID: References: , , <20150415154854.GF1707@perard.uk.xensource.com>, , <1429176429.25195.55.camel@citrix.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="_3053fab3-304b-4177-a043-ee4a02ffef32_" Return-path: In-Reply-To: <1429176429.25195.55.camel@citrix.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: "anthony.perard@citrix.com" Cc: "ian.campbell@citrix.com" , "xen-devel@lists.xen.org" List-Id: xen-devel@lists.xenproject.org --_3053fab3-304b-4177-a043-ee4a02ffef32_ Content-Type: multipart/alternative; boundary="_cf790d66-c0c3-4888-b9bc-ee469f7414c7_" --_cf790d66-c0c3-4888-b9bc-ee469f7414c7_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable 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 t= apc32a6b48-25 failed' backend/vif/1/0/hotplug-status error ++ log debug 'Writing backend/vif/1/0/hotplug-error' 'ip link set vif1.0 na= me tapc32a6b48-25 failed' backend/vif/1/0/hotplug-status 'error to xenstore= .' ++ local level=3Ddebug ++ 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' back= end/vif/1/0/hotplug-status 'error to xenstore.' ++ xenstore-write backend/vif/1/0/hotplug-error 'ip link set vif1.0 name ta= pc32a6b48-25 failed' backend/vif/1/0/hotplug-status error ++ log err ip link set vif1.0 name 'tapc32a6b48-25 failed' ++ local level=3Derr ++ 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 Openst= ack Nova > From: ian.campbell@citrix.com > To: bderzhavets@hotmail.com > CC: anthony.perard@citrix.com=3B xen-devel@lists.xen.org > Date: Thu=2C 16 Apr 2015 10:27:09 +0100 >=20 > On Thu=2C 2015-04-16 at 05:14 -0400=2C Boris Derzhavets wrote: >=20 > Please can you not top post. >=20 > > Done > >=20 > > /var/log/xen/xen-hotplug.log:- > >=20 > > RTNETLINK answers: Device or resource busy > >=20 > > Thank you. >=20 > 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. >=20 > Ian. >=20 = --_cf790d66-c0c3-4888-b9bc-ee469f7414c7_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Done

RTNETLINK answers: D= evice or resource busy
++ fatal ip link set vif1.0 name 'tapc32a6b48-25 = failed'
++ _xenstore_write backend/vif/1/0/hotplug-error 'ip link set vi= f1.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=3Ddebug
++ shift
++ logger -p daemon.debug -- /etc= /xen/scripts/vif-bridge: 'Writing backend/vif/1/0/hotplug-error' 'ip link s= et 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=3Derr
++ shift
++ logger -p daemon.err -- /etc/xen/scripts/vif-= bridge: ip link set vif1.0 name 'tapc32a6b48-25 failed'
++ exit 1
Boris.



>=3B Subject: Re: [Xen-devel] Ongoing issue w= ith libvirt-xen driver for Openstack Nova
>=3B From: ian.campbell@citr= ix.com
>=3B To: bderzhavets@hotmail.com
>=3B CC: anthony.perard@c= itrix.com=3B xen-devel@lists.xen.org
>=3B Date: Thu=2C 16 Apr 2015 10:= 27:09 +0100
>=3B
>=3B On Thu=2C 2015-04-16 at 05:14 -0400=2C Bor= is Derzhavets wrote:
>=3B
>=3B Please can you not top post.
&= gt=3B
>=3B >=3B Done
>=3B >=3B
>=3B >=3B /var/log/xe= n/xen-hotplug.log:-
>=3B >=3B
>=3B >=3B RTNETLINK answers: D= evice or resource busy
>=3B >=3B
>=3B >=3B Thank you.
>= =3B
>=3B My usual technique for debugging these sorts of hotplug scri= pt issues is
>=3B to insert near the top of vif-bridge:
>=3B = exec >=3B>=3B /tmp/hotplug.log 2>=3B&=3B1
>=3B echo `date= ` running vif-bridge $@
>=3B set -x
>=3B I hope I recalled th= e syntax correctly. The "set -x" makes it quite
>=3B noisy but gives p= retty good clues.
>=3B
>=3B Ian.
>=3B
=
= --_cf790d66-c0c3-4888-b9bc-ee469f7414c7_-- --_3053fab3-304b-4177-a043-ee4a02ffef32_ Content-Type: application/x-gzip Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="xen-hotplug.log.gz" H4sICHKML1UAA3hlbi1ob3RwbHVnLmxvZwDtWOtv2zYQ/56/4moYUztXlp09UKRVsTTJumBBWjhZ 2yHLBFmibNaypJJUbK/o/74jqYdlyY6TJlgG1B8s6niPH+/Fswfnp0fnJ8env4Mb8RlhfA8OyRX1 CMQMGOFxynA9TPlip9PpAJknMRPwdv/8N9tKObOGNNpTC16sQjq05iQyrTUUzVlsNmmIPTesva+T KPQphA8YWua8k0Pn5PjVYH/wp1OCRRyKZ+NmrmD/9LX99s3Z8QctUnntACdCL0aMJGD8fXLgGJrg pQJM3wYz6CvJNMp4QTA3AU5HhDE4GgwULYxH4JNhOoI4CmlEQCwS4tDAvqIBfDg6ffXHmcY4dL0J iXwL6Vbf6mXC6BcIyRUJbaVEUfmYBiJXjsbATMB3yTSOutqSaYJFhCdDYnGP0URwqdYcMuqPyN7N kUC3rlDGOyJiFrOJ6cVTaZ2PFarZmHpjoEGaSNGARv4B7ruR32BYcWCRuGwENAKj1f6lJf0so8SQ 4pN5LmVLsqc12ZomKYyIlMnUAOPCyHmNR3a5vtQKr9zwncuoOwwJ/0okYLw0oL+NxLKPl8QkmBXj nVUwe5AtPJcTaLWz7RaoQsCkupKc/W5viSdzT84jCBdSi/ZHpk66ScNRO9o718S/YqwDGHsuYkYc Rlzf8UngpqGAFTn5jNwpBsCoCJlSaB2zNJYtbeEm3g+77s/DH5+Zuz/l0KvUHP9S7G17JfKMSHWO PK0+A9Q160qr+lTT1qOhCaCZCdZjPGtQ6cdOzByfkpKRiByBcswGlZs5Bze5byBwBZ5jnWpjxaGB S0PiK8c5RZxnjApSi9k4FkmYjkzsd2jX2A58bmCtNi5ckXJQSncqHdR4jzBoNNoMxLhrJIY+n4iL FO4aZX5Uu3PRnG/bmx/YGYui/a8zQN6pt0jh5Rihis0Rkjaui88tMJA5FdD/Nvn93ya/lUGvNgpu P/kFwYMZ/W4M5c5mv7rlrUauTKw6/Wliw/iXcTfMf/Xt/KVxPvxKtN8mxAc5IebhWR0RJfqmacy+ wWHwZtjqHDTRzcgbx1pA2wFdovbO1ga1QKZjs03NWhr5NGSVsyrvmP9Ala69o/aMR7hPwOILbnmh y7mF9W81sg+Ozm1Mgup4jA6GRqM9VPsJ+plsU5LKQXpGxThOhaPnDNQj5LAeYnauQFgN4o14y469 QWrtRd/UsvOGfdt2fSscNX/RwIujgI5WK8OPZ9K/12yXXlnHaEjO+3XEtqYbWheMMZVCbIyJkL1d ZabQXd48AVMeETOaTh2EPSn2kDqd+FQhta5cZrE0UvdeNqTivoO3v5QJ/GUpfXiKq8ePgSKQHjx5 kr+9yN+UMZ964qJNL+1lcZwrHa3V3u31OjRnDvCIdhMSq2ac0dFYSP4dOZmk8qGuE4PMiQeo9cXL jYqyK4p4KBgor5hzKSbJCWGh7ATGDix94oREcHZ+eHz6FFovvkPelvwpKn/8th89r7BOF9AOfIdG 6RSd81jO+lryyUX/8nkmgqMV4uCYdzhCEL+QaFBFZWiXlbX3B6/fXfQulb4Kf8JoJKC1+CvCzhKU MLABlXqqIrWP0ZgNyzEovG8vsoScLxAcful0HGKHnuRt1dAXr3yqzYDFw6VM3XBpZbH2bPOwktKH 8Oubwfv9wSGYU0jGCy5br2lmK5PyrKb8ZWK0WlfmR9g/ODh6e74WhOli18YpEDNa42EkJNi+a2V0 qzJ5pt+ya6k8XVyu7XJZdew91RabXht6PFLojON4wlX7SWIuW56cAAM1/9VaXPtz/4vZ/rz7petb 33elZN7EsOLq7LIjSqUld5ELxX8kZ6nnYekEqfrrKgt2ET+JpRrqp9lMsHK/dO+pkd8pvmq3x4ws 5++lUvkXpclU/p4ZAAA= --_3053fab3-304b-4177-a043-ee4a02ffef32_ Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel --_3053fab3-304b-4177-a043-ee4a02ffef32_--