All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Kevin Wolf <kwolf@redhat.com>,
	Jan Kiszka <jan.kiszka@siemens.com>,
	qemu-devel@nongnu.org, Markus Armbruster <armbru@redhat.com>,
	Stefan Hajnoczi <stefanha@gmail.com>,
	Jiri Denemark <jdenemar@redhat.com>,
	Luiz Capitulino <lcapitulino@redhat.com>
Subject: Re: [Qemu-devel] QMP: RFC: I/O error info & query-stop-reason
Date: Fri, 3 Jun 2011 15:03:03 +0100	[thread overview]
Message-ID: <20110603140303.GQ32642@redhat.com> (raw)
In-Reply-To: <4DE8E6E1.4000909@codemonkey.ws>

On Fri, Jun 03, 2011 at 08:51:29AM -0500, Anthony Liguori wrote:
> On 06/03/2011 08:41 AM, Jan Kiszka wrote:
> >On 2011-06-03 15:26, Anthony Liguori wrote:
> >>I think what we're getting at is the need for an enumeration.  So let's
> >>introduce one.  Here's what I propose:
> >>
> >>SQMP
> >>query-status
> >>------------
> >>
> >>Return a json-object with the following information:
> >>
> >>- "running": true if the VM is running, or false if it is paused
> >>(json-bool)
> >>- "singlestep": true if the VM is in single step mode,
> >>                 false otherwise (json-bool)
> >>- "status": one of the following values (json-string) (optional)
> >>       "prelaunch" - QEMU was started with -S and guest has not started
> >>       "running" - guest is actively running
> >>       "singlestep" - guest is running in single step mode
> >
> >"singlestep" is just a subset of "debug" stops. Better use the latter.
> >
> >>       "paused" - guest has been paused via the 'stop' command
> >>       "postmigrate" - guest is paused following a successful 'migrate'
> >>       "shutdown" - guest is shut down (and -no-shutdown is in use)
> >>       "io-error" - the last IOP has failed and the device is configured
> >>to pause on I/O errors
> >>       "watchdog-error" - the watchdog action is configured to pause and
> >>has been triggered
> >
> >And "panic" or "internal-error".
> 
> Can you add the request help spec text too?  Is "internal-error" a
> KVM emulation error?  If so, I'd rather make it
> "kvm-emulation-error".

Yeah, its for the kvm-all.c code which calls vm_stop(VMSTOP_PANIC);
when it gets either an internal error, or an unhandled exit.

Regards,
Daniel
-- 
|: http://berrange.com      -o-    http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org              -o-             http://virt-manager.org :|
|: http://autobuild.org       -o-         http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org       -o-       http://live.gnome.org/gtk-vnc :|

  parent reply	other threads:[~2011-06-03 14:03 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-01 21:12 [Qemu-devel] QMP: RFC: I/O error info & query-stop-reason Luiz Capitulino
2011-06-01 21:35 ` Anthony Liguori
2011-06-02  9:06   ` Daniel P. Berrange
2011-06-02 13:08     ` Anthony Liguori
2011-06-02 13:24       ` Jiri Denemark
2011-06-02 14:02         ` Anthony Liguori
2011-06-02 18:01           ` Luiz Capitulino
2011-06-02 18:32             ` Anthony Liguori
2011-06-02 18:57               ` Luiz Capitulino
2011-06-02 19:35                 ` Anthony Liguori
2011-06-03  9:26             ` Daniel P. Berrange
2011-06-03 12:43               ` Anthony Liguori
2011-06-03 12:57                 ` Daniel P. Berrange
2011-06-03 13:26                   ` Anthony Liguori
2011-06-03 13:39                     ` Daniel P. Berrange
2011-06-03 13:44                       ` Luiz Capitulino
2011-06-03 14:01                         ` Anthony Liguori
2011-06-03 13:41                     ` Jan Kiszka
2011-06-03 13:51                       ` Anthony Liguori
2011-06-03 13:59                         ` Jan Kiszka
2011-06-03 14:03                         ` Daniel P. Berrange [this message]
2011-06-06 11:21           ` Markus Armbruster
2011-06-02 17:57   ` Luiz Capitulino
2011-06-02 18:00     ` Anthony Liguori
2011-06-02 18:09       ` Luiz Capitulino
2011-06-02 18:33         ` Anthony Liguori
2011-06-02 19:13           ` Luiz Capitulino
2011-06-02 20:03             ` Anthony Liguori
2011-06-02 20:13               ` [Qemu-devel] [libvirt] " Eric Blake
2011-06-02 20:55                 ` Anthony Liguori
2011-06-06  9:25         ` [Qemu-devel] " Kevin Wolf
2011-06-06 11:27           ` Markus Armbruster
2011-06-06 13:09             ` Anthony Liguori
2011-06-06 13:08           ` Anthony Liguori
2011-06-06 15:27             ` Daniel P. Berrange
2011-06-06 15:30               ` Luiz Capitulino
2011-06-08 12:59                 ` Anthony Liguori
2011-06-07 14:46             ` Luiz Capitulino
2011-06-07 15:39               ` Anthony Liguori
2011-06-07 15:54                 ` Luiz Capitulino
2011-06-07 16:32                   ` Anthony Liguori
2011-06-07 17:43                     ` Luiz Capitulino
2011-06-07 18:43                       ` Anthony Liguori
2011-06-07 18:48                         ` Luiz Capitulino
2011-06-07 15:41               ` Markus Armbruster
2011-06-07 16:31                 ` Anthony Liguori
2011-06-06 11:13   ` Markus Armbruster
2011-06-06 11:28     ` Markus Armbruster

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=20110603140303.GQ32642@redhat.com \
    --to=berrange@redhat.com \
    --cc=anthony@codemonkey.ws \
    --cc=armbru@redhat.com \
    --cc=jan.kiszka@siemens.com \
    --cc=jdenemar@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=lcapitulino@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.com \
    /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.