From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:33978) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TgtYG-0008Lc-CO for qemu-devel@nongnu.org; Fri, 07 Dec 2012 03:45:01 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TgtYF-0008Bp-34 for qemu-devel@nongnu.org; Fri, 07 Dec 2012 03:44:56 -0500 Received: from mx1.redhat.com ([209.132.183.28]:60757) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TgtYE-0008BX-SU for qemu-devel@nongnu.org; Fri, 07 Dec 2012 03:44:55 -0500 From: Markus Armbruster References: <877goysvtm.fsf@codemonkey.ws> <50C10F63.4080208@wiesinger.com> <87wqwu1ffk.fsf@blackfin.pond.sub.org> <50C1A4C7.1000903@wiesinger.com> Date: Fri, 07 Dec 2012 09:44:52 +0100 In-Reply-To: <50C1A4C7.1000903@wiesinger.com> (Gerhard Wiesinger's message of "Fri, 07 Dec 2012 09:11:51 +0100") Message-ID: <87d2ym1caj.fsf@blackfin.pond.sub.org> MIME-Version: 1.0 Content-Type: text/plain Subject: Re: [Qemu-devel] [ANNOUNCE] QEMU 1.3.0 release List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Gerhard Wiesinger Cc: qemu-devel@nongnu.org Gerhard Wiesinger writes: > On 07.12.2012 08:37, Markus Armbruster wrote: >> Gerhard Wiesinger 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.