From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bill Davidsen Subject: Re: kvm binary names Date: Mon, 30 Mar 2009 17:12:30 -0400 Message-ID: <49D135BE.7070302@tmr.com> References: <327276.24405.qm@web35804.mail.mud.yahoo.com> <20090320181715.GK2167@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: jd , KVM List To: "Daniel P. Berrange" Return-path: Received: from mail.tmr.com ([64.65.253.246]:60493 "EHLO partygirl.tmr.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758111AbZC3VMr (ORCPT ); Mon, 30 Mar 2009 17:12:47 -0400 In-Reply-To: <20090320181715.GK2167@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: Daniel P. Berrange wrote: > On Fri, Mar 20, 2009 at 10:57:50AM -0700, jd wrote: >> Hi >> What is the motivation for having different kvm binary names on various linux distributions.. ? >> >> -- kvm >> -- qemu-system-x86_84 >> -- qemu-kvm > > I can tell you the history from the Fedora POV at least... > > We already had 'qemu', 'qemu-system-x86_64', etc from the existing > plain qemu emulator RPMs we distributed. > > The KVM makefile creates a binary call qemu-system-x86_64 but this > clashes with the existing QEMU RPM, so we had to rename it somehow > to allow parallel installation of KVM and QEMU RPMs. > > KVM already ships with a python script called 'kvm' and we didn't > want to clash with that either, so we eventually settled on calling > it 'qemu-kvm'. Other distros didn't worry about clash with the python > script so called their binary just 'kvm' > Don't stop there, why does Fedora have both "qemu-ppc" and "qemu-system-ppc" and so forth? There are many of these, "arm" and "m68k" for instance. On x86 I assume that they are both emulated, and they are not two names for the same executable or such, so what are they and how to choose which to use? -- Bill Davidsen "We have more to fear from the bungling of the incompetent than from the machinations of the wicked." - from Slashdot