[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-users] domU boot failure with Xen 3.4.0

My domU (32-bit NetBSD) is running without any problems on 64-bit Debian 5.0.1 dom0 with self-compiled Xen 3.3.1. I upgraded our secondary dom0 to 3.4.0 (with kernel) and started my domU but it panics early in the boot.

# xm create -c /xen/conf/mydomain.org
Using config file "/xen/conf/mydomain.org".
Started domain mydomain.org (id=1)
Loaded initial symtab at 0xc04dfdb8, strtab at 0xc05159ec, # entries 12823
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 5.0.0_PATCH (XEN3PAE_DOMU) #0: Mon May 18 08:50:17 EEST 2009

total memory = 512 MB
avail memory = 496 MB
mainbus0 (root)
hypervisor0 at mainbus0: Xen version 3.4
vcpu0 at hypervisor0: Intel 686-class, 2992MHz, id 0x10676
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
xbd0 at xenbus0 id 2048: Xen Virtual Block Device Interface
xpq_flush_queue: 1 entries
0x00000002f8509e70: 0x00000000335cc003
panic: HYPERVISOR_mmu_update failed

"xm dmesg" shows this:

(XEN) mm.c:804:d1 Error getting mfn 335cc (pfn 5555555555555555) from L1 entry 00000000335cc003 for dom1

Any ideas what's wrong?


Xen-users mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.