From: Anthony Liguori <aliguori@us.ibm.com>
To: qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] [ANNOUNCE] QEMU 1.1-rc3 release
Date: Tue, 22 May 2012 09:32:36 -0500 [thread overview]
Message-ID: <4FBBA384.4010803@us.ibm.com> (raw)
Hi,
On behalf of the QEMU Team, I'd like to announce the availability of the third
release candidate for the QEMU 1.1 release. This release is meant for testing
purposes and should not be used in a production environment.
http://wiki.qemu.org/download/qemu-1.1.0-rc3.tar.bz2
You can help improve the quality of the QEMU 1.1 release by testing this release
and reporting bugs on Launchpad:
https://bugs.launchpad.net/qemu/
The release plan for the 1.1 release is available at:
http://wiki.qemu.org/Planning/1.1
And a detailed change log is available at:
http://wiki.qemu.org/ChangeLog/Next
Known Issues:
- There are no known release blockers in -rc3.
Changes since -rc2:
- xen: Fix PV-on-HVM (Anthony PERARD)
- qdev: Fix memory leak (dunrong huang)
- virtio: check virtio_load return code (Orit Wassermann)
- virtio-blk: always enable VIRTIO_BLK_F_SCSI (Paolo Bonzini)
- virtio-blk: define VirtIOBlkConf (Paolo Bonzini)
- virtio-blk: blockdev_mark_auto_del is transport-independent (Paolo Bonzini)
- virtio-blk: report non-zero status when failing SG_IO requests (Paolo Bonzini)
- use an uint64_t for the max_sz parameter in load_image_targphys (Mark Langsdorf)
- tests: Add rtc-test (fix test regression) (Stefan Weil)
- tests: Fix linker failure for fdc-test (Stefan Weil)
- mips: Fix BC1ANY[24]F instructions (Richard Sandiford)
- linux-user: Fix stale tbs after mmap (Alexander Graf)
- virtio-pci: add missing 'static' (Blue Swirl)
- sparc64: fix initrd loading (Blue Swirl)
- audio: split IN_T into two separate constants (Roger Pau Monne)
- target-microblaze: impelemented swapx instructions (Peter A. G. Crosthwaite)
- qemu-ga: align versioning with QEMU_VERSION (Michael Roth)
- qemu-ga: fix segv after failure to open log file (Michael Roth)
- qemu-ga: guest-shutdown: use only async-signal-safe functions (Luiz Capitulino)
- qemu-ga: guest-shutdown: become synchronous (Luiz Capitulino)
- qemu-ga: guest-suspend: make the API synchronous (Luiz Capitulino)
- qemu-ga: become_daemon(): reopen standard fds to /dev/null (Luiz Capitulino)
- qemu-ga: make reopen_fd_to_null() public (Luiz Capitulino)
- qemu-ga: guest-suspend-hybrid: don't emit a success response (Luiz Capitulino)
- qemu-ga: guest-suspend-ram: don't emit a success response (Luiz Capitulino)
- qemu-ga: guest-suspend-disk: don't emit a success response (Luiz Capitulino)
- qemu-ga: guest-shutdown: don't emit a success response (Luiz Capitulino)
- qemu-ga: don't warn on no command return (Luiz Capitulino)
- qapi: add support for command options (Luiz Capitulino)
Regards,
Anthony Liguori
next reply other threads:[~2012-05-22 14:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-22 14:32 Anthony Liguori [this message]
2012-05-22 15:09 ` [Qemu-devel] [ANNOUNCE] QEMU 1.1-rc3 release Jan Kiszka
2012-05-22 15:33 ` Gerd Hoffmann
2012-05-22 15:13 ` Avi Kivity
2012-05-22 15:54 ` Paolo Bonzini
2012-05-23 8:17 ` Stefan Hajnoczi
2012-05-23 8:22 ` Zhi Yong Wu
2012-05-23 8:32 ` Kevin Wolf
2012-05-23 8:43 ` Michael Tokarev
2012-05-23 11:55 ` Stefano Stabellini
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=4FBBA384.4010803@us.ibm.com \
--to=aliguori@us.ibm.com \
--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).