From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: kvm-devel <kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: [ANNOUNCE] kvm-42 release
Date: Fri, 21 Sep 2007 07:37:58 +0200 [thread overview]
Message-ID: <46F358B6.5080505@qumranet.com> (raw)
Only one fix, but an important one. It fixes booting of newer Linux
versions, which experienced disk and keyboard problems without
-no-kvm-irqchip.
As usual, if you have an issue please try with -no-kvm-irqchip and report.
Changes since kvm-42:
- fix ioapic edge-triggered interrupt handling
Notes:
If you use the modules bundled with kvm-43, you can use any version
of Linux from 2.6.9 upwards.
If you use the modules bundled with Linux 2.6.20, you need to use
kvm-12.
If you use the modules bundled with 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.
For best performance, use Linux 2.6.23-rc2 or later as the host.
http://kvm.qumranet.com
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
next reply other threads:[~2007-09-21 5:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-21 5:37 Avi Kivity [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-09-20 19:09 [ANNOUNCE] kvm-42 release Avi Kivity
[not found] ` <46F2C559.7020709-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-09-20 19:48 ` Avi Kivity
2007-09-20 20:31 ` Luca
2007-09-20 20:39 ` Luca
[not found] ` <68676e00709201339w43841c8h40e9345628831e69-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-09-21 3:50 ` Avi Kivity
[not found] ` <46F33F9A.8050301-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-09-21 19:17 ` Luca
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=46F358B6.5080505@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