qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Luiz Capitulino <lcapitulino@redhat.com>
To: qemu-devel@nongnu.org
Cc: pbonzini@redhat.com, aliguori@us.ibm.com, jan.kiszka@siemens.com,
	eblake@redhat.com, quintela@redhat.com
Subject: [Qemu-devel] [PATCH 1/4] QError: Introduce new errors for the migration command
Date: Mon, 12 Mar 2012 16:58:57 -0300	[thread overview]
Message-ID: <1331582340-4611-2-git-send-email-lcapitulino@redhat.com> (raw)
In-Reply-To: <1331582340-4611-1-git-send-email-lcapitulino@redhat.com>

The new errors are QERR_MIGRATION_ACTIVE and QERR_MIGRATION_NOT_SUPPORTED,
which are going to be used by the QAPI converted migration command.

Signed-off-by: Luiz Capitulino <lcapitulino@redhat.com>
---
 qerror.c |    8 ++++++++
 qerror.h |    6 ++++++
 2 files changed, 14 insertions(+)

diff --git a/qerror.c b/qerror.c
index f55d435..41c729a 100644
--- a/qerror.c
+++ b/qerror.c
@@ -193,6 +193,14 @@ static const QErrorStringTable qerror_table[] = {
         .desc      = "Using KVM without %(capability), %(feature) unavailable",
     },
     {
+        .error_fmt = QERR_MIGRATION_ACTIVE,
+        .desc      = "There's a migration process in progress",
+    },
+    {
+        .error_fmt = QERR_MIGRATION_NOT_SUPPORTED,
+        .desc      = "State blocked by non-migratable device '%(device)'",
+    },
+    {
         .error_fmt = QERR_MIGRATION_EXPECTED,
         .desc      = "An incoming migration is expected before this command can be executed",
     },
diff --git a/qerror.h b/qerror.h
index e26c635..e16f9c2 100644
--- a/qerror.h
+++ b/qerror.h
@@ -166,6 +166,12 @@ QError *qobject_to_qerror(const QObject *obj);
 #define QERR_KVM_MISSING_CAP \
     "{ 'class': 'KVMMissingCap', 'data': { 'capability': %s, 'feature': %s } }"
 
+#define QERR_MIGRATION_ACTIVE \
+    "{ 'class': 'MigrationActive', 'data': {} }"
+
+#define QERR_MIGRATION_NOT_SUPPORTED \
+    "{ 'class': 'MigrationNotSupported', 'data': {'device': %s} }"
+
 #define QERR_MIGRATION_EXPECTED \
     "{ 'class': 'MigrationExpected', 'data': {} }"
 
-- 
1.7.9.2.384.g4a92a

  reply	other threads:[~2012-03-12 19:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-12 19:58 [Qemu-devel] [PATCH v3 0/4] qapi: Convert migrate Luiz Capitulino
2012-03-12 19:58 ` Luiz Capitulino [this message]
2012-03-12 19:58 ` [Qemu-devel] [PATCH 2/4] Error: Introduce error_copy() Luiz Capitulino
2012-03-12 19:58 ` [Qemu-devel] [PATCH 3/4] Purge migration of (almost) everything to do with monitors Luiz Capitulino
2012-03-12 19:59 ` [Qemu-devel] [PATCH 4/4] qapi: Convert migrate Luiz Capitulino
2012-03-15 14:20 ` [Qemu-devel] [PATCH v3 0/4] " Luiz Capitulino
  -- strict thread matches above, loose matches on Subject: below --
2012-03-16 19:26 [Qemu-devel] [PULL 0/4]: QMP queue Luiz Capitulino
2012-03-16 19:26 ` [Qemu-devel] [PATCH 1/4] QError: Introduce new errors for the migration command Luiz Capitulino
2012-03-09 18:13 [Qemu-devel] [PATCH v2 0/4] qapi: Convert migrate Luiz Capitulino
2012-03-09 18:13 ` [Qemu-devel] [PATCH 1/4] QError: Introduce new errors for the migration command Luiz Capitulino

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=1331582340-4611-2-git-send-email-lcapitulino@redhat.com \
    --to=lcapitulino@redhat.com \
    --cc=aliguori@us.ibm.com \
    --cc=eblake@redhat.com \
    --cc=jan.kiszka@siemens.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.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 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).