[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] xen.git branch reorg / success with 2.6.30-rc3 pv_ops dom0
On Mon, May 18, 2009 at 03:57:07PM +0100, Ian Campbell wrote: > Hi Pasi, > > On Thu, 2009-05-07 at 13:24 -0400, Pasi Kärkkäinen wrote: > > On Wed, May 06, 2009 at 02:51:59PM -0700, Jeremy Fitzhardinge wrote: > > > Great! I'd be interested to know if you're still having HIGHPTE > > > problems. It may or may not have got fixed. > > > > > > > I just tried with CONFIG_HIGHPTE=y but that didn't seem to work: > > http://pasik.reaktio.net/xen/pv_ops-dom0-debug/pv_ops-dom0-bootlog-30-xen331-linux-2.6.30-rc3-next-crash-with-highpte.txt > > > > (XEN) mm.c:2006:d0 Bad type (saw 28000001 != exp e0000000) for mfn 6b0a6 > > (pfn 2c959) > > (XEN) mm.c:707:d0 Error getting mfn 6b0a6 (pfn 2c959) from L1 entry > > 000000006b0a6063 for dom0 > > (XEN) mm.c:3640:d0 ptwr_emulate: could not get_page_from_l1e() > > I thought I might have a poke at this, how do you go about reproducing > it? I've used your .config and it boots OK -- now I'm trying a kernbench > run since I think you mentioned compiling a kernel in domain 0 at one > point. > I can reproduce it every time like this: - boot into pv_ops dom0 kernel - run "make bzImage && make modules" - wait for the kernel compilation to finish.. - *crash*, before the compilation finishes, usually within 15-30mins > How much RAM does your host have? Are you running 32 or 64 bit > hypervisor? Which hypervisor version? From your .config I think your > dom0 kernel is 32 bit, right? > My host has 2GB of RAM. Hypervisor is 32bit PAE, Fedora 11 Xen 3.3.1-11 rpms. My dom0 kernel is 32bit PAE aswell. grub.conf: kernel /xen-3.3.gz dom0_mem=1024M module /vmlinuz-2.6.30-rc3-tip root=/dev/sda1 ro module /boot/initrd.img-2.6.30-rc3-tip I'm (was) using xen-tip/next. -- Pasi _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |