[libvirt] License issues
Matthias Bolte
matthias.bolte at googlemail.com
Wed May 1 16:24:00 UTC 2013
2013/5/1 Eric Blake <eblake at redhat.com>:
> Implementation wise, this would mean that we compile the vbox driver as
> an independent module (much the same as we do for qemu or lxc), and link
> that module into libvirtd rather than into libvirt.so directly. In
> libvirt.so, attempts to use a vbox:// URI would then be forwarded over
> RPC to libvirtd, instead of directly using vbox code. vbox would then
> be a remote instead of a local protocol. Since existing vbox://
> connections are local, vbox users have not previously had to ensure that
> the system libvirtd daemon is running. Therefore, I suspect that it
> would be nicer to reuse the qemu://session code that auto-spawns a
> session libvirtd, so that from the user standpoint, they can continue to
> connect to vbox without having to have a libvirtd system daemon running.
> The initial connection time will take slightly longer as a session
> libvirtd is autospawned, but that should not be too much impact.
This will break Virtual Box support on Windows, because libvirtd
doesn't work on Windows yet.
--
Matthias Bolte
http://photron.blogspot.com
More information about the libvir-list
mailing list