This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-users] domU boot failure with Xen 3.4.0

To: Xen User-List <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-users] domU boot failure with Xen 3.4.0
From: Martti Kuparinen <martti.kuparinen@xxxxxx>
Date: Fri, 07 Aug 2009 13:48:29 +0300
Delivery-date: Fri, 07 Aug 2009 03:49:17 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4A28BCA3.3050006@xxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <4A28BCA3.3050006@xxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird (X11/20090608)
Martti Kuparinen wrote:
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.

I just tried Xen 3.4.1 on my Debian 5.0 dom0 but my NetBSD/i386 5.0.1 domU still fails to start. This domU works perfectly on 3.3.2 dom0. Any ideas?

NetBSD 5.0.1 (XEN3PAE_DOMU) #5: Sat Aug  1 05:13:23 EEST 2009
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
0x00000002f850de70: 0x0000000031373003
panic: HYPERVISOR_mmu_update failed

fatal breakpoint trap in supervisor mode
trap type 1 code 0 eip c0395c9c cs 9 eflags 246 cr2 0 ilevel 6
Stopped in pid 0.12 (system) at netbsd:breakpoint+0x4:  popl    %ebp

Xen-users mailing list

<Prev in Thread] Current Thread [Next in Thread>
  • Re: [Xen-users] domU boot failure with Xen 3.4.0, Martti Kuparinen <=