From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kevin Wolf Subject: Re: [Qemu-devel] qemu-kvm guest which won't 'cont' (emulation failure?) Date: Mon, 24 Oct 2011 13:36:54 +0200 Message-ID: <4EA54DD6.2090603@redhat.com> References: <20111024100037.GS9917@arachsys.com> <4EA54104.7000001@redhat.com> <20111024105826.GT9917@arachsys.com> <4EA5497F.3030507@redhat.com> <20111024112929.GX9917@arachsys.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org To: Chris Webb Return-path: Received: from mx1.redhat.com ([209.132.183.28]:32782 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755207Ab1JXLdu (ORCPT ); Mon, 24 Oct 2011 07:33:50 -0400 In-Reply-To: <20111024112929.GX9917@arachsys.com> Sender: kvm-owner@vger.kernel.org List-ID: Am 24.10.2011 13:29, schrieb Chris Webb: > Kevin Wolf 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