From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Fitzhardinge Subject: Re: Re: NX related build failure in latest pv_ops dom0 hackery tree Date: Thu, 16 Apr 2009 17:49:43 -0700 Message-ID: <49E7D227.3070001@goop.org> References: <20090404192338.GJ24960@edu.joroinen.fi> <49D840D4.1070701@goop.org> <1239555359.12706.4.camel@leto.intern.saout.de> <49E4BF6F.2010308@goop.org> <1239887761.30384.13.camel@leto.intern.saout.de> <49E7591E.3030402@goop.org> <1239919531.8028.31.camel@leto.intern.saout.de> <49E7B0B5.4070003@goop.org> <1239925535.9443.5.camel@leto.intern.saout.de> <1239926093.9443.7.camel@leto.intern.saout.de> <49E7C765.8040201@goop.org> <1239928496.9443.24.camel@leto.intern.saout.de> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1239928496.9443.24.camel@leto.intern.saout.de> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Christophe Saout Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org Christophe Saout wrote: > Ok, that seems to help. Also, there was an unfortunate mixup of the > kernels. The xen-tip/next kernel actually works fine as well (it's just > my merged one that didn't). Sorry about that. > !? When I diffed them, there were hardly any differences, and nothing which seemed relevant... > With vdso32=0 I could now get the hackery kernel to boot up completely. > For some reason the xen-tip/next also gets past the initramfs stage and > I can see it mount the root filesystem, but doesn't come up further than > that (the network never comes up and the last thing I see is netconsole > telling me the rootfs got mounted) > > Maybe I mixed something up again. Possible, it's quite late, I'll > follow up on this another time. > OK, thanks for looking at this. J