WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] hang on restore in 3.3.1

To: James Harper <james.harper@xxxxxxxxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] hang on restore in 3.3.1
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Wed, 11 Feb 2009 09:45:13 +0000
Cc:
Delivery-date: Wed, 11 Feb 2009 01:45:41 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <AEC6C66638C05B468B556EA548C1A77D0162C6DA@trantor>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcmLIUlAfaq+PtOOS4GuTmMb1z1qKQBA3KpwAAIs6oU=
Thread-topic: [Xen-devel] hang on restore in 3.3.1
User-agent: Microsoft-Entourage/12.15.0.081119
On 11/02/2009 08:45, "James Harper" <james.harper@xxxxxxxxxxxxxxxx> wrote:

> Now I'm seeing the same thing but on vector 0x93 instead. There is
> nothing on that vector. It appears that when xen is restoring my domain,
> an interrupt line is getting 'stuck' somehow, as the hang occurs as soon
> as I enable interrupts after doing the restore... any suggestions?

Not for a line that isn't connected up. Usually this is due to bad restore
of the evtchn callback irq, or bad restore of irqs from qemu. With 3.3 you
could of course try reverting to the in-tree qemu (CONFIG_QEMU=ioemu) and
see if that makes the problem go away.

> Can anyone confirm that "INJ_VIRQ [ dom:vcpu = 0x00000062, vector =
> 0x83, fake = 0 ]" does actually imply that an interrupt is being set in
> my DomU, and that the vector is the actual offset into the vector table?

Yes that's right.

 -- Keir



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel