From: Avi Kivity <avi@qumranet.com>
To: kvm-devel <kvm-devel@lists.sourceforge.net>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: [ANNOUNCE] kvm-15 release
Date: Sun, 25 Feb 2007 13:09:08 +0200 [thread overview]
Message-ID: <45E16E54.60503@qumranet.com> (raw)
The big news today is that live migration works with kvm (kvm-14 could
do live migration, but only with -no-kvm). See
http://kvm.qumranet.com/kvmwiki/Migration for instructions.
Changes from kvm-14:
- live migration with kvm (Uri Lublin)
- based on Anthony Liguori's qemu patches
- new userspace interface (work in progress)
- the usual random fixes
Note that if you use the modules from Linux 2.6.20, you need to use
kvm-12. You can use kvm-15 with Linux 2.6.20, provided you use the
external module included in kvm-15. API/ABI stability is planned for
Linux 2.6.21.
http://kvm.qumranet.com
--
error compiling committee.c: too many arguments to function
next reply other threads:[~2007-02-25 11:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-25 11:09 Avi Kivity [this message]
2007-02-26 9:50 ` [kvm-devel] [ANNOUNCE] kvm-15 release Gerd Hoffmann
2007-02-26 10:01 ` Dor Laor
2007-02-26 10:04 ` Avi Kivity
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=45E16E54.60503@qumranet.com \
--to=avi@qumranet.com \
--cc=kvm-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.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