Xen users - Dec 2010 - Crash with XEN 4.0 on Suse 11.3

Hello,

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'':
''com-ingres''}
[2010-12-12 19:37:37 4240] DEBUG (XendDomainInfo:2450) Destroying device
model
[2010-12-12 19:37:37 4240] DEBUG (XendDomainInfo:2457) Releasing devices

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

Domain0 
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 2.6.34.7-0.5-xen 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

Regards

JP P



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

--- On Sun, 12/12/10, JP P <storm66@club-internet.fr> wrote:
> From: JP P <storm66@club-internet.fr>
> Subject: [Xen-users] Crash with XEN 4.0 on Suse 11.3
> To: xen-users@lists.xensource.com
> Date: Sunday, December 12, 2010, 11:39 AM
> Hello,
> 
> I get a VM crash while trying to load a database.
> 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
> 
Tell us why you don''t want a paravirtual VM. If you tried xen 4.0.1,
you must have tried a pv VM. What goes wrong with that?

To convert the VM to paravirtual, use the kernel-xen in C5.5

You need at least 2 new modules in your initrd.img: xennet and xenblk

/sbin/mkinitrd --with=xennet --with=xenblk --without-dmraid -v -f
/boot/initrd-$(uname -r).img $(uname -r)

If the above is awkward, before you install kernel-xen (xen aware kernel), make
the following edit

#cat >> /etc/sysconfig/mkinitrd/pvxen<<EOL
with=xennet
with=xenblk
preload=xenblk
EOL

#chmod +x /etc/sysconfig/mkinitrd/pvxen

#yum install kernel-xen

then in your VM.cfg use bootloader=pygrub or copy the vmlinuz-xx.yy-el5xen and
initrd-xx.yy-el5xen.img to dom0

This may not fix the crash, but performance should improve.

-- 
Mark




      

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