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-users] Crash with XEN 4.0 on Suse 11.3

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Crash with XEN 4.0 on Suse 11.3
From: JP P <storm66@xxxxxxxxxxxxxxxx>
Date: Sun, 12 Dec 2010 20:39:05 +0100
Delivery-date: Sun, 12 Dec 2010 11:40:36 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Reply-to: jp.pozzi@xxxxxxxxx
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx

I get a VM crash while trying to load a database. The "smaller" tables
are loading OK, but When I try a bigger one (#3 000 000 rows) the ASCII
dump file is #766 MB. When I try to load that table the machine crash
and I find always the same message in the "qemu....log' file :

xc_map_foreign_batch: mmap failed: Cannot allocate memory
xc_map_foreign_bulk error 12

I try it with two different flavous of XEn ( 4.0.0 and 4.0.1).

In "/var/log/xen" some messages about VM's crash :

[2010-12-12 19:37:36 4240] WARNING (image:559) domain com-ingres: device
model failure: pid 1252: malfunctioning (closed sentinel), killed;
see /var/log/xen/qemu-dm-com-ingres.log
[2010-12-12 19:37:36 4240] WARNING (XendDomainInfo:2106) Domain has
crashed: name=com-ingres id=3.
[2010-12-12 19:37:36 4240] DEBUG (XendDomainInfo:3115)
XendDomainInfo.destroy: domid=3
[2010-12-12 19:37:37 4240] DEBUG (XendDomainInfo:1839) Storing domain
details: {'console/port': '3', 'description': '', 'console/limit':
'1048576', 'store/port': '2', 'vm':
'/vm/7c92d28c-753c-64df-6f39-f83776f59b5c', 'domid': '3',
'image/suspend-cancel': '1', 'cpu/0/availability': 'online',
'memory/target': '2097152',
'control/platform-feature-multiprocessor-suspend': '1',
'store/ring-ref': '1044476', 'console/type': 'ioemu', 'name':
[2010-12-12 19:37:37 4240] DEBUG (XendDomainInfo:2450) Destroying device
[2010-12-12 19:37:37 4240] DEBUG (XendDomainInfo:2457) Releasing devices

The machine is :
RAM     8gb
CPU     Amd 910e (quad core)
2 x 250Gb       RAID 1
2 x 1Tb         RAID 1

Ram     2gb
vcpu    2
Balloning is off
dom0_min_mem 2048
xen boot line :
kernel /boot/xen-4.0.0.gz dom0_mem=2048M cpufreq=xen cpuidle
System : Suse 11.3 with kernel

Database VM
Ram     2Gb
vcpu    1
DIsks   3 virtual disks (system, data, log) accessed as hda/hdb/hdc.
System Centos 5.5 with 2.6.18-194.26.1.el5 kernel



Xen-users mailing list

<Prev in Thread] Current Thread [Next in Thread>