Re: [Xen-users] xl memory bug

[Casey DeLorme <cdelorme@xxxxxxxxx>]

My mistake, not the same problem I had.

However, it does sound like a ballooning problem, Dom0 starts with an initial assigned memory from the dom0_mem flag, but it gets smaller over time possibly because ballooning is on by default.

With the xm toolstack you can set dom0-min-mem in the xend-config file, but I don't know how to do this with the xl toolstack, I imagine there is a grub flag for it though.

On Wed, Mar 28, 2012 at 11:44 AM, Flavio <fbcyborg@xxxxxxxxx> wrote:

On 28 March 2012 17:27, jacek burghardt <jaceksburghardt@xxxxxxxxx> wrote:
> I use ssh so it dies and system reboots just fine. Xm does not habe any
> issues allocati.g memory but it no longer being used. What is realy strange
> that now is taking wrong memory xl was never able to make use of all free
> memory on number of systems but now it does not check for lack of free
> memory on dom0 and just takes it before I would get error that there is not
> enough memory
>
> On Mar 28, 2012 8:53 AM, "Casey DeLorme" <cdelorme@xxxxxxxxx> wrote:
>>
>>
>> Does your xl/xm dmesg state anything about the memory maps being used?  I
>> wonder if it is related to the EFI memory bug I've run into with the e801 &
>> e820 maps.
>>
>> On Wed, Mar 28, 2012 at 10:11 AM, Flavio <fbcyborg@xxxxxxxxx> wrote:
>>>
>>> On 28 March 2012 15:19, jacek burghardt <jaceksburghardt@xxxxxxxxx>
>>> wrote:
>>> > I have Dell 860 with 8GB of memory I am running xen unstable 4.2 and
>>> > 3.3.0-rc7 with most recent version I see strange issue I am running two
>>> > server 2008 each gets 3 GB of ram xl info shows 1.5 GB now I am
>>> > attempting
>>> > to start Linux install running hvm with 512 memory it crashes domO . I
>>> > have
>>> > 512 allocated to domO but free shoes that 343 was assigned after
>>> > starring
>>> > two instances. Where is the memory going to.
>>> Hey!
>>>
>>> this seems related to a problem I've reported many months ago.
>>> http://lists.xen.org/archives/html/xen-users/2011-12/msg00069.html
>>>
>>> I would like to know how is the state of the fix process, as regard this
>>> issue.

For instance, it may also happen that if I don't pass the
dom0_mem=1024M parameter to
the hypervisor in grub.conf, the memory "situation" is like this:

            total       used       free     shared    buffers     cached

Mem:       6152824     155936    5996888          0      20864      40820
-/+ buffers/cache:      94252    6058572
Swap:      8388604          0    8388604

So, 6GB out of 8GB are available for dom0, instead of 800MB, but this is
completely random on every boot.

--
Flavio

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users