From: Anthony Liguori <anthony@codemonkey.ws>
To: qemu-devel@nongnu.org
Cc: Charles Duffy <Charles_Duffy@messageone.com>
Subject: Re: [Qemu-devel] [PATCH] add file: migration support (r2)
Date: Thu, 13 Nov 2008 12:49:38 -0600 [thread overview]
Message-ID: <491C76C2.9060409@codemonkey.ws> (raw)
In-Reply-To: <200811131844.11491.paul@codesourcery.com>
Paul Brook wrote:
> On Thursday 13 November 2008, Charles Duffy wrote:
>
>> This patch adds support for migration to and from file: targets, moves
>> common helpers between exec: and file: use cases from migration-exec.c
>> to migration.c, and adds a qemu_fdopen() helper parallel to qemu_fopen().
>>
>> Compared to the previous version submitted, it removes some cruft which
>> was accidentally included, and documents the limitations of O_NONBLOCK
>> on Linux with local filesystem access.
>>
>
> I don't see any documentation.
>
> The documentation should make it clear that this is not intended as a
> substitute for savvm/loadvm. A "live" migration doesn't make sense if you're
> writing to an actual file (rather than a FIFO) as you'll end up with
> unecessarily large files.
>
Forget the large file, it's not "live" which makes it not useful
compared with savevm/loadvm. Using rate limiting as a crutch to avoid
this is wrong because it requires the user to know how much bandwidth
QEMU can use before blocking.
To do live migration to a file, you need to tie into something like
posix-aio. You could actually use a bdrv_raw and expand it like we do
for a qcow file although that's sort of an abuse of the block driver API.
Regards,
Anthony Liguori
> Paul
>
>
>
next prev parent reply other threads:[~2008-11-13 18:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-13 18:04 [Qemu-devel] [PATCH] add file: migration support (r2) Charles Duffy
2008-11-13 18:39 ` Jamie Lokier
2008-11-13 18:44 ` Paul Brook
2008-11-13 18:49 ` Anthony Liguori [this message]
2008-11-14 3:33 ` Jamie Lokier
2008-11-14 3:49 ` Paul Brook
2008-11-18 3:04 ` Jamie Lokier
2008-11-18 12:57 ` Paul Brook
2008-11-18 14:26 ` 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=491C76C2.9060409@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=Charles_Duffy@messageone.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 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.