[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: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
  • From: Boris Derzhavets <bderzhavets@xxxxxxxxx>
  • Date: Tue, 16 Nov 2010 12:43:28 -0800 (PST)
  • Cc: Jeremy Fitzhardinge <jeremy@xxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, Bruce Edge <bruce.edge@xxxxxxxxx>
  • Delivery-date: Tue, 16 Nov 2010 12:44:24 -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:In-Reply-To:MIME-Version:Content-Type; b=I5QBB3TVULBANYMW6/W45/UxNZrnaQiCnmSDPoeHl2I6aoDz2HmDxOz/Hi74cX8Ub61TLU248ZMeJrsXtxTvaGeYYZQrc4DSkBsFbBkull2a+Eowy9eGhHnYVqOKn5XNfRwO7T6XwgMXbWTMfw395kQWVgu3FrwFHS4gV/5L0tg=;
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

> Huh. I .. what? I am confused. I thought we established that the issue
> was not related to Xen PCI front? You also seem to uncomment the
> upstream.core.patches and the xen.pvhvm.patch - why?

I cannot uncomment upstream.core.patches and the xen.pvhvm.patch
it gives failed HUNKs

> Ok, they are.. v2.6.37-rc2 which came out today has the fixes

I am pretty sure rc2 doesn't contain everything from xen.next-2.6.37.patch,
gntdev's stuff for sure. I've built 2.6.37-rc2 kernel rpms and loaded
kernel-2.6.27-rc2.git0.xendom0.x86_64 under Xen 4.0.1.
Device /dev/xen/gntdev has not been created. I understand that it's
unrelated to DomU ( related to Dom0) , but once again with rc2 in DomU i cannot
get 3.2 GB copied over to DomU from NFS share at Dom0.
The best results for 2.6.37-rc1 + xen.next-2.6.37.patch + xen.pcifront.fixes.patch

Boris.



--- On Tue, 11/16/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: "Boris Derzhavets" <bderzhavets@xxxxxxxxx>
Cc: "Bruce Edge" <bruce.edge@xxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, "Jeremy Fitzhardinge" <jeremy@xxxxxxxx>
Date: Tuesday, November 16, 2010, 2:00 PM

On Tue, Nov 16, 2010 at 10:43:49AM -0800, Boris Derzhavets wrote:
> Today i've built vmlinuz-2.6.37-0.1.rc1.git8.xendom0.fc14.x86_64
> via Michael's http://koji.fedoraproject.org/koji/taskinfo?taskID=2598434
> and uncommented xen.pcifront.fixes.patch in kernel.spec, i.e.
>
> # Xen patches
> ApplyPatch xen.next-2.6.37.patch
> # ApplyPatch xen.upstream.core.patch
> ApplyPatch xen.pcifront.fixes.patch
> # ApplyPatch xen.pvhvm.fixes.patch
>
> as a fesult a got kernel wich runs pretty stable NFS client at Xen 4.0.1
> F14 Dom0 (2.6.32.25-172.xendom0.fc14.x86_64).
>  
>   I was able several times copied from NFS folder F14's ISO image (3.2 GB)
> to DomU and scp'ed it back and didn't get any kernel crashing on DomU.

Huh. I .. what? I am confused. I thought we established that the issue
was not related to Xen PCI front? You also seem to uncomment the
upstream.core.patches and the xen.pvhvm.patch - why?

>
>  On Ubuntu 10.04 this kernel may be built as 2.6.37-rc1&git8 patched via
> xen.next-2.6.37.patch
> xen.pcifront.fixes.patch
> All required upstream patches may be taken (as well as 2 above)
> from  http://koji.fedoraproject.org/koji/taskinfo?taskID=2598434
>   I believe as soon as xen.pcifront.fixes.patch will be accepted by upstream
> NFS client issue on F14 will be gone

Ok, they are.. v2.6.37-rc2 which came out today has the fixes.

_______________________________________________
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®.