On 05/15/2013 12:33 PM, Daniel P. Berrange wrote: > From: "Daniel P. Berrange" <berrange@xxxxxxxxxx> > > Change the build process & driver initialization so that the > VirtualBox driver is built into libvirtd, instead of libvirt.so > This change avoids the VirtualBox GPLv2-only license causing > compatibility problems with libvirt.so which is under the > GPLv2-or-later license. > > NB this change prevents use of the VirtualBox driver on the > Windows platform, until such time as libvirtd can be made > to work there. > > Signed-off-by: Daniel P. Berrange <berrange@xxxxxxxxxx> > --- [...] > diff --git a/docs/drvvbox.html.in b/docs/drvvbox.html.in > index d59da57..e2a213c 100644 > --- a/docs/drvvbox.html.in > +++ b/docs/drvvbox.html.in > @@ -31,6 +31,18 @@ vbox+tcp://user@xxxxxxxxxxx/session (remote access, SASl/Kerberos) > vbox+ssh://user@xxxxxxxxxxx/session (remote access, SSH tunnelled) > </pre> > > + <p> > + <strong>NOTE: as of libvirt 1.0.6, the VirtualBox driver will always > + run inside the libvirtd daemon, instead of being built-in to the > + libvirt.so library directly. This change was required due to the > + fact that VirtualBox code is GPLv2-only licensed, which is not > + compatible with the libvirt.so license of GPLv2-or-later. The s/GPL/LGPL/ ? Martin -- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list