From: Avi Kivity <avi@redhat.com>
To: KVM list <kvm@vger.kernel.org>
Subject: [ANNOUNCE] qemu-kvm-0.10.5
Date: Sun, 31 May 2009 11:10:47 +0300 [thread overview]
Message-ID: <4A223B87.4020705@redhat.com> (raw)
qemu-kvm-0.10.5 is now available. This is the second release of the
0.10 stable branch of qemu-kvm. qemu-kvm 0.10.5 includes all of the
features and fixes of qemu-0.10.5, plus adaptations for improved kvm
support.
Note that qemu-kvm releases do not include the kvm external modules
(kvm*.ko); you can use the modules provided by your distribution,
modules from the development releases (kvm-xx), or from the kvm-kmod
stable branch releases once they become available.
Changes from qemu-kvm-0.10.4
- merge qemu-0.10.5
- kvm: trim unsupported cpu features from cpuid
- kvm: provide a better error message for -smp > 1
- Remove initrd printfs
- Initial variables found by valgrind
- Fix -initrd with > 4GB guests
- Fix busy loop on live migration for certain platforms
- Remove GCC 3.x requirements from docs
- ETRAX: fixes for kernel command line, ethernet address, bmi
- CRIS: Fix bmi
- Fix bounce buffer errors
- Fix regression in -kernel
- fix large guest migration (Glauber Costa)
- fix -no-shutdown (Daniel Gollub)
- fix testsuite build (Jochen Roth)
- fix hard disk count reported by BIOS for extboot (Gleb Natapov)
- fix large page alignment (Marcelo Tosatti)
- fix tap not resetting correctly
- propagate errors on failed migration (Glauber Costa)
- fix unregistering large memory slots
- drop packet from tap device if all NICs are down (Mark McLoughlin)
- increment virtio-net savevm version (Anthony Liguori)
- fix build to separate object directoy (Anthony Liguori)
- fix virtio-net savevm dependency on build options (Alex Williamson)
- refuse migration if host does not support vnet header and guest needs
it (Alex Williamson)
http://www.linux-kvm.org
--
error compiling committee.c: too many arguments to function
reply other threads:[~2009-05-31 8:10 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4A223B87.4020705@redhat.com \
--to=avi@redhat.com \
--cc=kvm@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