From: Jan Kiszka <jan.kiszka@web.de>
To: Alexandre DERUMIER <aderumier@odiso.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] qemu 1.3 vs qemu-kvm 1.3 differences ?
Date: Wed, 21 Nov 2012 09:28:20 +0100 [thread overview]
Message-ID: <50AC90A4.2070509@web.de> (raw)
In-Reply-To: <3e1f852d-1aac-42d6-8ee8-cb5478c7c213@mailpro>
[-- Attachment #1: Type: text/plain, Size: 490 bytes --]
On 2012-11-20 15:37, Alexandre DERUMIER wrote:
> Hi List,
>
> I would like to known what are the remaining differences between qemu 1.3 and qemu-kvm 1.3 ?
There is and there will be no qemu-kvm 1.3. That fork has been retired
by the maintainers.
The only difference remaining is some lacking infrastructure of KVM
low-level unit tests. But that's nothing a user has to worry about.
>
> Can we already switch from qemu-kvm to qemu ?
Yes, to qemu 1.3-rc0 ATM.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 259 bytes --]
next prev parent reply other threads:[~2012-11-21 8:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6dc0aec2-6220-4c94-9f82-521387f01643@mailpro>
2012-11-20 14:37 ` [Qemu-devel] qemu 1.3 vs qemu-kvm 1.3 differences ? Alexandre DERUMIER
2012-11-21 8:02 ` Alexandre DERUMIER
2012-11-21 8:28 ` Jan Kiszka [this message]
2012-11-21 8:44 ` Alexandre DERUMIER
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=50AC90A4.2070509@web.de \
--to=jan.kiszka@web.de \
--cc=aderumier@odiso.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).