From: Randy Smith <perlstalker@vuser.org>
To: Avi Kivity <avi@redhat.com>
Cc: KVM list <kvm@vger.kernel.org>
Subject: Re: [ANNOUNCE] kvm-84 release
Date: Mon, 16 Feb 2009 08:27:55 -0700 [thread overview]
Message-ID: <499985FB.6080701@vuser.org> (raw)
In-Reply-To: <499765E3.70607@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 760 bytes --]
Avi Kivity wrote:
> A long list of changes due to an unusually late release. As is becoming
> usual, many of the changes come from upstream qemu; the kvm specific
> changes are mostly bugfixes, but also include infrastructure intended
> for message-signalled interrupts (MSI).
>
> kvm-84 is slower when rendering fonts on Windows than kvm-83; we are
> still investigating why.
>
> Changes from kvm-83:
> - merge qemu-svn
> - redirect slirp traffic to qemu-char device
> - slirp fixes
> - qcow2 fixes
Does this fix the qcow2 corruption issue reported on the list last week
on this list? (qcow2 corruption observed, fixed by reverting old change)
[snip]
--
Randy Smith
http://www.vuser.org/
http://perlstalker.blogspot.com/
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]
prev parent reply other threads:[~2009-02-16 15:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-15 0:46 [ANNOUNCE] kvm-84 release Avi Kivity
2009-02-16 15:27 ` Randy Smith [this message]
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=499985FB.6080701@vuser.org \
--to=perlstalker@vuser.org \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.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