[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] out-of-memory problem when restoringballooneddomains


  • To: Lars Rasmusson <Lars.Rasmusson@xxxxxx>
  • From: Kip Macy <kip.macy@xxxxxxxxx>
  • Date: Wed, 4 May 2005 15:24:57 -0700
  • Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Wed, 04 May 2005 22:24:34 +0000
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=dWO49bFNCMPyXlVxL3tcBvOoE/YYTmgKusIbzE4dcC+ORRIMhMThva8KyzRdyIcOd8piWXqil9O4bZBo+Y87UwRN31JoeXi2E2PjinOvL3tw5uouVFby8FDqCwNoNeMHtpdGVvQrGyvQA+87o9MNoIA39A4sqBGZCrDg2B5/2UM=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

If it doesn't work already it is a neccessity long term to leverage
Xen for zero downtime upgrades.  Otherwise you end up having to leave
spare capacity available to ensure that a guest can be migrated.


           -Kip


On 5/4/05, Lars Rasmusson <Lars.Rasmusson@xxxxxx> wrote:
> 
> Hi, about two months ago I inquired about if xen could restore (or
> migrate) a *ballooned* domain if its unballoned size won't fit.
> 
> Example: on a 2G machine
> 
>   xm create domain1 memory=1500
>   xm balloon domain1 128
>   xm save domain1 saved1
> 
>   xm create domain2 memory=1500
> 
>   xm restore saved1
>   *** BEEP! Xen refuses ***
> 
> Is there any news on this issue?
> 
> I think this would be a very useful feature to have.
> 
> Even better would be if one could boot a machine giving it the impression
> pf having the whole memory space but without actually ever giving it all
> of memory, something like
> 
>   xm create domain1 memory=1500 balloon=128
> 
> if you see what I mean.
> 
> Anyway, thanks for all the cool stuff you're doing!
> 
> /Lars
> 
> 
> On Fri, 11 Mar 2005, Keir Fraser wrote:
> 
> >
> > On 10 Mar 2005, at 23:35, Lars Rasmusson wrote:
> >
> > > I think the relevant part from the log is this.
> > >
> > > xc_linux_restore start
> > > Could not create domain. pfns=460800, 1843200KB
> > > Could not create domain. pfns=460800, 1843200KB
> > > 4526 [INF] XFRD> Xfr service err=1
> >
> > Ah! The problem is that we initially create the domain with its
> > 'maximum possible' memory allocation, and then automatically 'balloon
> > it down' at the end of the restore operation. Of course by the third
> > domain you do not have 1.8GB of headroom and so the third restore
> > fails.
> >
> > This probably made live relocation easier to implement, but we need to
> > change this to allocate only the memory that the domain is currently
> > using during each round of pre-copy migration. Getting non-live moved
> > over is the first step, and then fix live relocation, I guess.
> >
> >   -- Keir
> >
> >
> >
> > -------------------------------------------------------
> > SF email is sponsored by - The IT Product Guide
> > Read honest & candid reviews on hundreds of IT Products from real users.
> > Discover which products truly live up to the hype. Start reading now.
> > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@xxxxxxxxxxxxxxxxxxxxx
> > https://lists.sourceforge.net/lists/listinfo/xen-devel
> >
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
>

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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.