Thanks Daniel. /Jd --- On Fri, 3/20/09, Daniel P. Berrange <berrange@xxxxxxxxxx> wrote: > From: Daniel P. Berrange <berrange@xxxxxxxxxx> > Subject: Re: kvm binary names > To: "jd" <jdsw2002@xxxxxxxxx> > Cc: "KVM List" <kvm@xxxxxxxxxxxxxxx> > Date: Friday, March 20, 2009, 11:17 AM > > -----Inline Attachment Follows----- > > 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' > > Ultimately this mess will resolve itself as all of KVM gets > merged into > upstream QEMU and we no longer have a separate code fork. > So the regular > QEMU RPM's qemu-system-x86_64 emulator binary will have KVM > support > builtin by default > > Regards, > Daniel > -- > |: Red Hat, Engineering, > London -o- http://people.redhat.com/berrange/ :| > |: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org > :| > |: http://autobuild.org > -o- > http://search.cpan.org/~danberr/ :| > |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 > 23C1 B3DF F742 7D3B 9505 :| > -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
