Subject: Re: Xen i386PAE status
To: None <port-xen@netbsd.org>
From: Florian Heigl <floh@deranfangvomen.de>
List: port-xen
Date: 01/26/2008 21:07:36
Hi Manuel,
On Sun, Jan 20, 2008 at 10:18:00PM +0100, Manuel Bouyer wrote:
[...]
> I've put kernels at ftp://asim.lip6.fr/outgoing/bouyer/, in case someone
> doesn't want to wait.
I don't yet figure out why, but on my test the PAE install kernel crashed when Xen tries to start it on my debian xen host.
(XEN) domain_crash_sync called from entry.S (ff15b6a9)
(XEN) Domain 12 (vcpu#0) crashed on cpu#0:
(XEN) ----[ Xen-3.0.3-1 x86_32p debug=n Not tainted ]----
(XEN) CPU: 0
(XEN) EIP: e019:[<c0222c64>]
(XEN) EFLAGS: 00000282 CONTEXT: guest
(XEN) eax: 00000000 ebx: 00000000 ecx: 00000000 edx: c02605b4
(XEN) esi: 00000000 edi: c0a00000 ebp: c025a950 esp: c025a928
(XEN) cr0: 8005003b cr4: 000006b0 cr3: 3deec000 cr2: 00000001
(XEN) ds: e021 es: e021 fs: 0000 gs: 0000 ss: e021 cs: e019
(XEN) Guest stack trace from esp=c025a928:
(XEN) 00000000 c0222c64 0001e019 00010082 c02580c2 c0a00000 c025a980 c01da720
(XEN) 00000000 c02580c2 c025a980 c01da735 00000000 00000000 c025a980 c01da6fa
(XEN) 00000000 00000000 00000000 00000000 c025a98c 00000100 c025a9b0 c01daff1
(XEN) c0253b04 c02220b7 00000000 00000000 00000000 00000000 3dee1001 c025a9bc
(XEN) c025aa44 00007ff0 c025aa60 c02227c7 c02580c2 00007ff0 c025aa60 c022279b
(XEN) 3dede000 00000000 00000000 00000000 00000000 00008000 c07f1000 c07e6000
(XEN) c07f2000 c07fafd8 007fb000 00000000 00000000 0003deed 0003deee c07ee000
(XEN) 007f1000 00000000 c07f2000 c07f7000 c025a000 c07fc000 00000005 c07f7000
(XEN) c07fc000 c07fc000 007f5000 00000000 00000000 c0a00000 00000000 00000002
(XEN) 0003dee1 00000000 00000000 00000005 c07f1000 00000005 c025aa90 c02229ad
(XEN) 00000005 00000000 0000c000 0000c000 00000008 c07f1000 c07e6000 746e6543
(XEN) c07e3200 c0789f00 00000000 c0100041 00000000 00000000 00000000 c0241500
(XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
(XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000 c02417c0
(XEN) c023e7e0 00000000 00000000 00000000 00000000 00000000 00000000 00000000
(XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
(XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
(XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
(XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
(XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
my config file - seems not too out of the ordinary, i uncompressed the kernel
after 1st crash, but that was just a random idea, no good.
kernel = '/xen/kernels/netbsd-INSTALL_XEN3PAE_DOMU'
memory = '64'
disk = [ 'phy:vgxen/nb-test01-disk,sda1,w', 'phy:vgxen/nb-test01-swap,sda2,w' ]
name = 'nb-test01'
vif = [ 'vifname=vif.nb-test01,bridge=xenbr0' ]
xm info:
[...]
xen_major : 3
xen_minor : 0
xen_extra : .3-1
xen_caps : xen-3.0-x86_32p
xen_pagesize : 4096 <--- is this evil?
platform_params : virt_start=0xf5800000
xen_changeset : Tue Oct 17 22:09:52 2006 +0100
cc_compiler : gcc version 3.4.6 (Debian 3.4.6-5)
cc_compile_by : skx
cc_compile_domain : debian.org
xend.log output was massive thats why i put it on
http://www.pastebin.ca/873673 - as far as i can tell it was also useless.
the only uncommon thing about my system is the via c7 type cpu,
on this system i only use a PAE kernel because my bigger xen host needs it.
do you have any hint as to where i can look for a fix?
--
florian heigl http://deranfangvomen.de/
Uebrigens: Viele DV-Leiter reagieren auf die Frage, welche
Backup-Loesung sie einsetzen wuerden, dass sie zu weiteren
Aussagen nur bereit seien, wenn sie nicht zitiert werden.
(computerwoche, 1989)