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] Problem for "xm create": "kernel: Setting mem allocation

Am Freitag, 20. Oktober 2006 08:36 schrieb Ulrich Windl:
> On 19 Oct 2006 at 16:48, harm wrote:
> > there is a balloon setting to specify the ram usage by Dom0, look in your
> > /etc/xend-config.sxp near the end of the file.
>
> Not here (SLES10): I only have:
> # Dom0 will balloon out when needed to free memory for domU.
> # dom0-min-mem is the lowest memory level (in MB) dom0 will get down to.
> # If dom0-min-mem=0, dom0 will never balloon out.
> (dom0-min-mem 196)
>
> > Your error msg indicates there is not enough free ram.
>
> not very clearly, and I wonder why it takes about one minute to find out
> that there's not enough  RAM.
>
> > You can check it with xm list, that will show the current mem usage with
> > Xen. Free -h will show system mem usage.
>
> # free -h
> free: invalid option -- h
free -m natürlich ^^ 

lg
stephan
> [...]
>
> Ulrich
>
> > On 10/19/06, Ulrich Windl <ulrich.windl@xxxxxxxxxxxxxxxxxxxx> wrote:
> > > Hi,
> > >
> > > When trying to boot a freshly created VM, nothing seems to happen, but
> > > Dom0
> > > repeats  messages like
> > > kernel: Setting mem allocation to ... kIB
> > > while "..." is some large number like this:
> > > Oct 19 15:55:33 rkdvmso1 kernel: Setting mem allocation to 816764 kiB
> > > Oct 19 15:55:41 rkdvmso1 kernel: Setting mem allocation to 816764 kiB
> > > Oct 19 15:55:46 rkdvmso1 kernel: Setting mem allocation to 816764 kiB
> > > Oct 19 15:55:54 rkdvmso1 kernel: Setting mem allocation to 816764 kiB
> > >
> > > Eventually I see (after "xm create"):
> > > Error: The privileged domain did not balloon!
> > >
> > > Now I think the error message on the console and in the syslog could be
> > > improved:
> > > Is Dom0 kernel retrying, how much is available (I assume less than
> > > demanded).
> > > Could this be a NUMA problem?
> > >
> > > A "# xm mem-set 0 256" to reduce the mem of Domain-0, but the VM
> > > wouldn't start,
> > > and Domain-0 re-allocated the previous size (556M)
> > >
> > > How do I limit the maximum mem for Domain-0, so that DomUs have enough
> > > RAM left
> > > over for them?
> > >
> > > Regards,
> > > Ulrich
> > >
> > >
> > > _______________________________________________
> > > Xen-users mailing list
> > > Xen-users@xxxxxxxxxxxxxxxxxxx
> > > http://lists.xensource.com/xen-users
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users

-- 
Stephan Augustin
Rosenpark 3
65795 Hattersheim
06190/879166
0173/1735867

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