From: Jeremy Fitzhardinge <jeremy@goop.org>
To: greno@verizon.net
Cc: xen-devel@lists.xensource.com
Subject: Re: Xen pv_ops dom0 2.6.32.13 issues
Date: Wed, 09 Jun 2010 15:37:38 -0700 [thread overview]
Message-ID: <4C1017B2.90800@goop.org> (raw)
In-Reply-To: <1382341628.4833695.1276117331660.JavaMail.root@vms170009.mailsrvcs.net>
On 06/09/2010 02:02 PM, greno@verizon.net wrote:
>
> Ok, I've been running this 2.6.32.13 pv_ops dom0 kernel for several
> weeks and it has twice killed my domU's. I get numerous CPU soft
> lockup bug errors and at times it will freeze which means a power
> cycle boot.
The lockups are in dom0 or domU? Do the backtraces indicate a common
subsystem, or are they all over the place?
> This has resulted in things like:
> EXT-fs error (device dm-0): ext4_lookup: deleted inode reference
> EXT-fs error (device dm-0): ext4_lookup: deleted inode reference
> in the domU boots which has killed two of them.
What's your storage path from guest device to media? Are they using
barriers?
J
next prev parent reply other threads:[~2010-06-09 22:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-09 21:02 Xen pv_ops dom0 2.6.32.13 issues greno
2010-06-09 22:37 ` Jeremy Fitzhardinge [this message]
2010-06-09 23:27 ` greno
2010-06-09 23:37 ` Jeremy Fitzhardinge
2010-06-11 17:06 ` Which disk backend to use in domU? Neobiker
2010-06-11 17:42 ` Valtteri Kiviniemi
2010-06-11 17:53 ` Valtteri Kiviniemi
2010-06-11 18:11 ` Neobiker
2010-06-14 10:49 ` Jeremy Fitzhardinge
2010-06-14 10:57 ` Daniel Stodden
2010-06-14 11:01 ` Pasi Kärkkäinen
-- strict thread matches above, loose matches on Subject: below --
2010-06-09 23:05 Xen pv_ops dom0 2.6.32.13 issues greno
2010-06-09 23:11 ` Jeremy Fitzhardinge
2010-06-09 23:52 greno
2010-06-10 0:47 ` 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=4C1017B2.90800@goop.org \
--to=jeremy@goop.org \
--cc=greno@verizon.net \
--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 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).