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/
Home Products Support Community News


RE: [Xen-users] memory problem

To: "Ralf Dreibrodt" <rd@xxxxxxxx>, <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-users] memory problem
From: "Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>
Date: Mon, 20 Jun 2005 15:09:43 +0100
Cc: ian.pratt@xxxxxxxxxxxx
Delivery-date: Mon, 20 Jun 2005 14:08:41 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcV04gmLJmDfMgkwQG64GYmlvKS2sgAv2NZg
Thread-topic: [Xen-users] memory problem
> There are 20 servers with 80 MB + 1x200 MB, about 1800 MB, 
> the server has 2000 MB.
> After some days/weeks and some xm shutdown/destroy/creates 
> later "xm list" shows:
> Name              Id  Mem(MB)  CPU  State  Time(s)  Console
> Domain-0       0      195    0  r----   9822.9        
> Domain-4       4       80    0  --p--      0.0        
> server1       70       79    0  -b---     62.9    9670
> server2       11       79    0  -b---   3684.5    9611
> server3       13       79    0  -b---   7434.6    9613
> There are suddenly names like "Domain-4", "Domain-5" and so on.

Looks like you have some zombie domains that have got into a bad state.
This can be due to a tools bug, or to a real hypervisor bug, though we
haven't seen any of the latter in a while. If you can find a way to
reproduce this reliably it would help track it down. The other approach
is to use a DEBUG=y build of Xen, and then hit 'o' on the serial console
when its in this state.


Xen-users mailing list

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