From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Dan Magenheimer" Subject: RE: Unresolved - qemu-dm crash under high dom0 disk load Date: Wed, 30 Jan 2008 10:37:07 -0700 Message-ID: <20080130103707093.00000002384@djm-pc> References: Reply-To: "dan.magenheimer@oracle.com" Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Keir Fraser , Randy McAnally , "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org If this solves the problem, it would be nice to slide it into 3.1.3 final. > -----Original Message----- > From: xen-devel-bounces@lists.xensource.com > [mailto:xen-devel-bounces@lists.xensource.com]On Behalf Of Keir Fraser > Sent: Wednesday, January 30, 2008 9:33 AM > To: Randy McAnally; xen-devel@lists.xensource.com > Subject: Re: [Xen-devel] Unresolved - qemu-dm crash under = > high dom0 disk > load > = > = > Please try the attached patch. > = > -- Keir > = > On 30/1/08 16:09, "Randy McAnally" wrote: > = > > This is regarding a long unresolved issue with HVM qemu-dm = > crashing under > > heavy Dom0 IO load. > > > > I decided to make a new thread on this seeing that I found = > many old ones > > scattered about with no resolution: > > > > Here are old threads regarding the same/similar issue > > > > = > http://lists.xensource.com/archives/html/xen-users/2007-08/msg 00135.html > http://lists.xensource.com/archives/html/xen-users/2007-07/msg00624.html > > Old bug reports of the issue: > > http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=3D542 > http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=3D1038 > > In 1038, spam@abma.de _incorrectly_ reports it is fixed in 3.1.1 -- Not o= nly > can I find any evidence of this, I can EASILY reproduce the crash over an= d > over with 3.1.3-rc2. > > I have a dev. Xen box available for anyone who wants access for stack > traces, ect. > > Unfortunately I myself do not have enough knowledge to find the problem > myself, however I am available to instruct on how to produce the bug, run= > stack traces, help organize this effort, and provide unrestricted access = to > this dev machine if needed.