WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Xen pv_ops dom0 2.6.32.13 issues

To: jeremy@xxxxxxxx
Subject: Re: [Xen-devel] Xen pv_ops dom0 2.6.32.13 issues
From: greno@xxxxxxxxxxx
Date: Wed, 09 Jun 2010 18:05:31 -0500 (CDT)
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 09 Jun 2010 16:07:07 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
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.

-Gerry



Jun 9, 2010 06:38:00 PM, jeremy@xxxxxxxx wrote:
On 06/09/2010 02:02 PM, greno@xxxxxxxxxxx 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

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

Attachment: dmesg
Description: Binary data

Attachment: kern.log
Description: Binary data

Attachment: messages
Description: Binary data

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel