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

Re: [Xen-devel] xen-hypervisor-4.3-amd64 4.3.0-3+b1 -> Intel M/B, I/O virt. enabled, start vm -> Kernel panic

To: Jo Mills <jo@xxxxxxxxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxx>
From: David Vrabel <david.vrabel@xxxxxxxxxx>
Date: Tue, 20 May 2014 11:14:30 +0100
Delivery-date: Tue, 20 May 2014 10:14:37 +0000
List-id: Xen developer discussion <xen-devel.lists.xen.org>

On 17/05/14 18:46, Jo Mills wrote:
> 
>     [  498.336430] ---[ end trace b9630577ecf84cd8 ]---
>     [  498.340053] Kernel panic - not syncing: Fatal exception in interrupt
>     (XEN) Domain 0 crashed: 'noreboot' set - not rebooting.

We need the full backtrace from the kernel.

David

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel

Follow-Ups:
- Re: [Xen-devel] xen-hypervisor-4.3-amd64 4.3.0-3+b1 -> Intel M/B, I/O virt. enabled, start vm -> Kernel panic
  - From: Ian Campbell

References:
- [Xen-devel] xen-hypervisor-4.3-amd64 4.3.0-3+b1 -> Intel M/B, I/O virt. enabled, start vm -> Kernel panic
  - From: Jo Mills

Prev by Date: Re: [Xen-devel] [PATCH] Don't track all memory when enabling log dirty to track vram
Next by Date: Re: [Xen-devel] xen-hypervisor-4.3-amd64 4.3.0-3+b1 -> Intel M/B, I/O virt. enabled, start vm -> Kernel panic
Previous by thread: Re: [Xen-devel] xen-hypervisor-4.3-amd64 4.3.0-3+b1 -> Intel M/B, I/O virt. enabled, start vm -> Kernel panic
Next by thread: Re: [Xen-devel] xen-hypervisor-4.3-amd64 4.3.0-3+b1 -> Intel M/B, I/O virt. enabled, start vm -> Kernel panic
Index(es):
- Date
- Thread

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