Re: Re: xen 4.1.1 with current linus tree as dom0 [ 0.000000] BUG: unable to handle kernel NULL pointer dereference at (null) [ 0.000000] IP: [<ffffffff810074d4>] xen_set_pte+0x24/0xe0

[Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>]

On Wed, Aug 03, 2011 at 05:05:24PM +0200, Sander Eikelenboom wrote:
> Hi Konrad,
> 
> Thx, after applying those patches it boots as dom0 and xen-pciback seems to work as well from my first tests.
> The compile problems reported in my earlier mail are still present (related to tracing and i think jeremy's patches).
> 
> Something that catched my eye when doing a make menuconfig:
>           <*>   Xen virtual block device support
>           <*>   Block-device backend driver
> 
> I think the backend description should also start with "Xen" as all xen specific drivers do ?

Yup. let me write a patch for that.
> 
> --
> Sander
> 
> 
> Wednesday, August 3, 2011, 3:51:52 PM, you wrote:
> 
> > On Wed, Aug 03, 2011 at 09:41:29AM -0400, Konrad Rzeszutek Wilk wrote:
> >> On Wed, Aug 03, 2011 at 01:18:24PM +0200, Sander Eikelenboom wrote:
> >> > Hi Jeremy/Konrad,
> >> > 
> >> > I'm still trying to get the current linus tree (commit ed8f37370d83e695c0a4fa5d5fc7a83ecb947526) to boot as a dom0 kernel under a xen 4.1.1 hypervisor.
> >> > But still can't boot (after compiling with tracers disabled).
> >> 
> >> Yeah, there is a bug introduced by Andy. Here is a patchset that fixes it:
> >> 
> >> http://marc.info/?i=cover.1311736366.git.luto@mit.edu
> 
> > Oh, and a new version is http://marc.info/?i=cover.1312378163.git.luto@mit.edu
> >> 
> >> _______________________________________________
> >> Xen-devel mailing list
> >> Xen-devel@lists.xensource.com
> >> http://lists.xensource.com/xen-devel
> 
> 
> 
> -- 
> Best regards,
>  Sander                            mailto:linux@eikelenboom.it