qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Charles Duffy <Charles_Duffy@messageone.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [RFC] More robust migration
Date: Fri, 20 Feb 2009 11:06:31 -0600	[thread overview]
Message-ID: <gnmnun$pq9$1@ger.gmane.org> (raw)
In-Reply-To: <499EBFD8.50307@amd.com>

Andre Przywara wrote:
> 1. Transfer configuration data. Currently there is no VM configuration 
> data transferred with the stream. One has to start QEMU/KVM with the 
> _exact_ same parameters on the other side to allow migration. If there 
> would be a pseudo-device (transferred first) holding these parameters 
> (and other runtime dependent stuff like kvm_enabled()) this would ease 
> migration a lot.

I presently have code which *relies* on the ability to migrate from one 
VM to a target with different different backing stores for their disk 
images (albeit sharing the same contents).

If this ability were to be removed, that would be unfortunate.

  parent reply	other threads:[~2009-02-20 17:06 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-20 14:36 [Qemu-devel] [RFC] More robust migration Andre Przywara
2009-02-20 15:15 ` Anthony Liguori
2009-02-20 16:09   ` Paul Brook
2009-02-20 16:38     ` Jamie Lokier
2009-02-20 16:47       ` Paul Brook
2009-02-23  3:51         ` Jamie Lokier
2009-02-23 11:55           ` Paul Brook
2009-02-23 22:07             ` Jamie Lokier
2009-02-23 23:21               ` Paul Brook
2009-02-24  1:15               ` Anthony Liguori
2009-02-24 10:18               ` Avi Kivity
2009-02-20 16:37   ` Jamie Lokier
2009-02-20 18:27     ` Anthony Liguori
2009-02-20 17:06 ` Charles Duffy [this message]
2009-02-23  3:54   ` [Qemu-devel] " 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='gnmnun$pq9$1@ger.gmane.org' \
    --to=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 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).