WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

RE: [Xen-devel] domains not shutting down properly - the problem isback

To: "Keir Fraser" <keir.fraser@xxxxxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-devel] domains not shutting down properly - the problem isback again
From: "James Harper" <james.harper@xxxxxxxxxxxxxxxx>
Date: Fri, 2 Jan 2009 10:52:09 +1100
Cc:
Delivery-date: Thu, 01 Jan 2009 15:53:05 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <C5827EF6.20A7E%keir.fraser@xxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <AEC6C66638C05B468B556EA548C1A77D0155015F@trantor> <C5827EF6.20A7E%keir.fraser@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AclsEUiDJwnrGfQLQ6G5Bsw4GM+wzgAAL2RgAAIdJkkAE/C/sA==
Thread-topic: [Xen-devel] domains not shutting down properly - the problem isback again
> On 01/01/2009 13:09, "James Harper" <james.harper@xxxxxxxxxxxxxxxx>
wrote:
> 
> >> Domains don't die, they just stay in the 's' state until you 'xm
> >> destroy' them, and even after that there is still a page or two
being
> >> used according to 'xm debug q'.
> >>
> >> I have upgraded to 3.3.1-rc4 but it doesn't seem to make a
> >> difference...
> >
> > Also, 'lsevtchn' shows one extra 'Channel is waiting interdom
> > connection' after starting and then destroying a new domain.
> 
> Backend driver not cleaning up due to xend not correctly deleting a
> directory from xenstore, or because of hotplug/udev script problems?
> There's
> some interaction going on with your dom0 installation, since no one
else
> has
> seen or reported this issue.

When I start the domain, 'udevadm monitor' says:

UDEV  [1230853478.622189] add      /devices/xen-backend/vbd-3-769
(xen-backend)
UDEV  [1230853478.684237] add      /devices/xen-backend/vbd-3-770
(xen-backend)
UDEV  [1230853478.830864] add      /devices/xen-backend/vif-3-0
(xen-backend)
UEVENT[1230853478.835024] add      /class/net/vif3.0 (net)
UEVENT[1230853478.837346] online   /devices/xen-backend/vif-3-0
(xen-backend)
UDEV  [1230853478.838478] online   /devices/xen-backend/vif-3-0
(xen-backend)
UDEV  [1230853478.871352] add      /class/net/vif3.0 (net)
UEVENT[1230853479.026088] add      /devices/xen-backend/console-3-0
(xen-backend)
UDEV  [1230853479.027654] add      /devices/xen-backend/console-3-0
(xen-backend)

Then when I issue the shutdown:

UDEV  [1230853614.593201] offline  /devices/xen-backend/vif-3-0
(xen-backend)
UDEV  [1230853614.593239] remove   /class/net/vif3.0 (net)

And because the domain is now stuck in the 's' state, I have to issue
the 'destroy':

UDEV  [1230853668.181925] remove   /devices/xen-backend/console-3-0
(xen-backend)
UDEV  [1230853668.219248] remove   /devices/xen-backend/vbd-3-769
(xen-backend)
UDEV  [1230853668.230573] remove   /devices/xen-backend/vbd-3-770
(xen-backend)
UDEV  [1230853668.238480] remove   /devices/xen-backend/vif-3-0
(xen-backend)

On another machine that does not have this problem, a similar domain
(different version of udev) does this on start:

UEVENT[1230853752.615378] add@/devices/xen-backend/vbd-10-769
UDEV  [1230853752.615378] add@/devices/xen-backend/vbd-10-769
UEVENT[1230853752.653987] add@/devices/xen-backend/vbd-10-770
UDEV  [1230853752.653987] add@/devices/xen-backend/vbd-10-770
UEVENT[1230853752.685909] add@/devices/xen-backend/vif-10-0
UDEV  [1230853752.685909] add@/devices/xen-backend/vif-10-0
UEVENT[1230853752.689908] add@/class/net/vif10.0
UDEV  [1230853752.697530] add@/class/net/vif10.0
UEVENT[1230853752.698462] online@/devices/xen-backend/vif-10-0
UDEV  [1230853752.699603] online@/devices/xen-backend/vif-10-0
UEVENT[1230853752.773270] add@/devices/xen-backend/console-10-0
UDEV  [1230853752.781188] add@/devices/xen-backend/console-10-0

And this on shutdown (shutdown was actually done before the start):

UEVENT[1230853735.596056] remove@/devices/xen-backend/console-7-0
UDEV  [1230853735.596056] remove@/devices/xen-backend/console-7-0
UEVENT[1230853735.625884] remove@/devices/xen-backend/vbd-7-769
UDEV  [1230853735.625884] remove@/devices/xen-backend/vbd-7-769
UEVENT[1230853735.641803] remove@/devices/xen-backend/vbd-7-770
UDEV  [1230853735.641803] remove@/devices/xen-backend/vbd-7-770
UEVENT[1230853735.653536] offline@/devices/xen-backend/vif-7-0
UDEV  [1230853735.653536] offline@/devices/xen-backend/vif-7-0
UEVENT[1230853735.764489] remove@/class/net/vif7.0
UDEV  [1230853735.764489] remove@/class/net/vif7.0
UEVENT[1230853736.005804] remove@/devices/xen-backend/vif-7-0
UDEV  [1230853736.135452] remove@/devices/xen-backend/vif-7-0

Does that suggest anything obvious?

Thanks

James

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>