virtualization.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: "Christopher S. Aker" <caker@theshore.net>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: virtualization@lists.linux-foundation.org
Subject: Re: Xen paravirt frontend block hang
Date: Mon, 28 Jan 2008 19:22:15 -0500	[thread overview]
Message-ID: <479E71B7.7060207@theshore.net> (raw)
In-Reply-To: <47758352.5040504@goop.org>

Jeremy Fitzhardinge wrote:
> Christopher S. Aker wrote on 12/26/07 2:33 PM,
>> Sorry for the noise if this isn't the appropriate venue for this.  I
>> posted this last month to xen-devel:
>>
>> http://lists.xensource.com/archives/html/xen-devel/2007-11/msg00777.html
>>
>> I can reliably cause a paravirt_ops Xen guest to hang during intensive
>> IO.  My current recipe is an untar/tar loop, without compression, of a
>> kernel tree.  For example:
>>
>> wget http://kernel.org/pub/linux/kernel/v2.6/linux-2.6.23.tar.bz2
>> bzip2 -d linux-2.6.23.tar.bz2
>>
>> while true;
>>   date
>>   tar xf linux-2.6.23.tar
>>   tar cf linux-2.6.23.tar linux-2.6.23
>> done
>>
>> After a few loops, anything that touches the xvd device that hung will
>> get stuck in D state.
>>
>> This happens on both a 2.6.16 and 2.6.18 dom0 (3.1.2 tools).  Paravirt
>> guests I've tried that exhibit the problem: 2.6.23.8, 2.6.23.12, and
>> 2.6.24-rc6.  It does *not* occur using the Xensource 2.6.18 domU tree
>> from 3.1.2.  In all cases, the host continues to run fine, nothing out
>> of the ordinary is logged on the dom0 side, xenstore reports the
>> status of the devices is fine.
>>
>> Can anyone reproduce this problem, or let me know what else I can
>> provide to help track this down? 
> 
> Hi,
> 
> I'll try to track this down asap.  Have you tried any other kernel
> versions?  In other words, did it just start happening, or its always
> done it?  Also, could you try 2.6.24-rc6, just to make sure it hasn't
> already been fixed (which is possible if its something that happened in
> a higher layer or something).

Were you able to give this a try?  Still doing it on pv_ops 2.6.24.

Thanks,
-Chris

  parent reply	other threads:[~2008-01-29  0:22 UTC|newest]

Thread overview: 18+ 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 [this message]
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-03-18 16:02               ` Jeremy Fitzhardinge
2008-02-28 20:00 ` Jeremy Fitzhardinge
     [not found] ` <47C712EF.1060703@goop.org>
2008-03-02  0:43   ` Christopher S. Aker
     [not found]   ` <47C9F818.4020200@theshore.net>
2008-03-02 15:35     ` Jeremy Fitzhardinge
     [not found]     ` <47CAC931.1000107@goop.org>
2008-03-02 16:03       ` Christopher S. Aker
     [not found]       ` <47CACFBE.5010007@theshore.net>
2008-03-18 16:01         ` [Xen-devel] " Jeremy Fitzhardinge
     [not found]         ` <47DFE75B.7080404@goop.org>
2008-03-25  1:37           ` Christopher S. Aker

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=479E71B7.7060207@theshore.net \
    --to=caker@theshore.net \
    --cc=jeremy@goop.org \
    --cc=virtualization@lists.linux-foundation.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).