From: Jeremy Fitzhardinge <jeremy@goop.org>
To: "Christopher S. Aker" <caker@theshore.net>
Cc: virtualization@lists.linux-foundation.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Xen-devel <xen-devel@lists.xensource.com>
Subject: Re: Xen paravirt frontend block hang
Date: Sun, 02 Mar 2008 07:35:13 -0800 [thread overview]
Message-ID: <47CAC931.1000107@goop.org> (raw)
In-Reply-To: <47C9F818.4020200@theshore.net>
Christopher S. Aker wrote:
> Jeremy Fitzhardinge wrote:
>> I've been running this all night without seeing any problem. I'm
>> using current x86.git#testing with a few local patches, but nothing
>> especially relevent-looking.
>
> Meh .. what backend are you using? We're using LVM volumes exported
> directly into the domUs like so:
>
> disk =[ 'phy:vg1/xencaker-56392,xvda,w', ... ]
>
>> Could you try the attached patch to see if it makes any difference?
>
> Unfortunately we're still in the same place... pv_ops kernels are
> still hanging after heavy disk IO:
>
> works - 2.6.18.x (from xen-unstable)
> hangs - 2.6.25-rc3-git3
> hangs - 2.6.25-rc3-git3 + your patch
>
> Any other suggestions or debugging I can provide that would be useful
> to squash this?
Are you running an SMP or UP domain? I found I could get hangs very
easily with UP (but I need confirm it isn't a result of some other very
experimental patches).
J
WARNING: multiple messages have this Message-ID (diff)
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: "Christopher S. Aker" <caker@theshore.net>
Cc: Xen-devel <xen-devel@lists.xensource.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
virtualization@lists.linux-foundation.org
Subject: Re: Xen paravirt frontend block hang
Date: Sun, 02 Mar 2008 07:35:13 -0800 [thread overview]
Message-ID: <47CAC931.1000107@goop.org> (raw)
In-Reply-To: <47C9F818.4020200@theshore.net>
Christopher S. Aker wrote:
> Jeremy Fitzhardinge wrote:
>> I've been running this all night without seeing any problem. I'm
>> using current x86.git#testing with a few local patches, but nothing
>> especially relevent-looking.
>
> Meh .. what backend are you using? We're using LVM volumes exported
> directly into the domUs like so:
>
> disk =[ 'phy:vg1/xencaker-56392,xvda,w', ... ]
>
>> Could you try the attached patch to see if it makes any difference?
>
> Unfortunately we're still in the same place... pv_ops kernels are
> still hanging after heavy disk IO:
>
> works - 2.6.18.x (from xen-unstable)
> hangs - 2.6.25-rc3-git3
> hangs - 2.6.25-rc3-git3 + your patch
>
> Any other suggestions or debugging I can provide that would be useful
> to squash this?
Are you running an SMP or UP domain? I found I could get hangs very
easily with UP (but I need confirm it isn't a result of some other very
experimental patches).
J
next prev parent reply other threads:[~2008-03-02 15:40 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-26 19:33 Xen paravirt frontend block hang Christopher S. Aker
2007-12-28 23:14 ` Jeremy Fitzhardinge
2007-12-29 1:12 ` Christopher S. Aker
2007-12-29 6:00 ` Jeremy Fitzhardinge
2008-01-29 0:22 ` Christopher S. Aker
2008-01-29 0:40 ` Jeremy Fitzhardinge
2008-01-29 1:04 ` Christopher S. Aker
2008-02-06 12:37 ` xming
2008-02-07 4:09 ` Jeremy Fitzhardinge
2008-02-07 14:12 ` xming
2008-02-28 20:03 ` Jeremy Fitzhardinge
2008-02-28 20:03 ` Jeremy Fitzhardinge
2008-02-28 20:03 ` Jeremy Fitzhardinge
2008-03-18 16:02 ` Jeremy Fitzhardinge
2008-02-28 20:00 ` Jeremy Fitzhardinge
2008-02-28 20:00 ` Jeremy Fitzhardinge
2008-02-28 20:00 ` Jeremy Fitzhardinge
2008-03-02 0:43 ` Christopher S. Aker
2008-03-02 0:43 ` Christopher S. Aker
2008-03-02 0:43 ` Christopher S. Aker
2008-03-02 15:35 ` Jeremy Fitzhardinge [this message]
2008-03-02 15:35 ` Jeremy Fitzhardinge
2008-03-02 16:03 ` Christopher S. Aker
2008-03-02 16:03 ` Christopher S. Aker
2008-03-18 16:01 ` [Xen-devel] " Jeremy Fitzhardinge
2008-03-18 16:01 ` Jeremy Fitzhardinge
2008-03-25 1:37 ` [Xen-devel] " Christopher S. Aker
2008-03-25 1:37 ` Christopher S. Aker
2008-03-25 1:37 ` [Xen-devel] " Christopher S. Aker
2008-03-18 16:01 ` Jeremy Fitzhardinge
2008-03-02 16:03 ` Christopher S. Aker
2008-03-02 15:35 ` Jeremy Fitzhardinge
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=47CAC931.1000107@goop.org \
--to=jeremy@goop.org \
--cc=caker@theshore.net \
--cc=linux-kernel@vger.kernel.org \
--cc=virtualization@lists.linux-foundation.org \
--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.