From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alexander Graf Subject: Re: [PATCH] Use qemu-kvm as installation name Date: Thu, 05 Feb 2009 17:05:18 +0100 Message-ID: <498B0E3E.20200@suse.de> References: <1232726884-14747-1-git-send-email-agraf@suse.de> <498B095F.9080502@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: kvm@vger.kernel.org, anthony@codemonkey.ws To: Avi Kivity Return-path: Received: from mx1.suse.de ([195.135.220.2]:43934 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753262AbZBEQFT (ORCPT ); Thu, 5 Feb 2009 11:05:19 -0500 In-Reply-To: <498B095F.9080502@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: Avi Kivity wrote: > Alexander Graf wrote: >> Most distributions use an executable name of qemu-kvm for kvm's >> qemu version. >> This is mostly because Qemu was there before and there usually is >> a package with a binary called qemu-system-x86_64 already. >> >> In order to not confuse people why distributions do things so >> differently from upstream, let's call the binary qemu-kvm in make >> install, so it's always qemu-kvm. >> >> Inspired by Anthony. >> > > While it does make sense, this will break a ton of existing scripts > (and my testsuite...). Also, upsteam qemu also does not rename qemu > even when kvm support is enabled. Wouldn't your scripts simply run qemu-system-x86_64 from the build directory? The patch only affects make install for exactly that reason. And at least from a distro perspective, symlinking qemu-kvm to qemu-system-x86_64 when things get stable in upstream qemu sounds fairly easy :-). Alex