All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jamie Lokier <jamie@shareable.org>
To: qemu-devel@nongnu.org
Cc: Charles Duffy <Charles_Duffy@messageone.com>
Subject: Re: [Qemu-devel] [PATCH] add file: migration support (r2)
Date: Fri, 14 Nov 2008 03:33:10 +0000	[thread overview]
Message-ID: <20081114033309.GK2055@shareable.org> (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.

That's true.  It would be better to use a slightly different format
when writing to a file, which lays out the RAM linearly and overwrites
re-dirtied pages during the migration.

I'm not sure if "live" migration to a file is really useful.  "Dead"
migration is useful for suspending a VM to disk.

-- Jamie

  parent reply	other threads:[~2008-11-14  3:33 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
2008-11-14  3:33   ` Jamie Lokier [this message]
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=20081114033309.GK2055@shareable.org \
    --to=jamie@shareable.org \
    --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.