From: Peter Lieven <pl@kamp.de>
To: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Paolo Bonzini <pbonzini@redhat.com>,
quintela@redhat.com
Subject: [Qemu-devel] [RFC] Migration capability negotation
Date: Thu, 24 Oct 2013 20:39:07 +0200 [thread overview]
Message-ID: <5269694B.2030106@kamp.de> (raw)
Hi,
I was thinking that it would be great to have the source and destination during migration negoatiate
migration capabilities e.g. something like this:
User wants to use a feature e.g. 'zero_blocks'. He switches it to 'on' or maybe a new state 'auto' on the source VM.
If the migration is started the source hypervisor sends a set of all desired features. The destination hypervisor
answers with a subset of all features it supports and automatically enables them on its side. Depending on the returned
subset the source disables all features the destination does not support.
This would also allow us also to introduce new features which we would like to enable by default, but we cannot
because we do not know if the destination will support it.
Is there any way to add this without breaking backwards compability?
Comments welcome.
Peter
next reply other threads:[~2013-10-24 18:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-24 18:39 Peter Lieven [this message]
2013-10-24 21:32 ` [Qemu-devel] [RFC] Migration capability negotation Eric Blake
2013-10-24 23:37 ` Juan Quintela
2013-10-25 3:27 ` Peter Lieven
2013-10-25 5:42 ` Eric Blake
2013-10-25 5:55 ` Peter Lieven
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=5269694B.2030106@kamp.de \
--to=pl@kamp.de \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@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 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).