qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Blue Swirl <blauwirbel@gmail.com>,
	Stefan Hajnoczi <stefanha@gmail.com>,
	"Shribman, Aidan" <aidan.shribman@sap.com>,
	qemu-devel Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH v4] XBZRLE delta for live migration of large memory apps
Date: Wed, 10 Aug 2011 19:40:45 +0300	[thread overview]
Message-ID: <4E42B48D.9020609@redhat.com> (raw)
In-Reply-To: <4E42B07C.2090805@codemonkey.ws>

On 08/10/2011 07:23 PM, Anthony Liguori wrote:
>> Right now we have capabilties in the form of -help output.
>>
>> If -help says
>>
>> -no-xzbrle disable xzbrle support
>>
>> (or -migration-compression xzbrle=off, or something) that's sufficient
>> for management tools.
>
>
> This is static, not dynamic.  You may attempt to migrate to another 
> host that supports it and then migrate to a second host that doesn't 
> support it after the first migration fails.

This may be acceptable, wait until the entire migration cluster is 
xzbrle capable before enabling it.  If not, add a monitor command.

>
>>
>> We shouldn't block this feature just because some monitor facility is
>> not yet implemented.
>
> We shouldn't make *any* changes to the migration protocol before we 
> have a feature negotiation capability.  I only want to do a hard break 
> of the protocol once.

Didn't we agree that management tool mediated feature negotiation (that 
is, outside the migration protocol itself) is acceptable?

-- 
error compiling committee.c: too many arguments to function

  reply	other threads:[~2011-08-10 16:40 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-08  8:42 [Qemu-devel] [PATCH v4] XBZRLE delta for live migration of large memory apps Shribman, Aidan
2011-08-08 13:29 ` Anthony Liguori
2011-08-08 13:41   ` Alexander Graf
2011-08-08 13:46     ` Anthony Liguori
2011-08-08 13:49     ` Avi Kivity
2011-08-08 13:51   ` Avi Kivity
2011-08-08 14:15     ` Anthony Liguori
2011-08-08 14:23       ` Avi Kivity
2011-08-08 14:33         ` Anthony Liguori
2011-08-08 14:39           ` Avi Kivity
2011-08-08 15:08             ` Anthony Liguori
2011-08-08 14:04   ` [Qemu-devel] [libvirt] " Daniel P. Berrange
2011-08-08 14:42     ` Avi Kivity
2011-08-08 14:46 ` [Qemu-devel] " Avi Kivity
2011-08-08 14:47   ` Avi Kivity
2011-08-08 14:56     ` Stefan Hajnoczi
2011-08-08 15:01       ` Avi Kivity
2011-08-08 15:10     ` Anthony Liguori
2011-08-08 15:15       ` Avi Kivity
2011-08-08 16:19         ` Anthony Liguori
2011-08-08 16:53           ` Avi Kivity
2011-08-08 16:55             ` Anthony Liguori
2011-08-10 15:07               ` Shribman, Aidan
2011-08-10 15:12                 ` Avi Kivity
2011-08-10 15:58                   ` Anthony Liguori
2011-08-10 16:08                     ` Avi Kivity
2011-08-10 16:23                       ` Anthony Liguori
2011-08-10 16:40                         ` Avi Kivity [this message]
2011-08-10 19:27                           ` Anthony Liguori
2011-08-11  8:03                             ` Shribman, Aidan
2011-08-11 13:00                               ` Anthony Liguori
2011-08-11  8:17                             ` Avi Kivity
2011-08-11  9:16                               ` [Qemu-devel] [libvirt] " Daniel P. Berrange
2011-08-11  9:20                                 ` Avi Kivity
2011-08-11 13:03                               ` [Qemu-devel] " Anthony Liguori
2011-08-11  9:24                             ` [Qemu-devel] [libvirt] " Daniel P. Berrange

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=4E42B48D.9020609@redhat.com \
    --to=avi@redhat.com \
    --cc=aidan.shribman@sap.com \
    --cc=anthony@codemonkey.ws \
    --cc=blauwirbel@gmail.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.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).