Re: [Xen-devel] libxl: error: libxl.c:2150:libxl_set_memory_target new target 0 for dom0 is below the minimum threshold

[Ian Campbell <Ian.Campbell@xxxxxxxxxx>]

On Tue, 2011-11-22 at 07:56 +0000, Teck Choon Giam wrote:
[...]
> memory = 15360
> maxmem = 15360
[...]
> How much RAM does the host system have? What are your hypervisor and
> > dom0 command lines.
> 
> 16GB RAM.

So you are assigning 15GB out of a total of 16GB to the guest which
necessitates ballooning dom0 from 16GB down to 1GB.

> title Scientific Linux (2.6.32.47-0.xen.pvops.choon.sl6)
>       root (hd0,0)
>       kernel /xen.gz dom0_mem=512M loglvl=all guest_loglvl=all cpuidle=0 
> cpufreq=none

But you have already forced the dom0_mem to 512M. I suspect this is
colluding with the above ballooning to make it look as if dom0 should be
ballooned to <128M, which causes xl to print a warning message. Perhaps
someone who understands this stuff can comment on whether or not this
should be the case.

Can you try setting "autoballoon=0" in /etc/xl.cfg.

I can't see anything in the range 23110:23190 which might have caused a
change in behaviour here though.

>       module /vmlinuz-2.6.32.47-0.xen.pvops.choon.sl6 ro
> root=UUID=154127e6-9469-4124-9a42-1f6c6160adf4
> rd_MD_UUID=d5126687:736a76db:5d5f597f:8b16fad4 rd_NO_LUKS rd_NO_LVM
> rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc
> KEYTABLE=us crashkernel=auto rhgb quiet panic=5 panic_timeout=10
>       module /initramfs-2.6.32.47-0.xen.pvops.choon.sl6.img
> 
> >
> > What is the last changeset which worked for you?
> 
> I did provide last working changeset is 23110 in my initial email.

So you did, sorry I missed it.

Ian.



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