From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tomasz Chmielewski Subject: Re: Re: [Xen-users] Re: Xen 3.1 released! Date: Fri, 25 May 2007 15:20:05 +0200 Message-ID: <4656E285.1020602@wpkg.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Keir Fraser Cc: "Petersson, Mats" , xen-devel@lists.xensource.com, xen-users@lists.xensource.com List-Id: xen-devel@lists.xenproject.org Keir Fraser schrieb: > > > On 25/5/07 13:57, "Tomasz Chmielewski" wrote: > >>>>> I inspected the logs, and it was the OOM-killer. Should it ever happen >>>>> when saving a guest domain? Xen host has 256 MB RAM for dom0 (3 GB >>>>> total), Xen guest 1.7 GB. >>>> It appears that saving of HVM somains needs more memory: in this >>>> particular case, when I increased memory for dom0, about 350 MB RAM was >>>> used in total during the domain save. >>> That's kind of surprising, but I guess totally plausible if you don't >>> configure a swap partition for dom0? >> No - dom0 has a 2 GB swap partition. > > Hmmm... That's not so explicable. Obviously something in save/restore is > causing unpageable allocations to happen. Could be pagetables for mappings > of HVM guest memory, or something like that. Needs investigating further, I > think. Could be. Now that I repeated the save/restore a couple of times, total RAM usage for dom0 jumps to ~700 MB sometimes during domain save (dom0 has now about 2.3 GB RAM, domU has 1.7 GB RAM; 4 GB RAM installed now in the machine). -- Tomasz Chmielewski http://wpkg.org