On Thu, 2009-10-08 at 16:49 +0100, Daniel P. Berrange wrote: > On Thu, Oct 08, 2009 at 11:44:38AM -0400, James Laska wrote: > > Greetings, > > > > Quick question about virt package dependencies. The Rawhide Acceptance > > Install Test (which does a virt install) [1] first installs the required > > packages by doing: > > > > # yum -y install qemu-kvm python-virtinst pax > > > > It seems that installing python-virtinst used to also pull libvirt into > > the transaction. However, this is no longer the case [2]. Should the > > deps chain when installing python-virtinst also install libvirt? Or is > > it expected that if you wish to run your own virt daemon, you should > > install libvirtd? > > In previous Fedora: > > python-virtinst -> libvirt-python > libvirt-python -> libvirt (and thus libvirtd) > > In F12 though we split libvirt > > python-virtinst -> libvirt-python > livirt-python -> libvirt-client > > > So, python-virtinst no longer causes the libvirtd daemon to be pulled in > > In the general case this is good, because we explicitly want to allow a > client only install of virtualization tools. > > If wanting to actually setup a virtualization host though, your yum > command line is no longer sufficient. > > You probably want to change to use > > yum -y groupinstall Virtualization > > Which I believe should pull in KVM, libvirt, virt-manager & virtinst Thanks for the explanation Daniel! That helps. -James
Attachment:
signature.asc
Description: This is a digitally signed message part