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] Dom0 Crashes on High I/O

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Dom0 Crashes on High I/O
From: Henri Cook <henri@xxxxxxxxxxxxxxxxxxxxx>
Date: Fri, 04 Apr 2008 14:44:30 +0100
Cc: Chuck Short <zulcss@xxxxxxxxxx>
Delivery-date: Fri, 04 Apr 2008 06:45:00 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird (X11/20080227)
Hi all, I have a problem that's very similar to this one - which doesn't
appear to have ever been resolved:

My dom0 will crash when I try to transfer large amounts of files in
(e.g. an rsync network backup), when I try to install Windows over HVM
(at the beginning of the installer when 'installation files are being
put into folders') and seemingly 'randomly' throughout the day -
although presumably this could be an instance of high I/O on a DomU that
I would not be aware of.

There are no errors, anywhere that I can see - i've checked

Please; can anyone shed some light on this? At the moment I can lose the
machine up to five times a day and obviously can't install windows or

System is running on Ubuntu Hardy, 2.6.24-14 - in case this is a bug
with their kernel port i've made a bug on launchpad:

Has anyone had this before? How did you solve it?

Swapping also causes a crash as observed in the initially referenced
post, but that's probably because it's a high i/o operation. Turning my
system's ability to swap off has helped the problem a little bit
(eliminating that point of failure at least)



Xen-users mailing list