From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: kvm-devel <kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: [ANNOUNCE] kvm-32 release
Date: Mon, 23 Jul 2007 13:16:34 +0300 [thread overview]
Message-ID: <46A48002.6040508@qumranet.com> (raw)
kvm-32 contains an important silent data corruption fix, as well as a
number of minor fixes and updates.
Changes since kvm-31:
- fix oops with the slub allocator (CONFIG_SLUB)
- fix cmov instruction emulation, trashed by the mmio rmw fix
- fix rare, silent data corruption on writes that cross a page boundary
and touch a page table (Aurelien Jarno, me)
- fix race between vm creation and vcpu hotunplug (Rusty Russell)
- fix guest turning on pae with invalid pdptres (Rusty Russell)
- adapt external module to changed kmem_cache_create() api
- allow external module on 2.6.22 i386 nonpae
- fix regression in network throughput caused by guest smp changes
(Aurelien Jarno, me)
- live migration updates (Uri Lublin)
- minor cleanups (Nguyen Anh Quynh, me)
Notes:
If you use the modules from kvm-32, you can use any version of Linux
from 2.6.9 upwards.
If you use the modules from Linux 2.6.20, you need to use kvm-12.
If you use the modules from Linux 2.6.21, you need to use kvm-17.
Modules from Linux 2.6.22 and up will work with any kvm version from
kvm-22. Some features may only be available in newer releases.
http://kvm.qumranet.com
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
reply other threads:[~2007-07-23 10:16 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=46A48002.6040508@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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