From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([140.186.70.92]:58662)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <kwolf@redhat.com>) id 1RIImt-000317-H6
	for qemu-devel@nongnu.org; Mon, 24 Oct 2011 07:33:52 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <kwolf@redhat.com>) id 1RIIms-0005S8-En
	for qemu-devel@nongnu.org; Mon, 24 Oct 2011 07:33:51 -0400
Received: from mx1.redhat.com ([209.132.183.28]:40639)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <kwolf@redhat.com>) id 1RIIms-0005Rs-3p
	for qemu-devel@nongnu.org; Mon, 24 Oct 2011 07:33:50 -0400
Message-ID: <4EA54DD6.2090603@redhat.com>
Date: Mon, 24 Oct 2011 13:36:54 +0200
From: Kevin Wolf <kwolf@redhat.com>
MIME-Version: 1.0
References: <20111024100037.GS9917@arachsys.com> <4EA54104.7000001@redhat.com>
	<20111024105826.GT9917@arachsys.com> <4EA5497F.3030507@redhat.com>
	<20111024112929.GX9917@arachsys.com>
In-Reply-To: <20111024112929.GX9917@arachsys.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [Qemu-devel] qemu-kvm guest which won't 'cont' (emulation
	failure?)
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Chris Webb <chris@arachsys.com>
Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org

Am 24.10.2011 13:29, schrieb Chris Webb:
> 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.

I'm afraid that it depends on many other changes, but you can try.

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

Good point... The only other thing that I can think of would be
attaching gdb and setting a breakpoint in vm_stop() or something.

Kevin