From: Avi Kivity <avi@redhat.com>
To: KVM list <kvm@vger.kernel.org>
Subject: [ANNOUNCE] kvm-83 release
Date: Tue, 13 Jan 2009 15:53:36 +0200 [thread overview]
Message-ID: <496C9CE0.2080103@redhat.com> (raw)
The biggest change this time around is support for the AMD IOMMU for
device assignment. As it requires extensive core kernel support, it is
only available on Linux 2.6.29rc1 or higher hosts.
Changes from kvm-82:
- amd iommu support (with Linux 2.6.29+ hosts) (Joerg Roedel)
- merge qemu-svn
- qcow2 correctness fixes
- '-drive serial=...' option
- virtio-net migration fixes
- fix '--with-patched-kernel' build on Ubuntu (Nolan Leake)
- improved tsc handling (Marcelo Tosatti)
- should reduce timing errors on older Linux guests
- remove cpuid code duplication due to upstream qemu work (Amit Shah)
- guest S3 sleep (Gleb Natapov)
- load assigned devices option rom (Kechao Liu)
- '-no-kvm-pit-reinjection' option to improve timing on RHEL 3 era guests
(Marcelo Tosatti)
- remove duplicate firmware config interface probe in bios (Sebastian
Herbszt)
- backward compatibility for marker_synchronize_register() (Eduardo Habkost)
- fix compile warning in tpr patching (Mark McLoughlin)
- don't install kvm headers to /usr/local
- fix smbios memory size in certain cases (Bill Rieske)
- simplify mmu shadow walking function
- stop using vmap() on guest pages (annoys ksm) (Izik Eidus)
- fix warning on MSR_VM_HSAVE_PA in dmesg
- fix i8254 timer count read (Marcelo Tosatti)
- ppc e500 core support (Hollis Blanchard)
- fix vmx real mode guest state validity checks
- make pop instruction emulation a little more generic
- implement 'ret far' instruction emulation
- properly lock i8354 timer
- remove ppc debug support (Hollis Blanchard)
- fix race freeing assigned device interrupt (Sheng Yang)
- fix pci interrupt in freeing in device assignment (Sheng Yang)
- allow disabling msi for assigned devices (Sheng Yang)
- emulate amd microcode level msr (Alexander Graf)
- helps esx boot on kvm
- make page unshadowing a little faster
- clear pending pit interrupts when unmasking the timer irq
- fixes xen-on-kvm
- mmu notifiers release method (Marcelo Tosatti)
- fixes large pages support
- expose ia64 registers to userspace (Jes Sorensen)
- fix type in has_svm() (Joe Perches)
- drop unnecessary memory clearing when allocating shadow page
(Marcelo Tosatti)
- rename "metaphysical" page attribute to "direct"
- fix irq routing with -no-kernel-irqchip
Notes:
If you use the modules bundled with kvm-83, you can use any version
of Linux from 2.6.16 upwards. You may also use kvm-83 userspace with
the kvm modules provided by Linux 2.6.25 or above. Some features may
only be available in newer releases.
http://kvm.qumranet.com
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
next reply other threads:[~2009-01-13 13:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-13 13:53 Avi Kivity [this message]
2009-01-13 15:54 ` [ANNOUNCE] kvm-83 release Farkas Levente
2009-01-15 14:00 ` Avi Kivity
2009-01-15 20:17 ` Farkas Levente
2009-01-13 16:15 ` John Wong
2009-01-13 17:27 ` Mark McLoughlin
2009-01-13 17:40 ` John Wong
2009-01-13 18:22 ` Amit Shah
2009-01-13 20:32 ` Michael Tokarev
2009-01-13 20:35 ` Michael Tokarev
2009-01-13 20:37 ` Anthony Liguori
2009-01-13 21:01 ` Michael Tokarev
2009-01-13 22:30 ` Mark McLoughlin
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=496C9CE0.2080103@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