[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] Re: 2.6.37-rc1 mainline domU - BUG: unable to handle kernel paging request


  • To: Sander Eikelenboom <linux@xxxxxxxxxxxxxx>
  • From: Boris Derzhavets <bderzhavets@xxxxxxxxx>
  • Date: Sun, 14 Nov 2010 09:47:25 -0800 (PST)
  • Cc: Jeremy Fitzhardinge <jeremy@xxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, Bruce Edge <bruce.edge@xxxxxxxxx>, Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
  • Delivery-date: Sun, 14 Nov 2010 09:48:18 -0800
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:Cc:MIME-Version:Content-Type; b=YaDba//AeWdRzB6ewIDIK6WiKVRMT6tmKVSnoiXyZHpPYgbHTrHROAm9VGxdFfsh/SHf3kUis9hD76Ol/h4vhwiVx2my5nItmgfl7d8qxxn8FfdBhxgZu5zaTvizD26/GoNFtB+Ue6IiMdrDNMFRqj7naa2bhmDH3XVgMS5PYck=;
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

This is not exactly git8 . Michael Young applied attached patch on top of git8.
It's  his the most recent submission to fedora-xen.
http://koji.fedoraproject.org/koji/taskinfo?taskID=2598434


Boris.

--- On Sun, 11/14/10, Sander Eikelenboom <linux@xxxxxxxxxxxxxx> wrote:

From: Sander Eikelenboom <linux@xxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Re: 2.6.37-rc1 mainline domU - BUG: unable to handle kernel paging request
To: "Boris Derzhavets" <bderzhavets@xxxxxxxxx>
Cc: "Konrad Rzeszutek Wilk" <konrad.wilk@xxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, "Bruce Edge" <bruce.edge@xxxxxxxxx>, "Jeremy Fitzhardinge" <jeremy@xxxxxxxx>
Date: Sunday, November 14, 2010, 12:19 PM

Perhaps these patches (especially Stefano's) could make a difference ?

http://lkml.indiana.edu/hypermail/linux/kernel/1011.1/02348.html

I don't think these are applied to your domU kernel  since it's git8, it worth the shot i guess...

--
Sander

Sunday, November 14, 2010, 6:09:14 PM, you wrote:

>> Hmmm have you tried do do a lot of I/O with something else as NFS ?

> I've tried scp a lot from DomU to Dom0 on F14 no problems, on Ubuntu 10.04 Server
> DomU as NFS client cannot survive more then a 2-3 min with I/O generated by scp.
> If i unmount NFS share everything goes fine ( Ubuntu 10.04)

>> That would perhaps pinpoint it to NFS doing something not completely compatible with
> Xen.

> If DomU ( Ubuntu 10.04 ) is running  by 2.6.36 kernel there is no any NFS or other network related problems . Issue is specific for 2.6.37-rc1 kernel as kernel running DomU at Xen 4.0.1 Dom0 ( 2.6.32.25 pvops) on top of Ubuntu Lucid Server.

> Boris.





> -- On Sun, 11/14/10, Sander Eikelenboom <linux@xxxxxxxxxxxxxx> wrote:

> From: Sander Eikelenboom <linux@xxxxxxxxxxxxxx>
> Subject: Re: [Xen-devel] Re: 2.6.37-rc1 mainline domU - BUG: unable to handle kernel paging request
> To: "Boris Derzhavets" <bderzhavets@xxxxxxxxx>
> Cc: "Konrad Rzeszutek Wilk" <konrad.wilk@xxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, "Bruce Edge" <bruce.edge@xxxxxxxxx>, "Jeremy Fitzhardinge" <jeremy@xxxxxxxx>
> Date: Sunday, November 14, 2010, 11:56 AM

> 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).
> I tried NFS in the past, but had some troubles setting it up, and even more problems with disconnects.

> 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


Attachment: xen.next-2.6.37.patch.gz
Description: GNU Zip compressed data

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

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.