From: Jan Kiszka <jan.kiszka@siemens.com>
To: kvm <kvm@vger.kernel.org>
Subject: [ANNOUNCE] kvm-kmod-2.6.33
Date: Thu, 25 Feb 2010 11:17:55 +0100 [thread overview]
Message-ID: <4B864E53.2000402@siemens.com> (raw)
Now that 2.6.33 is out, time to release the corresponding kvm-kmod
package as well. Not much has happened since 2.6.33-rc6, though.
KVM changes since kvm-kmod-2.6.33-rc6:
- PIT: control word is write-only
(fixes side-effects of spurious reads)
- kvmclock: count total_sleep_time when updating guest clock
(requires >= 2.6.32.9 as host, falls back to unfixed version
otherwise)
kvm-kmod changes:
- warn about kvmclock issues across host suspend/resume
- detect host kernel extra version to make use of fixes in stable
series
See [1] for the delta to 2.6.32.
I also released kvm-kmod-2.6.32.9 with basically the same changes. That
may be the last release based on that kernel, but nothing is set in
stone yet (specifically as we already maintain kvm-kmod-2.6.32
internally for a customer).
Jan
[1] https://sourceforge.net/projects/kvm/files/kvm-kmod/2.6.33-rc6/changelog/view
next reply other threads:[~2010-02-25 10:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-25 10:17 Jan Kiszka [this message]
2010-02-26 15:11 ` [ANNOUNCE] kvm-kmod-2.6.33 Ingmar Schraub
2010-02-26 15:38 ` Jan Kiszka
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=4B864E53.2000402@siemens.com \
--to=jan.kiszka@siemens.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