[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] domain in state p isn't destroyed

To: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
From: Chris Bainbridge <chris.bainbridge@xxxxxxxxx>
Date: Mon, 3 Oct 2005 17:32:28 +0100
Delivery-date: Mon, 03 Oct 2005 16:30:02 +0000
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=eaYk4siG36pXS/bA7f5cRYgaxWpe75QiWEk18hDSYVusMprEYwUvgiv4dQMcXsmDU9JWYahxkekfFQcg1TMu+mEoknam5PQV7a+zvjR0lqRIo4CiLIRQlM2jI+oI0/bi7YNynR0DzWg/+tXlCHji8HsI85NE47XAKOleFoKatrU=
List-id: Xen developer discussion <xen-devel.lists.xensource.com>

Using recent xen-unstable. I execute 'poweroff' in domU. xm list in
dom0 then shows:

Name              Id  Mem(MB)  CPU VCPU(s)  State  Time(s)
Domain-0           0       91    -      2   r-----   1123.6
server                 2       96    1      1   --p---      0.0

I can execute 'xm destroy server' manually now, but I thought it was
supposed to be automatic?

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

Follow-Ups:
- [Xen-devel] Re: domain in state p isn't destroyed
  - From: Chris Bainbridge

Prev by Date: RE: [Xen-devel] IOMMU support: __direct_remap_pfn_range() fails
Next by Date: Re: [Xen-devel] ethool for e1000
Previous by thread: RE: [Xen-devel] IOMMU support: __direct_remap_pfn_range() fails
Next by thread: [Xen-devel] Re: domain in state p isn't destroyed
Index(es):
- Date
- Thread

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.