From: "Randy McAnally" <rsm@fast-serv.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>,
"dan.magenheimer@oracle.com" <dan.magenheimer@oracle.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: Unresolved - qemu-dm crash under high dom0 disk load
Date: Wed, 30 Jan 2008 12:42:19 -0500 [thread overview]
Message-ID: <20080130174145.M33140@fast-serv.com> (raw)
In-Reply-To: <C3C66706.1BAE7%Keir.Fraser@cl.cam.ac.uk>
This certainly solves the issues I've been having. Thanks so much for all
your hard work, Keir.
--
Randy McAnally
Fast Serv Networks, LLC
619-819-8252 x201
619-819-9443 fax
---------- Original Message -----------
From: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
To: "dan.magenheimer@oracle.com" <dan.magenheimer@oracle.com>, Randy
McAnally <rsm@fast-serv.com>, "xen-devel@lists.xensource.com" <xen-
devel@lists.xensource.com>
Sent: Wed, 30 Jan 2008 17:40:22 +0000
Subject: Re: [Xen-devel] Unresolved - qemu-dm crash under high dom0 disk load
> Sure. I'm confident to slip this one in without doing another rc.
>
> -- Keir
>
> On 30/1/08 17:37, "Dan Magenheimer" <dan.magenheimer@oracle.com> wrote:
>
> > 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" <rsm@fast-serv.com> 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=542
> >> http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1038
> >>
> >> In 1038, spam@abma.de _incorrectly_ reports it is fixed in 3.1.1 -- Not
only
> >> can I find any evidence of this, I can EASILY reproduce the crash over
and
> >> 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.
> >
> >
> >
------- End of Original Message -------
prev parent reply other threads:[~2008-01-30 17:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-30 16:09 Unresolved - qemu-dm crash under high dom0 disk load Randy McAnally
2008-01-30 16:32 ` Keir Fraser
2008-01-30 17:19 ` Randy McAnally
2008-01-30 17:37 ` Dan Magenheimer
2008-01-30 17:40 ` Keir Fraser
2008-01-30 17:42 ` Randy McAnally [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080130174145.M33140@fast-serv.com \
--to=rsm@fast-serv.com \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=dan.magenheimer@oracle.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.