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 16:37:36 -0700 [thread overview]
Message-ID: <4C1025C0.2070808@goop.org> (raw)
In-Reply-To: <1742609046.4840453.1276126053830.JavaMail.root@vms170009.mailsrvcs.net>
On 06/09/2010 04:27 PM, greno@verizon.net wrote:
> blkbackd
Using phy: in your config file? That really isn't recommended because
it has poor integrity; the writes are buffered in dom0 so writes can be
reordered or lost on crash, and the guest filesystem can't maintain any
of its own integrity guarantees.
tap:aio: is more resilient, since the writes go directly to the device
without buffering.
That doesn't directly relate to your lockup issues, but it should
prevent filesystem corruption when they happen.
J
>
>
>
> Jun 9, 2010 07:13:23 PM, jeremy@goop.org wrote:
>
> On 06/09/2010 04:05 PM, greno@verizon.net wrote:
> > Jeremy,
> > The soft lockups seemed to be occurring in different systems. And I
> > could never make sense out of what was triggering them. I have not
> > mounted any file systems with "nobarriers" in guests. The guests are
> > all a single /dev/xvda. The underlying physical hardware is LVM over
> > RAID-1 arrays. I'm attaching dmesg, kern.log, and messages in case
> > these might be useful.
>
> Using what storage backend? blkback? blktap2?
>
> J
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
next prev parent reply other threads:[~2010-06-09 23: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
2010-06-09 23:27 ` greno
2010-06-09 23:37 ` Jeremy Fitzhardinge [this message]
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=4C1025C0.2070808@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).