From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:34642) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TjQ6U-0007Ji-Q1 for qemu-devel@nongnu.org; Fri, 14 Dec 2012 02:54:43 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TjQ6T-0005sW-H7 for qemu-devel@nongnu.org; Fri, 14 Dec 2012 02:54:42 -0500 Received: from mx4-phx2.redhat.com ([209.132.183.25]:56034) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TjQ6T-0005sS-8g for qemu-devel@nongnu.org; Fri, 14 Dec 2012 02:54:41 -0500 Date: Fri, 14 Dec 2012 02:54:40 -0500 (EST) From: Paolo Bonzini Message-ID: <1379550897.23864274.1355471680686.JavaMail.root@redhat.com> In-Reply-To: <20121213214153.GP3236@otherpad.lan.raisama.net> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH] define qemukvm-1.2 machine type List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Eduardo Habkost Cc: Anthony Liguori , Marcelo Tosatti , qemu-devel@nongnu.org, Cole Robinson > > > > I think distros that used to ship qemu-kvm should just change > > > > the default just like for the acpi_piix4.c change. > > > > > > Maybe we could provide a --with-qemu-kvm-compat configure flag to > > > them? I like this. > > I think that defeats the purpose of a single binary. > > > > I think it would be better for the distros to have a qemu-kvm > > script that was: > > > > /usr/libexec/qemu-kvm: > > > > #!/bin/sh > > > > qemu-system-x86_64 -enable-qemu-kvm-compat "$@" > > That would be even better. I proposed a configure flag because I > understood (maybe incorrectly) that Paolo proposed a build-time > default change. Yes, that's what I was thinking. The problem is that Fedora did ship a qemu-system-x86_64 binary that disabled the qemu-kvm options (including using TCG by default), but it still had a qemu-kvm-compatible migration format. Paolo