Re: domains not shutting down properly - the problem isback again

[Keir Fraser <keir.fraser@eu.citrix.com>]

Not releasing any guest memory would possibly be a different bug. James's
guests are hanging around with just a few kilobytes of memory remaining.

 K.

On 01/01/2009 14:34, "Venefax" <venefax@gmail.com> wrote:

> 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@lists.xensource.com
> [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Keir Fraser
> Sent: Thursday, January 01, 2009 9:09 AM
> To: James Harper; xen-devel@lists.xensource.com
> Subject: Re: [Xen-devel] domains not shutting down properly - the problem
> isback again
> 
> On 01/01/2009 13:09, "James Harper" <james.harper@bendigoit.com.au> 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@lists.xensource.com
> http://lists.xensource.com/xen-devel
>