From: Markus Armbruster <armbru@redhat.com>
To: Gerhard Wiesinger <lists@wiesinger.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [ANNOUNCE] QEMU 1.3.0 release
Date: Fri, 07 Dec 2012 09:44:52 +0100 [thread overview]
Message-ID: <87d2ym1caj.fsf@blackfin.pond.sub.org> (raw)
In-Reply-To: <50C1A4C7.1000903@wiesinger.com> (Gerhard Wiesinger's message of "Fri, 07 Dec 2012 09:11:51 +0100")
Gerhard Wiesinger <lists@wiesinger.com> writes:
> On 07.12.2012 08:37, Markus Armbruster wrote:
>> Gerhard Wiesinger <lists@wiesinger.com> writes:
>>
>>> On 03.12.2012 21:51, Anthony Liguori wrote:
>>>> Hi,
>>>>
>>>> Major features include:
>>>> - After nearly 6 years of work, all remaining differences between the
>>>> qemu-kvm.git and qemu.git have been merged into qemu.git
>>>>
>>> How is qemu-kvm enabled?
>>> --enable-kvm ?
>> Yes.
There's also --machine parameter accel. From --help:
property accel=accel1[:accel2[:...]] selects accelerator
supported accelerators are kvm, xen, tcg (default: tcg)
Example: --machine accel=kvm:tcg tries KVM, and if it's unavailable, it
falls back to TCG.
>>> Is there a runtime only command line switch also available?
>> I didn't get that.
>
> Is it possible to have only one binary built and switch between qemu
> and qemu-kvm by specifying a command line option?
> Another possibility might be when binary is name qemu-kvm KVM is
> enabled otherwise not-
>
> Therefore 2 different binary builds between qemu and qemu-kvm aren't
> necessary.
There's only one build. The resulting binary is intended to serve as
drop-in replacement for qemu-kvm. Please report any regressions.
next prev parent reply other threads:[~2012-12-07 8:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-03 20:51 [Qemu-devel] [ANNOUNCE] QEMU 1.3.0 release Anthony Liguori
2012-12-06 21:34 ` Gerhard Wiesinger
2012-12-07 7:37 ` Markus Armbruster
2012-12-07 8:11 ` Gerhard Wiesinger
2012-12-07 8:44 ` Markus Armbruster [this message]
2012-12-07 10:12 ` Paolo Bonzini
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=87d2ym1caj.fsf@blackfin.pond.sub.org \
--to=armbru@redhat.com \
--cc=lists@wiesinger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.