From: Hailiang Zhang <zhang.zhanghailiang@huawei.com>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: peter.huangpeng@huawei.com, qemu-devel@nongnu.org,
amit.shah@redhat.com, dgilbert@redhat.com, quintela@redhat.com
Subject: Re: [Qemu-devel] [RFC PATCH 0/2] Migration: support working on file:url
Date: Fri, 22 Jul 2016 14:28:47 +0800 [thread overview]
Message-ID: <5791BD1F.6040506@huawei.com> (raw)
In-Reply-To: <20160721121914.GG13528@redhat.com>
On 2016/7/21 20:19, Daniel P. Berrange wrote:
> On Thu, Jul 21, 2016 at 01:05:58PM +0800, zhanghailiang wrote:
>> It is more simple to use file:url to migrate VM into file.
>> Besides, it will be used in memory snapshot.
>
> NB, you can already migrate into a file
>
> "exec:/bin/cat > /path/to/file"
>
> and likewise
>
> qemu -incoming "exec:/bin/cat /path/to/file"
>
> This avoids the problem with POSIX I/O on plain files not actually
> supporting O_NONBLOCK in any sensible manner, which your file:
> suggestion suffers from.
>
OK, got it, please ignore this series. Thanks.
> Regards,
> Daniel
>
prev parent reply other threads:[~2016-07-22 6:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-21 5:05 [Qemu-devel] [RFC PATCH 0/2] Migration: support working on file:url zhanghailiang
2016-07-21 5:05 ` [Qemu-devel] [RFC PATCH 1/2] migration: Allow the migrate command to work on file:urls zhanghailiang
2016-07-21 12:05 ` Dr. David Alan Gilbert
2016-07-21 12:13 ` Daniel P. Berrange
2016-07-21 5:06 ` [Qemu-devel] [RFC PATCH 2/2] migration: Allow -incoming to work on file: urls zhanghailiang
2016-07-21 12:07 ` Dr. David Alan Gilbert
2016-07-21 12:19 ` [Qemu-devel] [RFC PATCH 0/2] Migration: support working on file:url Daniel P. Berrange
2016-07-21 17:41 ` Dr. David Alan Gilbert
2016-07-22 8:04 ` Daniel P. Berrange
2016-07-22 6:28 ` Hailiang Zhang [this message]
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=5791BD1F.6040506@huawei.com \
--to=zhang.zhanghailiang@huawei.com \
--cc=amit.shah@redhat.com \
--cc=berrange@redhat.com \
--cc=dgilbert@redhat.com \
--cc=peter.huangpeng@huawei.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 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.