From: Michael Roth <mdroth@linux.vnet.ibm.com>
To: qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org
Subject: [Qemu-devel] [ANNOUNCE] QEMU 2.3.0 is now available
Date: Mon, 27 Apr 2015 10:41:33 -0500 [thread overview]
Message-ID: <20150427154133.27251.42618@loki> (raw)
On behalf of the QEMU Team, I'd like to announce the availability of
the QEMU 2.3.0 release. This release contains 1900+ commits from 184
authors.
http://wiki.qemu.org/download/qemu-2.3.0.tar.bz2
The full list of changes are available at:
http://wiki.qemu.org/ChangeLog/2.3
Highlights include:
* Support for 32-bit KVM guests on 64-bit ARM hosts
* Support for running KVM under valgrind
* New IvyBridge CPU model for x86 guests
* Xen: support for ioreq-server API
* New 5KEc and 5KEf MIPS64r2, and M14K and M14Kc MIPS32r2
microMIPS CPU models for MIPS guests
* Basic support for transactional memory extentions in PowerPC guests
* Improved VGA support for little-endian PPC/pSeries guests
* PCI bus support for s390x guests
* Support for automatic guest device unplug when passthrough devices
are unbound from VFIO host driver
* Improved UI performance/support for GTK+/VNC/SDL/Spice, and VNC
support for multiseat
* Performance improvements for virtio-blk emulation: asynchronous SCSI
request handling, and disk read merging.
* QEMU Guest Agent: now also supports file operations in Windows guests,
can be used to enable/disable memory blocks in linux guests in
support for memory hotplug.
* Migration can now include a JSON description of migration stream to aid
in identifying incompatibilities betweens guests/hosts.
* And lots more...
Thank you to everyone involved!
Sincerely,
Michael Roth
reply other threads:[~2015-04-27 15:42 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=20150427154133.27251.42618@loki \
--to=mdroth@linux.vnet.ibm.com \
--cc=peter.maydell@linaro.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).