> 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? Yes. When i want to get 1-2 hr of stable work :- # service network restart # service nfs restart at Dom0. I also believe that presence of xen-pcifront.fix.patch is making things much more stable on F14. Boris. --- On Tue, 11/16/10, Konrad Rzeszutek Wilk wrote: From: Konrad Rzeszutek Wilk Subject: Re: [Xen-devel] Re: 2.6.37-rc1 mainline domU - BUG: unable to handle kernel paging request To: "Boris Derzhavets" Cc: "Jeremy Fitzhardinge" , xen-devel@lists.xensource.com, "Bruce Edge" Date: Tuesday, November 16, 2010, 4:15 PM 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?