public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: kvm-devel <kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: [ANNOUNCE] kvm-18 release
Date: Sun, 25 Mar 2007 14:15:50 +0200	[thread overview]
Message-ID: <460667F6.20107@qumranet.com> (raw)

This is mostly to fix the 32-bit Linux guest breakage in kvm-17.

Changes from kvm-17:

- merged new userspace API
- revert the optimization which killed some 32-bit Linux guests
- reboot support on Intel hosts (AMD are already supported)
- better timekeeping under load (Uri Lublin)
- other minor fixes and cleanups

Note that if you use the modules from Linux 2.6.20, you need to use
kvm-12.  You can use kvm-18 with Linux 2.6.20, provided you use the
external module included in kvm-18.  API/ABI stability is planned for
Linux 2.6.22.

http://kvm.qumranet.com

-- 
error compiling committee.c: too many arguments to function


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

             reply	other threads:[~2007-03-25 12:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-25 12:15 Avi Kivity [this message]
     [not found] ` <460667F6.20107-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-03-25 20:39   ` [ANNOUNCE] kvm-18 release Michael Riepe
     [not found]     ` <4606DE0F.5010009-0QoEqw4nQxo@public.gmane.org>
2007-03-26  7:17       ` Avi Kivity
     [not found]         ` <4607738D.30001-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-03-26 14:50           ` Michael Riepe

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=460667F6.20107@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