qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@web.de>
To: kvm <kvm@vger.kernel.org>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] [ANNOUNCE] kvm-kmod-3.4
Date: Mon, 21 May 2012 20:03:09 -0300	[thread overview]
Message-ID: <4FBAC9AD.7040400@web.de> (raw)

[-- Attachment #1: Type: text/plain, Size: 1135 bytes --]

After the release of kernel 3.4, this is now the announcements of the
corresponding kvm-kmod-3.4. The package is available from

http://sourceforge.net/projects/kvm/files/kvm-kmod/3.4/kvm-kmod-3.4.tar.bz2/download

See [1] for further details on kvm-kmod.

Major KVM changes since kvm-kmod-3.3.6:
 - Timekeeping improvements
   (specifically: Don't mark TSC unstable due to S4 suspend)
 - Support for assigning host PCI devices that share interrupt lines
   (only usable with host kernels >= 3.3)
 - Fix privilege checks during task switches
 - SVM: Add support for AMD's OSVW feature in guests
 - x86: increase recommended max vcpus to 160
 - VMX: remove yield_on_hlt
 - various smaller fixes

kvm-kmod changes:
 - none

Note that I'm considering to stop distributing updated kernel headers
along with kvm-kmod with the next release. The only known users of this
feature, QEMU, stopped relying on it 2, soon 3, releases ago. I assume
people pulling in latest KVM modules via kvm-kmod will also regularly
update their QEMU version.

Jan

[1] http://www.linux-kvm.org/page/Getting_the_kvm_kernel_modules


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]

                 reply	other threads:[~2012-05-21 23:03 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=4FBAC9AD.7040400@web.de \
    --to=jan.kiszka@web.de \
    --cc=kvm@vger.kernel.org \
    --cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).