Re: Fix for NetBSD Dom0 boot problem

[Petar Bogdanovic <list+2007%smokva.net@localhost>]

On Thu, Dec 06, 2007 at 09:08:17AM +0100, Christoph Egger wrote:
> On Wednesday 05 December 2007 23:11:31 Manuel Bouyer wrote:
> > On Wed, Dec 05, 2007 at 06:23:46PM +0100, Christoph Egger wrote:
> > > Hi Manuel,
> > >
> > > Please update pkgsrc's xenkernel3/patches/patch-ba:
> > >
> > > hg clone http://xenbits.xensource.com/staging/xen-unstable.hg/
> > > hg diff -p -r16534 -r16535 >netbsd_dom0_bootfix.diff
> > >
> > > The content of netbsd_dom0_bootfix.diff should match this:
> > > http://xenbits.xensource.com/staging/xen-unstable.hg/rev/c67d024fdd2d
> > >
> > > Add this diff to above patch-ba.
> > >
> > >
> > > This fixes a NetBSD Dom0 Xen-amd64 boot problem for me, which I have
> > > with Xen 3.1.x and Xen-unstable. The Xen crash output is below. The crash
> > > happened right before NetBSD loaded the symbol table.
> > >
> > > The bug was a trampoline mapping leaking into Dom0s address space.
> > > And the bug was hit when the Dom0 freed the pagetable.
> > >
> > > Linux Dom0 uses the builder-provided pagetable as its kernel idle
> > > pagetable. So it never frees the pagetable and so never hit the bad path.
> > >
> > > Oh, I have no idea how you got NetBSD Dom0 booting without that fix.
> >
> > Yes, I did it see that problem too. It crashes when it tries to unpin the
> > L4 page table provided by Xen. I debugged it and came with patch-cy in
> > xenkernel3. I now have commited the Xen offical fix, and removed patch-cy
> > which should have never been there in the first place (the same file
> > patched twice ...) Thanks !
> 
> You're welcome.
> 
> Oh, I see you updated pkgsrc to Xen 3.1.2.

FYI, Manuel: I was not able to fetch xen-3.1.2-src.tgz from 
${MASTER_SITE_LOCAL}.

        fetch: Unable to fetch expected file xen-3.1.2-src.tgz
        *** Error code 1

        Stop.
        make: stopped in /usr/pkgsrc/sysutils/xentools3

        --

        $ wget 
http://ftp.NetBSD.org/pub/NetBSD/packages/distfiles/xen-3.1.2-src.tgz
        (...)
        22:58:27 ERROR 404: Not Found.