On Fri, Mar 30, 2012 at 12:31:02PM -0400, Laine Stump wrote: > On 03/30/2012 12:20 PM, Daniel P. Berrange wrote: > > On Fri, Mar 30, 2012 at 12:13:13PM -0400, Laine Stump wrote: > >> With the current setup, you can install the "libvirt" package, and it > >> will just use/present whichever hypervisors happen to be installed on > >> the machine. With the new setup, if you have qemu-kvm and lxc installed > >> on the machine, then install "libvirt", you won't get the libvirt driver > >> for either of these - you'll need to explicitly install libvirt-qemu and > >> libvirt-lxc. This may cause surprises for people who already have > >> bootstraps that just install "qemu-kvm" and "libvirt". > > No, that's not the case. The behaviour of 'yum install libvirt' is > > identical before & after. You won't get the 'libvirt-daemon-kvm' > > package installed, but that's fine, because that's an empty > > virtual package. > > That will be the case with the current changes, but will it still be > true even after we switch to providing a separately compiled module for > each hypervisor driver? (that's actually the case I was thinking about, > not the current case) Oh right, yes. What will happen is that 'libvirt-daemon' will not pull in any drivers, but for back compat 'libvirt' will still pull in all driver modules. This is why the docs recommend people to dep on 'libvirt-daemon-qemu' instead of relying on 'libvirt-daemon' to pull in qemu. > BTW, you've probably already fixed it, but I just found that > packaging.html fails to validate (haven't investigated, since it's very > likely you already encountered it too) Yep, thanks for mentioning it. Daniel -- |: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :| -- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list