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/
Home Products Support Community News


[Xen-bugs] Mmap failed: Cannot allocate memory

To: <xen-bugs@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-bugs] Mmap failed: Cannot allocate memory
From: "Smith, Mike" <Mike.Smith@xxxxxxxxxxxxxxxxx>
Date: Thu, 28 May 2009 06:56:08 -0600
Delivery-date: Thu, 28 May 2009 06:33:24 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-bugs-request@lists.xensource.com?subject=help>
List-id: Xen Bugzilla <xen-bugs.lists.xensource.com>
List-post: <mailto:xen-bugs@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-bugs-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acnfk6s281C8pgiqTby3JaQepYrRVQ==
Thread-topic: Mmap failed: Cannot allocate memory

 Hey all,

 New to the list here. We are having some very serious issues with Xen. Our current environment has around 25 Dell 905's (4 quad cores and 128GM) as our Xen hosts/Dom0's. Under these we have maybe 60 guests running a variety of applications (Oracle, Ldap, DB2,etc).

 We've been seeing major stability problems. The latest one has us a bit concerned. We have an LDAP box that will stay running for 3-4 hours then spit this out in the qemu-dm-<guestname>.log

Xc_map_foreign_batch: mmap failed: Cannot allocate memory
Xc_map_foreign_batch: error 12

When this happens, the guest/domU goes offline. No ping, no access via console or vnc. The guest is configured for 16G ram and 2 vcpus.

Anyone else seeing problems like this? It consistantly happens with this domU, others less frequent. We've migrated the guests to various other hosts and it continues to happen. So we can rule out hardware. Either something in the xen kernel or the underlying OS (Suse 11).

Oh, we are running with xen-3.3.1


- Mike Smith

- - - - - - - - - - - - - - - - - - - - - - - - - -
This message is intended only for the personal and confidential use of the designated recipient(s) named. If you are not the intended recipient of this message, you are hereby notified that any review, dissemination, distribution or copying of this message is strictly prohibited. This communication is for information purposes only and should not be regarded as an offer to sell or as a solicitation of an offer to buy any financial product, an official confirmation of any transaction, or as an official statement of Aurora Bank FSB. Email transmission cannot be guaranteed to be secure or error-free. Therefore, we do not represent that this information is complete or accurate and it should not be relied upon as such. All information is subject to change without notice.
Xen-bugs mailing list
<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-bugs] Mmap failed: Cannot allocate memory, Smith, Mike <=