From: Chris Webb <chris@arachsys.com>
To: Kevin Wolf <kwolf@redhat.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 12:29:30 +0100 [thread overview]
Message-ID: <20111024112929.GX9917@arachsys.com> (raw)
In-Reply-To: <4EA5497F.3030507@redhat.com>
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.
next prev parent reply other threads:[~2011-10-24 11:29 UTC|newest]
Thread overview: 9+ 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:00 ` [Qemu-devel] " Chris Webb
2011-10-24 10:42 ` Kevin Wolf
2011-10-24 10:58 ` Chris Webb
2011-10-24 10:58 ` [Qemu-devel] " Chris Webb
2011-10-24 11:18 ` Kevin Wolf
2011-10-24 11:29 ` Chris Webb [this message]
2011-10-24 11:36 ` Kevin Wolf
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=20111024112929.GX9917@arachsys.com \
--to=chris@arachsys.com \
--cc=kvm@vger.kernel.org \
--cc=kwolf@redhat.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.