From: "Venefax" <venefax@gmail.com>
To: 'Keir Fraser' <keir.fraser@eu.citrix.com>,
'James Harper' <james.harper@bendigoit.com.au>,
xen-devel@lists.xensource.com
Subject: RE: domains not shutting down properly - the problem isback again
Date: Thu, 1 Jan 2009 09:34:40 -0500 [thread overview]
Message-ID: <009301c96c1e$159c18e0$40d44aa0$@com> (raw)
In-Reply-To: <C5827EF6.20A7E%keir.fraser@eu.citrix.com>
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
next prev parent reply other threads:[~2009-01-01 14:34 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-01 13:03 domains not shutting down properly - the problem is back again James Harper
2009-01-01 13:09 ` domains not shutting down properly - the problem isback again James Harper
2009-01-01 14:08 ` Keir Fraser
2009-01-01 14:34 ` Venefax [this message]
2009-01-01 14:41 ` Keir Fraser
2009-01-01 23:52 ` James Harper
2009-01-02 2:38 ` James Harper
2009-01-02 3:40 ` James Harper
2009-01-02 4:15 ` domains not shutting down properly - the problemisback again James Harper
2009-01-02 4:48 ` James Harper
2009-01-02 9:11 ` domains not shutting down properly - theproblemisback again James Harper
2009-01-02 9:55 ` Keir Fraser
2009-01-02 10:11 ` James Harper
2009-01-02 10:28 ` Keir Fraser
2009-01-02 10:28 ` James Harper
2009-01-02 10:41 ` Keir Fraser
2009-01-02 10:48 ` James Harper
2009-01-02 11:47 ` domains not shutting down properly - theproblemisbackagain James Harper
2009-01-02 12:34 ` Keir Fraser
2009-01-02 13:27 ` domains not shutting down properly -theproblemisbackagain James Harper
2009-01-02 15:31 ` Keir Fraser
2009-01-03 0:57 ` James Harper
2009-01-03 2:25 ` domains not shutting down properly-theproblemisbackagain James Harper
2009-01-03 5:12 ` domains not shutting down properly -theproblemisbackagain James Harper
2009-01-03 5:36 ` domains not shutting down properly-theproblemisbackagain James Harper
2009-01-03 6:29 ` bug in evtchn_cpu_notify (was domains not shutting down properly-theproblemisbackagain) James Harper
2009-01-03 7:04 ` James Harper
2009-01-03 8:52 ` Keir Fraser
2009-01-02 12:52 ` domains not shutting down properly -theproblemisbackagain James Harper
2009-01-02 11:15 ` domains not shutting down properly - theproblemisback again James Harper
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='009301c96c1e$159c18e0$40d44aa0$@com' \
--to=venefax@gmail.com \
--cc=james.harper@bendigoit.com.au \
--cc=keir.fraser@eu.citrix.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.