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] Re: 2.6.37-rc1 mainline domU - BUG: unable to handle ker

To: Sander Eikelenboom <linux@xxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Re: 2.6.37-rc1 mainline domU - BUG: unable to handle kernel paging request
From: Bruce Edge <bruce.edge@xxxxxxxxx>
Date: Mon, 15 Nov 2010 12:21:28 -0800
Cc: Boris Derzhavets <bderzhavets@xxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, Jeremy Fitzhardinge <jeremy@xxxxxxxx>, Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Delivery-date: Mon, 15 Nov 2010 12:22:48 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=rlSuHT0t8BuTWcB9m8Z+ptlhUgr8O5J/+C9ZGZY/b6E=; b=r15hB0L5mOGVc1TJJOZxWMc59TUqTxLahVbWjvQe9lqYMyQNI4l9Usnbg6f7B9XT2I 8lN1Z7QR32HkmG23GCDBMO42Xl8L98B2XlTkh3pIUMdsH4FWxxupvdR80+TAbPRVERe/ lfF+Vq2OJwbxO5GWu7sXKywH6BxVp1DRIih9Q=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=dUwZPjS4Y1BtOmbLQIJyZq/rq0GbQUU0jhEsH2TvODo7QRaHnPZjscxUQX5jfQVhlt i3+go89lvO+WMIvqVpEV3dlvcMaUYZEk6liHLEnNDTh7XQ8iBIaCiS6mmhydyRAGyVfg kegylU4ljEmxiafwnsdXC5vPeBLmSsE04esls=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1835258992.20101114175648@xxxxxxxxxxxxxx>
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>
References: <20101112170143.GC10339@xxxxxxxxxxxx> <503106.98736.qm@xxxxxxxxxxxxxxxxxxxxxxxxxxx> <1835258992.20101114175648@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Sun, Nov 14, 2010 at 8:56 AM, Sander Eikelenboom
<linux@xxxxxxxxxxxxxx> wrote:
> Hmmm have you tried do do a lot of I/O with something else as NFS ?
> That would perhaps pinpoint it to NFS doing something not completely 
> compatible with Xen.
>
> I'm not using NFS (I still use file: based guests, and i use glusterfs (fuse 
> based userspace cluster fs) to share diskspace to domU's via ethernet).

Sander,
I took a quick look at glusterfs and it uses the same nfs client:
http://www.gluster.com/community/documentation/index.php/Gluster_3.1:_Manually_Mounting_Volumes_Using_NFS
I'm assuming that this would cause the same problem on the VM as we're
seeing with NFS, unless it's really an Xen/dom0 NFS server problem
that triggering the domU nfs client crash.

Perhaps the context is different. I'm exporting filesystems to domU
from dom0 via NFS. Is that how you're using glusterfs, or are you
using it to host your file backed VM's storage? In the latter, that
may explain why you're not seeing these problems because you're not
using the nfs client on domU.


> I tried NFS in the past, but had some troubles setting it up, and even more 
> problems with disconnects.

What kind of NFS problems? It was working very well for us until this
problem cropped up.

-Bruce

>
> I haven't seen any "unable to handle page request" problems with my mix of 
> guest kernels, which includes some 2.6.37-rc1 kernels.
>
> --
>
> Sander
>
>
>
>
>
> Sunday, November 14, 2010, 5:37:59 PM, you wrote:
>
>> I've tested F14 DomU (kernel 
>> vmlinuz-2.6.37-0.1.rc1.git8.xendom0.fc14.x86_64) as NFS client and Xen 4.0.1 
>> F14 Dom0 (kernel vmlinuz-2.6.32.25-172.xendom0.fc14.x86_64) as NFS server . 
>> Copied 700 MB ISO images from NFS folder at Dom0 to DomU and scp'ed them 
>> back to Dom0. During about 30 - 40 min DomU ran pretty stable , regardless 
>> kernel crash as "unable to handle page request" was reported once by F14 
>> DomU, but it didn't actually crash DomU. Same excersises with replacement 
>> F14 by Ubuntu 10.04 Server results DomU crash in about several minutes. 
>> Dom0's instances dual boot on same development box ( Q9500,ASUS P5Q3,8GB)
>
>> Boris.
>
>> --- On Fri, 11/12/10, Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx> wrote:
>
>> From: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
>> Subject: Re: [Xen-devel] Re: 2.6.37-rc1 mainline domU - BUG: unable to 
>> handle kernel paging request
>> To: "Sander Eikelenboom" <linux@xxxxxxxxxxxxxx>
>> Cc: "Boris Derzhavets" <bderzhavets@xxxxxxxxx>, 
>> xen-devel@xxxxxxxxxxxxxxxxxxx, "Bruce Edge" <bruce.edge@xxxxxxxxx>, "Jeremy 
>> Fitzhardinge" <jeremy@xxxxxxxx>
>> Date: Friday, November 12, 2010, 12:01 PM
>
>> On Fri, Nov 12, 2010 at 05:27:43PM +0100, Sander Eikelenboom wrote:
>>> Hi Bruce,
>>>
>>> Perhaps handpick some kernels before and after the pulls of the xen patches 
>>> (pv-on-hvm etc) to begin with ?
>>> When you let git choose, especially with rc-1 kernels, you will end up with 
>>> kernels in between patch series, resulting in panics.
>
>> Well, just the bare-bone boot of PV guests with nothing fancy ought to work.
>
>> But that is the theory and ..
>>> > The git bisecting is slow going. I've never tried that before and I'm a 
>>> > git
>>> > rookie.
>>> > I picked 2.6.36 - 2.6.37-rc1 as the bisect range and my first 2 bisects 
>>> > all
>>> > panic at boot so I'm obviously doing something wrong.
>>> > I'll RTFM a bit more and keep at it.
>
>> .. as Bruce experiences this is not the case. Hmm..
>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@xxxxxxxxxxxxxxxxxxx
>> http://lists.xensource.com/xen-devel
>
>
>
>>
>
>
>
> --
> Best regards,
>  Sander                            mailto:linux@xxxxxxxxxxxxxx
>
>

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

<Prev in Thread] Current Thread [Next in Thread>