Current-Users archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: XEN i386-PAE DomU under XEN x86-64 Dom0 doesnt work(panic: HYPERVISOR_mmu_update failed)
On Mon, Jun 16, 2008 at 02:22:52PM +0100, David Markey wrote:
> When trying to boot an i386 PAE kernel under a x86-64 Xen DomU i get this
> error (with a tr)
>
>
>
> Loaded initial symtab at 0xc09a4a38, strtab at
> 0xc09d972c, # entries 12590
> Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005,
> 2006, 2007, 2008
> The NetBSD Foundation, Inc. All rights reserved.
> Copyright (c) 1982, 1986, 1989, 1991, 1993
> The Regents of the University of California. All rights reserved.
>
> NetBSD 4.99.64 (INSTALL_XEN3PAE_DOMU) #0: Sun Jun 15 07:57:38 PDT 2008
> builds@wb28
> :/home/builds/ab/HEAD/i386/200806150002Z-obj/home/builds/ab/HEAD/src/sys/arch/i386/compile/INSTALL_XEN3PAE_DOMU
> total memory = 128 MB
> avail memory = 115 MB
> mainbus0 (root)
> hypervisor0 at mainbus0: Xen version 3.2
> vcpu0 at hypervisor0: AMD 686-class, 2475MHz, id 0x20fb1
> vcpu0: 8 page colors
> xenbus0 at hypervisor0: Xen Virtual Bus Interface
> xencons0 at hypervisor0: Xen Virtual Console Driver
> xencons0: using event channel 2
> npx0 at hypervisor0: using exception 16
> xenbus0: using event channel 1
> xbd0 at xenbus0 id 768: Xen Virtual Block Device Interface
> xennet0 at xenbus0 id 0: Xen Virtual Network Interface
> xennet0: MAC address 00:16:3e:00:54:01
> unknown type console at xenbus0 id 0 not configured
> xbd0: 9789 MB, 512 bytes/sect x 20048000 sectors
> raidattach: Asked for 8 units
> Kernelized RAIDframe activated
> Searching for RAID components...
> RAIDframe: can't get label for dev md0 (22)
> boot device: xbd0
> root on md0a dumps on md0b
> dump_misc_init: max_paddr = 0x8100000
> mountroot: trying lfs...
> mountroot: trying ffs...
> root file system type: ffs
> warning: no /dev/console
> init: copying out flags `-s' 3
> xpq_flush_queue: 3 entries
> 0x00000000338f4000: 0x0000000029044001
> 0x00000000338f4008: 0x0000000029053001
> 0x00000000338f4010: 0x000000002904a001
> panic: HYPERVISOR_mmu_update failed
>
> fatal breakpoint trap in supervisor mode
> trap type 1 code 0 eip c038002c cs 9 eflags 246 cr2 0 ilevel 6
> Stopped in pid 1.1 (init) at netbsd:breakpoint+0x4: popl %ebp
> db> tr
> breakpoint(c042b55f,ca8c9b18,c0922700,c02f38c5,0,5,0,0,ca8c9b28,3) at
> netbsd:bre
> akpoint+0x4
> panic(c042cefa,338f4010,0,2904a001,0,0,ca8c9bbc,c02f276c,ca8c9d18,0) at
> netbsd:p
> anic+0x1b2
> xpq_flush_queue(0,c041938c,64,ca8c9bb0,0,1f,0,ffff0011,6,338f4018) at
> netbsd:xpq
> _flush_queue+0xb2
> xpq_queue_tlb_flush(6,0,ca8c9bdc,c0389aa0,338f4010,0,2904a001,0,ca079f04,c09a2c4
> 0) at netbsd:xpq_queue_tlb_flush+0x19
> tlbflush(338f4010,0,2904a001,0,ca079f04,c09a2c40,ca0702a0,ca8c9da0,1,0) at
> netbs
> d:tlbflush+0x1a
> pmap_load(1,ca8c9d2c,c0100788,c02a62b2,ca8c9d18,bf7ffffd,3,0,ffffffff,ffffffff)
> a
> t netbsd:pmap_load+0x340
> do_pmap_load(c02a62b2,ca8c9d18,bf7ffffd,3,0,ffffffff,ffffffff,0,b0717,ffffffff)
> a
> t netbsd:do_pmap_load+0x16
> copyout(ca0702a0,0,c010006b,c0100063,c010006b,0,0,0,0,0) at
> netbsd:copyout+0x48
> db>
>
>
>
>
> I'm using Xen 3.2, I run other 386 PAE kernels and they work fine. Anyone
> any ideas?
Anything is 'xm dmesg' ? You may need to boot a debug Xen kernel to see
anything usefull ...
--
Manuel Bouyer <bouyer%antioche.eu.org@localhost>
NetBSD: 26 ans d'experience feront toujours la difference
--
Home |
Main Index |
Thread Index |
Old Index