Re: Balloon driver.

[Christoph Egger <Christoph_Egger%gmx.de@localhost>]

On Thursday 08 July 2010 17:42:46 Cherry G. Mathew wrote:
> Hi Christoph,
>
> On 7 July 2010 14:30, Christoph Egger <Christoph_Egger%gmx.de@localhost> 
> wrote:
>
> [...]
>
> >> > Though I have to report a bug:
> >> >
> >> > I have an amd64 Dom0 kernel w/o XEN_BALLOONING in the kernel config.
> >> > Boot the xen kernel with dom0_mem=512m
> >> >
> >> > After login I do:
> >> >
> >> > # sysctl kern.xen
> >> > kern.xen.balloon.current = 131072
> >> > node_val out of range.
> >> > node_val = 0
> >> >
> >> > I expect kern.xen.balloon.current to say 512MB and I don't expect to
> >> > see the node_val messages.
> >>
> >> Whoops!
> >>
> >> Does the following patch fix it for you:
> >
> > I think, the ballooning sysctl's should be always there regardless if
> > compiled with or w/o XEN_BALLOONING in the kernel config to prevent
> > misbehaviour of the xen tools.
> >
> > If XEN_BALLOONING is not specified then the sysctl values should be
> > a) read-only
> > b) print reasonable fixed values.
>
> http://mail-index.netbsd.org/source-changes/2010/07/08/msg011550.html
>
> I hope this works for you.
>
>
> Would the following patch work be ok for xentools ?

I get this:

# sysctl kern.xen
kern.xen.balloon.current = 131072
kern.xen.balloon.target = 131072

So for xentools, this is fine but the values are incorrect
as I boot xen kernel with dom0_mem=512m.
The correct value for both current and target is 524288.

Christoph