From: Avi Kivity <avi@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] ANNOUNCE: Release 0.11.0-rc1 of QEMU
Date: Sun, 02 Aug 2009 19:33:21 +0300 [thread overview]
Message-ID: <4A75BFD1.8080101@redhat.com> (raw)
In-Reply-To: <4A71E935.3010005@codemonkey.ws>
On 07/30/2009 09:40 PM, Anthony Liguori wrote:
> The following fixes have been added since qemu-0.11.0-rc0:
>
> - add machine aliasing support (Mark McLoughlin)
> - add getfd/closefd monitor commands (Mark McLoughlin)
> - use correct headers for tap-win32 (Filip Navara)
> - fix live migration (Glauber Costa)
> - slirp: use monotonic clock if available (Ed Swierk)
> - clear msix_entries_nr on error (Michael Tsirkin)
> - HPET: fix reg writes (Beth Kon)
> - slirp: fix guestfwd for incoming data (Jan Kiszka)
> - fix build of qemu-thread.c on win32 (Sebastian Herbszt)
> - improve signrom.sh portability (Christoph Egger)
> - fix qemu-img convert to copy unallocated parts of the image
> (Akkarit Sangpetch)
> - vmdk: fix backing file handling (Kevin Wolf)
> - scsi: add save/restore support (Nolan Leake)
> - fix live migration for SCSI (Nolan Leake)
> - various sparc build fixes (Blue Swirl)
> - fix OpenBSD build (Blue Swirl)
> - only allow -cpu host when using KVM (Anthony Liguori)
> - fix build breakage when !KVM (Anthony Liguori)
>
Is there a (high-level) changelog of the changes from 0.10 series to 0.11?
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-08-02 16:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-30 18:40 [Qemu-devel] ANNOUNCE: Release 0.11.0-rc1 of QEMU Anthony Liguori
2009-08-02 16:33 ` Avi Kivity [this message]
2009-08-03 2:18 ` Anthony Liguori
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=4A75BFD1.8080101@redhat.com \
--to=avi@redhat.com \
--cc=anthony@codemonkey.ws \
--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).