From: Avi Kivity <avi@redhat.com>
To: Nils Cant <nils.cant@kangaroot.net>
Cc: kvm@vger.kernel.org, Juan Quintela <quintela@redhat.com>
Subject: Re: Is it possible to live migrate guest OS'es between different versions of kvm/qemu-kvm?
Date: Sun, 05 Sep 2010 11:39:43 +0300 [thread overview]
Message-ID: <4C83574F.6030906@redhat.com> (raw)
In-Reply-To: <4C80DD6D.5030709@kangaroot.net>
On 09/03/2010 02:35 PM, Nils Cant wrote:
First, don't trim the cc list. It's evil.
> Is this something we can depend on for future releases then?
>
> If we decide now to build a virtual hosting farm on 0.12, will we be
> able to use live migration in the future if we decide we want to
> upgrade to 0.13 or later?
I believe so. Juan, can you confirm?
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2010-09-05 8:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-26 14:07 Is it possible to live migrate guest OS'es between different versions of kvm/qemu-kvm? Nils Cant
2010-08-30 12:04 ` Nils Cant
2010-08-30 20:16 ` Brian Jackson
2010-08-31 12:24 ` Avi Kivity
2010-09-03 11:35 ` Nils Cant
2010-09-05 8:39 ` Avi Kivity [this message]
2010-09-07 7:23 ` Nils Cant
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=4C83574F.6030906@redhat.com \
--to=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=nils.cant@kangaroot.net \
--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).