On Tue, Jun 19, 2007 at 09:23:04PM +0900, Kazushi Marukawa wrote:
> Hi,
> 
> Manuel, Thanks for the support of Xen 3.1.
> 
> However, Xen 3.1 is not working for me.  I got following
> error when I tried to run NetBSD as DomU under NetBSD Dom0.
> I am using Xen on a PC box with Core Solo T2300.
> 
> xvif15.0: Ethernet address aa:00:00:51:02:f1
> (XEN) Unhandled page fault in domain 15 on VCPU 0 (ec=0000)
> (XEN) Pagetable walk from c0100000:
> (XEN)  L2[0x300] = 5e371067 0000044a
> (XEN)  L1[0x100] = 00000000 ffffffff
> (XEN) domain_crash_sync called from entry.S (ff164d89)
> (XEN) Domain 15 (vcpu#0) crashed on cpu#1:
> (XEN) ----[ Xen-3.1.0  x86_32  debug=n  Not tainted ]----
> (XEN) CPU:    1
> (XEN) EIP:    e019:[<c0100000>]
> (XEN) EFLAGS: 00010202   CONTEXT: guest
> (XEN) eax: 00000000   ebx: 00000000   ecx: 00000000   edx: 00000000
> (XEN) esi: c0546000   edi: 00000000   ebp: 00000000   esp: c054d000
> (XEN) cr0: 8005003b   cr4: 000026d0   cr3: 5e372000   cr2: c0100000
> (XEN) ds: e021   es: e021   fs: e021   gs: e021   ss: e021   cs: e019
> (XEN) Guest stack trace from esp=c054d000:
> (XEN)   Fault while accessing guest memory.

This looks a lot like the bug I fixed in dom0 support recently. You need a
very recent current or 4.0 kernel for xen3.1  dom0 (newer than
2007/06/13 10:38:44, which is the time when the bug fix was pulled up to
netbsd-4).

-- 
Manuel Bouyer <bouyer@antioche.eu.org>
     NetBSD: 26 ans d'experience feront toujours la difference
--