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

[Xen-devel] 64bit Xen + iSCSI became in a dom0 crash

  • To: xen-devel@xxxxxxxxxxxxxxxxxxx
  • From: "Luis Vinay" <luisvinay@xxxxxxxxx>
  • Date: Thu, 14 Dec 2006 15:36:47 -0300
  • Delivery-date: Thu, 14 Dec 2006 10:36:49 -0800
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type; b=TOW2NRBw6nRAiKDX9ZxX1+cal7Up3dhZmrJIBmNbKIzGxLixbukijZqNf+RCNoE/8yyJEfc+nDFbFj24kstNhFMFkNRXEqg3kQArqSHNCvwcxs0m0BspL90F2Wo+q8Cp7FX7Oc3TtzqXvG/dfX5F24Vrvl/FmHDSshpvMGnZtRE=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

I'm experimenting with Xen + iSCSI on 64bit platfoms, and I founded that under heavy stress domU's can crash entire system, I've reproduced this many many times.

My systems are like this

- iSCSI Enterprise Target v0.4.13
- RedHat AS4 update 4 64bit + Xen 3.0.3-0 Kernel + Open iSCSI v2.0.730 (Initiator)
- Bonnie++ v1.03a (stressing program)

- Debian 3.1r3 + Open iSCSI v2.0.730 (Initiator)
- RedHat AS4 update 4 + Open iSCSI v2.0.730 (Initiator)

Perfomed tests:
Four instances of bonnie++ with root uid on the filesystem to be stressed

On all the cases the result was a crash, but when I switch to a 32bit distro everything works fine

The attached files are the captured crash errors on the cosole

Luis Vinay

Attachment: minicom-capture-Xen7-2.txt
Description: Text document

Attachment: minicom-capture-Xen7-3.txt
Description: Text document

Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.