[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#625217: xen-linux-system-2.6.32-5-xen-amd64: Heavy load on domU causes dom0 to run out of memory



Hi,

The maschine has 12G of RAM. For dom0 I tried several configurations -
4G with balloning enabled, at least 1G statically assigned. DomUs have
different memory settings.

xm info | grep mem:

total_memory           : 12224
free_memory            : 1589
node_to_memory         : node0:1077
node_to_dma32_mem      : node0:1074
xen_commandline        : placeholder dom0_mem=1024M dom0_max_vcpus=2
dom0_vcpus_pin


dom0 free -m:

             total       used       free     shared    buffers     cached
Mem:          1019       1008         10          0        249        528
-/+ buffers/cache:        231        788
Swap:         1913         29       1884


xm list:

Name                                        ID   Mem VCPUs      State
Time(s)
Domain-0                                     0  1019     2     r-----
12087.5
alfresco                                     1  3096     1     -b----
  57.0
destiny                                      3   384     1     -b----
 919.5
hudson32                                     4   384     1     -b----
 165.2
hudson64                                     5  1536     1     -b----
2697.1
ms2cistage                                   7  2048     1     -b----
  10.5
ms2istage                                    6  2048     1     -b----
  19.1


Thanks
Sebastian


Am 02.05.2011 19:35, schrieb Ben Hutchings:
> On Mon, 2011-05-02 at 16:50 +0200, Sebastian Hofmann wrote:
>> Package: xen-linux-system-2.6.32-5-xen-amd64
>> Version: 2.6.32-31
>> Severity: critical
>> Justification: breaks the whole system
>>
>> Hi,
>>
>> I have 64 bit xen kernel from squeeze installed on a dual xeon
>> maschine. Usually everything runs fine until it comes to heavy load on
>> a domU with high I/O and memory consumption.
>> This causes the dom0 to run out of memory and to kill several
>> processes (see log below). As a consequence of this, the whole system
>> becomes unusable.
>>
>> I tried several things like assign dedicated memory to dom0, disable
>> balloning, increase scheduler domain weights and assigned dedicated
>> CPUs to dom0 as described in 
>> http://wiki.xensource.com/xenwiki/XenBestPractices but had no success.
>>
>> I think a domU should never break the whole system, so this might be a
>> bug. Please let me know if you need further information.
> [...]
> 
> How much physical RAM is in the system and how much memory do you assign
> to each domain?
> 
> Ben.
> 

-- 
--------------------------------------
M.Sc. Sebastian Hofmann

SOURCEPARK GmbH
Hohenzollerndamm 150 Haus 7a
14199 Berlin

Tel:    +49 (0)30/398 068 30
Fax:    +49 (0)30/398 068 39
e-mail: sebastian.hofmann@sourcepark.de
www:    www.sourcepark.de
--------------------------------------
SOURCEPARK GmbH
Sitz der Gesellschaft: Berlin / Amtsgericht Charlottenburg
HRB 80254
Geschäftsführung: Matthias Barmeier, Harald Dürr
--------------------------------------

Wichtiger Hinweis: Die vorgenannten Angaben werden jeder E-Mail
automatisch hinzugefügt und lassen keine Rückschlüsse auf den
Rechtscharakter der E-Mail zu.

Diese E-Mail kann vertrauliche und/oder rechtlich geschützte
Informationen enthalten. Wenn Sie nicht der richtige Adressat
sind oder diese E-Mail irrtümlich erhalten haben, informieren
Sie bitte sofort den Absender und vernichten Sie diese E-Mail.
Das unerlaubte Kopieren sowie die unbefugte Weitergabe
dieser E-Mail ist nicht gestattet.



Reply to: