From: "Daniel P. Berrange" <berrange@redhat.com>
To: zhanghailiang <zhang.zhanghailiang@huawei.com>
Cc: qemu-devel@nongnu.org, amit.shah@redhat.com,
peter.huangpeng@huawei.com, dgilbert@redhat.com,
quintela@redhat.com
Subject: Re: [Qemu-devel] [RFC PATCH 0/2] Migration: support working on file:url
Date: Thu, 21 Jul 2016 13:19:14 +0100 [thread overview]
Message-ID: <20160721121914.GG13528@redhat.com> (raw)
In-Reply-To: <1469077560-20620-1-git-send-email-zhang.zhanghailiang@huawei.com>
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.
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 :|
next prev parent reply other threads:[~2016-07-21 12:19 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 ` Daniel P. Berrange [this message]
2016-07-21 17:41 ` [Qemu-devel] [RFC PATCH 0/2] Migration: support working on file:url Dr. David Alan Gilbert
2016-07-22 8:04 ` Daniel P. Berrange
2016-07-22 6:28 ` Hailiang Zhang
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=20160721121914.GG13528@redhat.com \
--to=berrange@redhat.com \
--cc=amit.shah@redhat.com \
--cc=dgilbert@redhat.com \
--cc=peter.huangpeng@huawei.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=zhang.zhanghailiang@huawei.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).