From: Kevin Wolf <kwolf@redhat.com>
To: Chris Webb <chris@arachsys.com>
Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: Re: [Qemu-devel] qemu-kvm guest which won't 'cont' (emulation failure?)
Date: Mon, 24 Oct 2011 13:36:54 +0200 [thread overview]
Message-ID: <4EA54DD6.2090603@redhat.com> (raw)
In-Reply-To: <20111024112929.GX9917@arachsys.com>
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
next prev parent reply other threads:[~2011-10-24 11:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-24 10:00 qemu-kvm guest which won't 'cont' (emulation failure?) Chris Webb
2011-10-24 10:42 ` [Qemu-devel] " Kevin Wolf
2011-10-24 10:58 ` Chris Webb
2011-10-24 11:18 ` [Qemu-devel] " Kevin Wolf
2011-10-24 11:29 ` Chris Webb
2011-10-24 11:36 ` Kevin Wolf [this message]
2011-10-24 12:05 ` Chris Webb
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4EA54DD6.2090603@redhat.com \
--to=kwolf@redhat.com \
--cc=chris@arachsys.com \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).