From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: Re: 2.6.37-rc1 mainline domU - BUG: unable to handle kernel paging request Date: Tue, 16 Nov 2010 16:15:03 -0500 Message-ID: <20101116211503.GA11118@dumpdata.com> References: <20101116190043.GB11549@dumpdata.com> <531995.75322.qm@web56101.mail.re3.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <531995.75322.qm@web56101.mail.re3.yahoo.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Boris Derzhavets Cc: Jeremy Fitzhardinge , xen-devel@lists.xensource.com, Bruce Edge List-Id: xen-devel@lists.xenproject.org On Tue, Nov 16, 2010 at 12:43:28PM -0800, Boris Derzhavets wrote: > > 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 Uhh.. I am even more confused. > > > 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. So what I think you are saying is that you keep on getting the bug in DomU? Is the stack-trace the same as in rc1?