Re: [libvirt] [PATCH] Refactor the libvirt RPM daemon pieces
On Fri, Mar 30, 2012 at 02:22:01PM +0100, Daniel P. Berrange wrote:
From: "Daniel P. Berrange" <berrange(a)redhat.com>
NB: this is in response to a Fedora 17 beta blocker bug.
Currently gnome-boxes depends on 'libvirt' which pulls
in the default virtual network, which kills networking
if you install Fedora 17 inside a KVM guest.
There are a number of flaws with our packaging of the libvirtd
daemon:
- Installing 'libvirt' does not install 'qemu-kvm' or 'xen'
etc which are required to actually run the hypervisor in
question
- Installing 'libvirt' pulls in the default configuration
files which may not be wanted & cause problems if installed
inside a guest
- It is not possible to explicitly required all the peices
required to manage a specific hypervisor
This change takes the 'libvirt' RPM and and changes it thus
- libvirt: just a virtual package with dep on libvirt-daemon and
libvirt-daemon-configs
- libvirt-daemon: the libvirt daemon and related pieces
- libvirt-daemon-configs: the default network & filter configs
It occurs to me that we perhaps ought to split the configs into
two pieces too.
The Xen and UML drivers only support the network driver, so they
don't need the network filter configs
The OpenStack NOVA project does not want the default NAT network,
but it does want the network filter configs.
So I'm thinking instead of libvirt-daemon-configs, create:
- libvirt-daemon-config-network
- libvirt-daemon-config-nwfilter
Regards,
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 :|