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

[Xen-devel] Xen pv_ops dom0 2.6.32.13 issues

To: greno@xxxxxxxxxxx
Subject: [Xen-devel] Xen pv_ops dom0 2.6.32.13 issues
From: greno@xxxxxxxxxxx
Date: Wed, 09 Jun 2010 16:02:11 -0500 (CDT)
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 09 Jun 2010 14:11:46 -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

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.  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.  I had to rebuild the images from backups.  The domU's are running 2.6.32-16-server domU kernels (ubuntu).


-Gerry


May 19, 2010 09:01:00 PM, greno@xxxxxxxxxxx wrote:
On 05/19/2010 05:24 PM, Jeremy Fitzhardinge wrote:
> On 05/19/2010 02:09 PM, Gerry Reno wrote:
>
>> I am using a pv_ops dom0 kernel 2.6.32.12 with xen 4.0.0-rc8. My
>> domU's use 2.6.31-14-server ubuntu.
>>
>> When I try to ping another computer on the network from the domU I
>> still received this error:
>> Attempting to checksum a non-TCP/UDP packet, dropping a protocol 1 packet
>>
>> I thought this error was fixed somewhere around 2.6.32.10 but
>> apparently it is still in 2.6.32.12.
>>
>> How do I get around this problem?
>>
> I applied a patch to fix up a checksum bug in netback, but I realized I
> hadn't applied it to stable-2.6.32. Please try again (it will be
> 2.6.32.13) and tell me how it goes.
>
> Thanks,
> J
>
>
Jeremy, that fixed it. Thanks.

-Gerry


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