From: Pavel Hrdina <phrdina@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] savevm: Improve error message for unmigratable devices
Date: Thu, 18 Apr 2013 12:43:38 +0200 [thread overview]
Message-ID: <516FCE5A.20103@redhat.com> (raw)
In-Reply-To: <1366277029-17311-1-git-send-email-kwolf@redhat.com>
On 18.4.2013 11:23, Kevin Wolf wrote:
> Trying to take an internal snapshot when an unmigratable device is in
> use resuled in an 'Error -22 while writing VM' message. This patch
> changes it to print the same error message as migration would print:
> 'State blocked by non-migratable device xyz'
>
> Signed-off-by: Kevin Wolf <kwolf@redhat.com>
> ---
Hi Kevin,
this patch is not needed because I'm fixing the same in my patch series
http://lists.nongnu.org/archive/html/qemu-devel/2013-04/msg03287.html in
this patch
http://lists.nongnu.org/archive/html/qemu-devel/2013-04/msg03298.html .
Pavel
next prev parent reply other threads:[~2013-04-18 10:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-18 9:23 [Qemu-devel] [PATCH] savevm: Improve error message for unmigratable devices Kevin Wolf
2013-04-18 10:43 ` Pavel Hrdina [this message]
2013-04-18 11:33 ` Kevin Wolf
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=516FCE5A.20103@redhat.com \
--to=phrdina@redhat.com \
--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 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).