On Tue, May 05, 2009 at 01:10:43PM -0700, Jeremy Fitzhardinge wrote:
> Pasi Kärkkäinen wrote:
> >And here we go:
> >http://pasik.reaktio.net/xen/pv_ops-dom0-debug/pv_ops-dom0-bootlog-28-xen331-linux-2.6.30-rc3-next-crash-no-highpte.txt
> >
> >(XEN) d0:v0: unhandled page fault (ec=0003)
> >(XEN) Pagetable walk from c1268000:
> >
>
>
> Oh, look, we're not reserving the Xen pagetable, and this time we really
> should. Does this work for you?
>
Yes, this fixes the problem! Now xen-tip/next pv_ops dom0 boots OK for me,
just like dom0/hackery did earlier!
But there's more.. I was pretty surprised when I booted up my testbox,
using the serial console as usual, and in the end of the boot process login
prompt (getty) appeared on the VGA text console (tty1) !!
It seems this (or some other) patch has fixed the 32bit pv_ops dom0 console
problems aswell..
Next I tried without the serial console, and yes, now the VGA text console
works just like it does with the old 2.6.18 xenlinux tree! I can see the
pv_ops dom0 kernel boot messages after Xen boot messages just fine.
My grub.conf:
title Fedora Xen pv_ops dom0-test (2.6.30-rc3-tip)
root (hd0,0)
kernel /xen-3.3.gz dom0_mem=1024M loglvl=all guest_loglvl=all
module /vmlinuz-2.6.30-rc3-tip ro root=/dev/vg00/lv01
module /initrd-2.6.30-rc3-tip.img
No need to specify console= or earlyprintk= anymore!
Thanks for all the hard work and congratulations!
-- Pasi
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
Home