From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Fitzhardinge Subject: Re: Xen pv_ops dom0 2.6.32.13 issues Date: Wed, 09 Jun 2010 16:37:36 -0700 Message-ID: <4C1025C0.2070808@goop.org> References: <1742609046.4840453.1276126053830.JavaMail.root@vms170009.mailsrvcs.net> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1742609046.4840453.1276126053830.JavaMail.root@vms170009.mailsrvcs.net> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: greno@verizon.net Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org 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 >