From: Bill Davidsen <davidsen@tmr.com>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: jd <jdsw2002@yahoo.com>, KVM List <kvm@vger.kernel.org>
Subject: Re: kvm binary names
Date: Mon, 30 Mar 2009 17:12:30 -0400 [thread overview]
Message-ID: <49D135BE.7070302@tmr.com> (raw)
In-Reply-To: <20090320181715.GK2167@redhat.com>
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 <davidsen@tmr.com>
"We have more to fear from the bungling of the incompetent than from
the machinations of the wicked." - from Slashdot
next prev parent reply other threads:[~2009-03-30 21:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-20 17:57 kvm binary names jd
2009-03-20 18:17 ` Daniel P. Berrange
2009-03-30 21:12 ` Bill Davidsen [this message]
2009-03-30 21:26 ` Glauber Costa
2009-03-31 9:40 ` Daniel P. Berrange
-- strict thread matches above, loose matches on Subject: below --
2009-03-22 14:46 jd
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=49D135BE.7070302@tmr.com \
--to=davidsen@tmr.com \
--cc=berrange@redhat.com \
--cc=jdsw2002@yahoo.com \
--cc=kvm@vger.kernel.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.