All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: qemu-devel@nongnu.org
Cc: Uri Lublin <uril@redhat.com>
Subject: Re: [Qemu-devel] migration: adding migration to/from a file (v2)
Date: Thu, 19 Feb 2009 07:57:01 -0600	[thread overview]
Message-ID: <499D652D.60803@codemonkey.ws> (raw)
In-Reply-To: <499D4654.9000305@redhat.com>

Uri Lublin wrote:
>
> Migration to file, uses migration-to-fd (supports live migration).
> Migration from file, uses qemu-fopen directly.

Eh?  Haven't we already talked about why this doesn't work?  Maybe 
there's a v3 that you meant to send?

Regards,

Anthony Liguori

> pre-save:
>   (qemu) stop   # unless you really want live migration
>   (qemu) migrate_set_speed 3.5G # not needed, speed things up
>
> save:
>   (qemu) migrate [-d] file:/path/to/state-file
>
> load:
>   [shell] <qemu> <params> -incoming file:/path/to/state-file
>
>
> changes from v1:
>    - making sure write would not block (using select)
>    - pass max_throttle as is (can be set by user)
>    - not checking qemu_mallocz
>    - compile for non-windows as select is being used.
>

  reply	other threads:[~2009-02-19 13:57 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-19 11:45 [Qemu-devel] migration: adding migration to/from a file (v2) Uri Lublin
2009-02-19 13:57 ` Anthony Liguori [this message]
2009-02-19 16:14   ` Uri Lublin
2009-02-19 16:51     ` Anthony Liguori
2009-02-19 19:06       ` Uri Lublin
2009-02-19 20:05         ` Anthony Liguori
2009-02-19 20:28           ` Jamie Lokier
2009-02-19 23:36             ` M. Warner Losh
2009-02-19 23:59               ` Anthony Liguori
2009-02-20  0:36                 ` M. Warner Losh
2009-02-19 20:45           ` Uri Lublin
2009-02-19 19:37       ` Jamie Lokier
2009-02-19 20:06         ` Anthony Liguori
2009-02-19 19:33     ` Jamie Lokier

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=499D652D.60803@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=qemu-devel@nongnu.org \
    --cc=uril@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.