From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christopher Thunes Subject: Re: HELP:) vif-common.sh call on xm shutdown / xm destroy Date: Fri, 13 Jun 2008 13:43:41 -0400 Message-ID: <4852B1CD.6060205@brewtab.com> References: <483696B7.5050600@swisscenter.com> <18486.41168.929068.555017@mariner.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <18486.41168.929068.555017@mariner.uk.xensource.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Ian Jackson Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org We've also seen this problem and have some more information. Looking=20 into it we have found that the udev "offline" event is not being=20 triggered by the kernel on paravirtual guest shutdowns. HVM guests seem=20 to work just fine though. We can provide udevmonitor output and/or udev=20 log output if it would help. Definitely seems like a bug though. - Chris Thunes Ian Jackson wrote: > S=E9bastien RICCIO writes ("[Xen-devel] HELP:) vif-common.sh call on xm= shutdown / xm destroy"): >> Is it right that xm shutdown doesn't call vif-common.sh ? >=20 > shutdown just asks the guest to shut itself down so shouldn't bring > the interfaces down right away. But I think the script should be > called when the domain indicates that its shutdown is complete, > destroying itself. It's quite possible that this is buggy ... >=20 > Ian. >=20 > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel