Re: [libvirt] [PATCH 00/10] Enable loadable modules for libvirtd

2012-04-03 Thread Daniel Veillard
On Mon, Apr 02, 2012 at 08:57:11PM +0100, Daniel P. Berrange wrote: For a long timer we've had the ability to build each libvirt driver as a loadable module. We have never used this by default and as a result it constantly bit-rots. This series fixes various bugs, and then enables it by

Re: [libvirt] [PATCH 00/10] Enable loadable modules for libvirtd

2012-04-03 Thread Daniel P. Berrange
On Tue, Apr 03, 2012 at 04:22:59PM +0800, Daniel Veillard wrote: On Mon, Apr 02, 2012 at 08:57:11PM +0100, Daniel P. Berrange wrote: For a long timer we've had the ability to build each libvirt driver as a loadable module. We have never used this by default and as a result it constantly

Re: [libvirt] [PATCH 00/10] Enable loadable modules for libvirtd

2012-04-03 Thread Daniel Veillard
On Tue, Apr 03, 2012 at 10:06:02AM +0100, Daniel P. Berrange wrote: On Tue, Apr 03, 2012 at 04:22:59PM +0800, Daniel Veillard wrote: On Mon, Apr 02, 2012 at 08:57:11PM +0100, Daniel P. Berrange wrote: For a long timer we've had the ability to build each libvirt driver as a loadable

Re: [libvirt] [PATCH 00/10] Enable loadable modules for libvirtd

2012-04-03 Thread Daniel P. Berrange
On Tue, Apr 03, 2012 at 05:41:57PM +0800, Daniel Veillard wrote: On Tue, Apr 03, 2012 at 10:06:02AM +0100, Daniel P. Berrange wrote: On Tue, Apr 03, 2012 at 04:22:59PM +0800, Daniel Veillard wrote: - libvirt-daemon - Just the libvirtd daemon, no drivers, no configs -

Re: [libvirt] [PATCH 00/10] Enable loadable modules for libvirtd

2012-04-03 Thread Daniel Veillard
On Tue, Apr 03, 2012 at 02:08:11PM +0100, Daniel P. Berrange wrote: On Tue, Apr 03, 2012 at 05:41:57PM +0800, Daniel Veillard wrote: On Tue, Apr 03, 2012 at 10:06:02AM +0100, Daniel P. Berrange wrote: On Tue, Apr 03, 2012 at 04:22:59PM +0800, Daniel Veillard wrote: - libvirt-daemon -

Re: [libvirt] [PATCH 00/10] Enable loadable modules for libvirtd

2012-04-03 Thread Daniel P. Berrange
On Tue, Apr 03, 2012 at 09:57:19PM +0800, Daniel Veillard wrote: On Tue, Apr 03, 2012 at 02:08:11PM +0100, Daniel P. Berrange wrote: So, 'yum install libvirt' would end up pulling in every single hypervisor we support (qemu, qemu-kvm, xen), which is not at all what we want. Separating

Re: [libvirt] [PATCH 00/10] Enable loadable modules for libvirtd

2012-04-03 Thread Daniel Veillard
On Tue, Apr 03, 2012 at 03:13:54PM +0100, Daniel P. Berrange wrote: On Tue, Apr 03, 2012 at 09:57:19PM +0800, Daniel Veillard wrote: On Tue, Apr 03, 2012 at 02:08:11PM +0100, Daniel P. Berrange wrote: So, 'yum install libvirt' would end up pulling in every single hypervisor we support

Re: [libvirt] [PATCH 00/10] Enable loadable modules for libvirtd

2012-04-03 Thread Daniel P. Berrange
On Tue, Apr 03, 2012 at 10:44:26PM +0800, Daniel Veillard wrote: On Tue, Apr 03, 2012 at 03:13:54PM +0100, Daniel P. Berrange wrote: On Tue, Apr 03, 2012 at 09:57:19PM +0800, Daniel Veillard wrote: On Tue, Apr 03, 2012 at 02:08:11PM +0100, Daniel P. Berrange wrote: So, 'yum install

Re: [libvirt] [PATCH 00/10] Enable loadable modules for libvirtd

2012-04-03 Thread Eric Blake
On 04/03/2012 08:46 AM, Daniel P. Berrange wrote: I think it is worth it, based on the fact that we get reasonably frequent bug reports that installing libvirt did not install qemu-kvm, or similar. In practice now we ask people to install 'qemu-kvm' directly With the change we ask people

[libvirt] [PATCH 00/10] Enable loadable modules for libvirtd

2012-04-02 Thread Daniel P. Berrange
For a long timer we've had the ability to build each libvirt driver as a loadable module. We have never used this by default and as a result it constantly bit-rots. This series fixes various bugs, and then enables it by default in configure. It also makes the PRMs use the loadable modules, adding

Re: [libvirt] [PATCH 00/10] Enable loadable modules for libvirtd

2012-04-02 Thread Eric Blake
On 04/02/2012 01:57 PM, Daniel P. Berrange wrote: For a long timer we've had the ability to build each libvirt driver as a loadable module. We have never used this by default and as a result it constantly bit-rots. This series fixes various bugs, and then enables it by default in configure.