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

["Venefax" <venefax@xxxxxxxxx>]

I have the same issue. And Novell technical services is working on a fix.
The memory assigned to a domain is not returned to the system after is
killed with "destroy". After several dozen "destroy" and "start" I have to
reboot the host. An my host has 128 GB of ram.
Federico

-----Original Message-----
From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
[mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Keir Fraser
Sent: Thursday, January 01, 2009 9:09 AM
To: James Harper; xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: Re: [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.

 -- Keir



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


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