Re: [Xen-users] Memory problems persist... Cannot allocate memory

[Andrew Lyon <andrew.lyon@xxxxxxxxx>]

On Wed, Jan 27, 2010 at 8:22 PM, Pasi Kärkkäinen <pasik@xxxxxx> wrote:
> On Wed, Jan 27, 2010 at 01:36:21PM -0500, James Pifer wrote:
>> > Hello,
>> >
>> > If you set "dom0_mem=4096M" try to set "dom0_min_mem=4096" in 
>> > xend-config.sxp
>> > You said that the system ran a long time before showing "can't allocate 
>> > memory"
>> > it could be a problem with memory fragmentation or a memory leak.
>> > I saw something about that setting a long time ago, but I always use it.
>> >
>>
>> So you always set the dom0_min_mem equal to what you set the kernel
>> parameter to? I'll keep that in mind. I can't change anything right now
>> because I've opened a ticket with Novell and waiting to hear back.
>>
>
> Let us know how it goes..
>
>> The strange thing right now is, there's free memory in dom0, free memory
>> in swap, and a lot of free ram in xm (from xm info).
>>
>
> Definitely sounds like a bug.. Just don't reboot the box before they
> get what they need to debug it :)
>
> -- Pasi
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users
>

I think I may have hit a similar bug running 3.4.2 , while testing
save/restore/migrate I occasionally got "unable to allocate memory"
errors and the domU failed to restore or migrate successfully, but
immediately trying to start the same vm on the same system was
successful, and having restarted it I was able to migrate it between
two servers several times.

So it appears that sometimes Xen will error that it cannot allocate
memory, but a subsequent request for the same amount of memory is
successful.

Andy

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