From mboxrd@z Thu Jan  1 00:00:00 1970
From: Keir Fraser <keir.fraser@eu.citrix.com>
Subject: Re: hang on restore in 3.3.1
Date: Wed, 11 Feb 2009 10:21:36 +0000
Message-ID: <C5B85730.252D%keir.fraser@eu.citrix.com>
References: <AEC6C66638C05B468B556EA548C1A77D0162C6DD@trantor>
Mime-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <AEC6C66638C05B468B556EA548C1A77D0162C6DD@trantor>
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: James Harper <james.harper@bendigoit.com.au>, "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
List-Id: xen-devel@lists.xenproject.org




On 11/02/2009 09:51, "James Harper" <james.harper@bendigoit.com.au> wrote:

> 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?

Most interrupts come from qemu, since it emulates most devices. Switching
your qemu is a pretty easy test (build internal old version rather than
out-of-tree new version).

 -- Keir