From mboxrd@z Thu Jan  1 00:00:00 1970
From: Chris Webb <chris@arachsys.com>
Subject: Re: [Qemu-devel] qemu-kvm guest which won't 'cont' (emulation
 failure?)
Date: Mon, 24 Oct 2011 12:29:30 +0100
Message-ID: <20111024112929.GX9917@arachsys.com>
References: <20111024100037.GS9917@arachsys.com>
 <4EA54104.7000001@redhat.com>
 <20111024105826.GT9917@arachsys.com>
 <4EA5497F.3030507@redhat.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org
To: Kevin Wolf <kwolf@redhat.com>
Return-path: <kvm-owner@vger.kernel.org>
Received: from alpha.arachsys.com ([91.203.57.7]:56160 "EHLO
	alpha.arachsys.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1754820Ab1JXL3d (ORCPT <rfc822;kvm@vger.kernel.org>);
	Mon, 24 Oct 2011 07:29:33 -0400
Content-Disposition: inline
In-Reply-To: <4EA5497F.3030507@redhat.com>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

Kevin Wolf <kwolf@redhat.com> writes:

> In qemu 1.0 we'll have an extended 'info status' that includes the stop
> reason, but 0.14 doesn't have this yet (was committed to git master only
> recently).

Right, okay. I might take a look at cherry-picking and back-porting that to
our version of qemu-kvm if it's not too entangled with other changes. It
would be very useful in these situations.

> If you attach a QMP monitor (see QMP/README, don't forget to send the
> capabilities command, it's part of creating the connection) you will
> receive messages for I/O errors, though.

Thanks. I don't think I can do this with an already-running qemu-kvm that's
in a stopped state can I, only with a new qemu-kvm invocation and wait to
try to catch the problem again?

Cheers,

Chris.