From: Anthony Liguori <anthony@codemonkey.ws>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
Lucas Meneghel Rodrigues <lmr@redhat.com>,
qemu-devel@nongnu.org,
Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>,
Juan Quintela <quintela@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 3/4] qcow2: add a migration blocker
Date: Mon, 14 Nov 2011 10:25:07 -0600 [thread overview]
Message-ID: <4EC140E3.1070001@codemonkey.ws> (raw)
In-Reply-To: <CAJSP0QWHDJWSNhFB3_WLmoeSy27XhBH7ySmDdQhZ7rsmK5S1Og@mail.gmail.com>
On 11/14/2011 09:51 AM, Stefan Hajnoczi wrote:
> On Fri, Nov 11, 2011 at 8:29 PM, Anthony Liguori<aliguori@us.ibm.com> wrote:
>> +#define QERR_BLOCK_FORMAT_FEATURE_NOT_SUPPORTED \
>> + "{ 'class': 'BlockFormatFeatureNotSupported', 'data': { 'format': %s, 'name': %s, 'feature': %s } }"
>> +
>
> Isn't having a separate error going to make life harder for management
> tool writers? I would have expected one "migration not supported"
> error, regardless of whether the reason is ivshmem, qcow2, or anything
> else.
Errors shouldn't be tied to verbs. IOW, if you have a migrate command, you
don't want to have a MigrationFailed error because that's tied to a specific verb.
Instead, you want the errors to provide additional information about the verb
failed. In this case, the verb is failing because you're requesting to use a
feature that is not supported by this particular block format.
Regards,
Anthony Liguori
>
> Stefan
>
next prev parent reply other threads:[~2011-11-14 16:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-11 20:29 [Qemu-devel] [PATCH 1/4] migrate: add migration blockers Anthony Liguori
2011-11-11 20:29 ` [Qemu-devel] [PATCH 2/4] ivshmem: use migration blockers to prevent live migration in peer mode Anthony Liguori
2011-11-12 20:24 ` Aneesh Kumar K.V
2011-11-11 20:29 ` [Qemu-devel] [PATCH 3/4] qcow2: add a migration blocker Anthony Liguori
2011-11-14 15:51 ` Stefan Hajnoczi
2011-11-14 16:25 ` Anthony Liguori [this message]
2011-11-14 16:37 ` Kevin Wolf
2011-11-14 16:45 ` Stefan Hajnoczi
2011-11-14 16:49 ` Anthony Liguori
2011-11-14 16:57 ` Stefan Hajnoczi
2011-11-11 20:29 ` [Qemu-devel] [PATCH 4/4] qed: add " Anthony Liguori
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=4EC140E3.1070001@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=kwolf@redhat.com \
--cc=lmr@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=stefanha@gmail.com \
--cc=stefanha@linux.vnet.ibm.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.