Re: [Xen-devel] Re: PROBLEM: Xen ballon driver seems to be broken in 2.6.26

[Jeremy Fitzhardinge <jeremy@xxxxxxxx>]

Németh Tamás wrote:
> > What is your "newest" Xen version?  If 3.2, the balloon driver fix
> > isn't there yet, but I have a bash-script workaround.  See
> > tools/xenballoond in xen-unstable.
> >     
>  The source codes of the hyperhisor and the tools were downloaded from
> xen.org a few days ago, so Xen is 3.2.1 and the dom0 kernel is
> 2.6.18.8-xen-3.2.0 (based on 2.6.18.8).
>
>  The domU kernel is 2.6.26 of course.
>
>
>
>   
> > > So that's consistent with the balloon driver
> > > over-aggressively shrinking
> > > the domain, until there's no memory left to do anything.  The balloon
> > > driver has no safety checks to prevent that from happening.
> > >
> > > What value are you setting the target size to?  Are you using
> > > the right
> > > units?
> > >       
> Please take a look at this:
>
> carrier5:/usr/local/LOCALHOST/src/linux-2.6.26 # xm list
> Name                                        ID   Mem VCPUs      State   Time(s)
> Domain-0                                     0  2048     1     r-----    370.3
> u-96                                         5  1024     1     -b----     14.5
> carrier5:/usr/local/LOCALHOST/src/linux-2.6.26 # xm mem-set u-96 768M
> carrier5:/usr/local/LOCALHOST/src/linux-2.6.26 # xm list
> Name                                        ID   Mem VCPUs      State   Time(s)
> Domain-0                                     0  2048     1     r-----    371.4
> u-96                                         5   768     1     -b----     14.6
> carrier5:/usr/local/LOCALHOST/src/linux-2.6.26 #
>
> DomU - although being seemngly frozen - still responses for icmp echo
> requests.
Thanks, I'll have a look at it.

   J


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