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: "Keir Fraser" <keir.fraser@xxxxxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-devel] hang on restore in 3.3.1
From: "James Harper" <james.harper@xxxxxxxxxxxxxxxx>
Date: Wed, 11 Feb 2009 20:51:57 +1100
Cc:
Delivery-date: Wed, 11 Feb 2009 01:52:25 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <C5B84EA9.193C%keir.fraser@xxxxxxxxxxxxx>
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>
References: <AEC6C66638C05B468B556EA548C1A77D0162C6DA@trantor> <C5B84EA9.193C%keir.fraser@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcmLIUlAfaq+PtOOS4GuTmMb1z1qKQBA3KpwAAIs6oUAADJLIA==
Thread-topic: [Xen-devel] hang on restore in 3.3.1
> 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.
> 

What do you think the chances are of it being a qemu problem? the
xentrace code would indicate that it was the hypervisor asserting the
interrupt, but that wouldn't preclude qemu from being the originator of
the interrupt would it?

Thanks

James

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