WARNING - OLD ARCHIVES

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

xen-users

Re: [Xen-users] oom-killer keeps killing big un-tars

To: Mark Williamson <mark.williamson@xxxxxxxxxxxx>
Subject: Re: [Xen-users] oom-killer keeps killing big un-tars
From: Andrew Thompson <xenuser@xxxxxxxxxxx>
Date: Wed, 18 May 2005 13:06:32 -0400
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 18 May 2005 17:05:59 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <200505181748.41795.mark.williamson@xxxxxxxxxxxx>
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>
References: <428B62A8.7080401@xxxxxxxxxxx> <200505181748.41795.mark.williamson@xxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
Mark Williamson wrote:
Are you running any guest domains? What are you using for the other domains filesystems? Things like LVM snapshots and (especially) loopback devices over NFS can use lots of (non swappable) kernel memory in dom0 and cause OOM conditions quite easily.

I currently have one guest domain that is happily running in another 30-40MB of RAM. (Repartitioned my drive, so I'm trying to untar gentoo stage3 and portage.)

All filesystems are currently living on standard extended partitions of a SCSI harddrive.

I do not have NFS(or hardly any other apps) running in dom0.

Now it appears that sshd has locked up or was killed so I can no longer connect to the instance from here. I'll have to sit down at the machine later tonight to do any more debugging. (I had Xen kill something important in dom0 one time that broke my whole access to the console and ssh of dom0.)

--
Andrew Thompson
http://aktzero.com/

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