On Fri, 2016-11-18 at 11:16 -0500, Dawid Zamirski wrote:
Hi Andrea,
Sure, in this case those patches simply enable support of VirtualBox
5.1.x series in libvirt (prior to that libvirt supported vbox 2.x.x
to
5.0.x)- and as such it does not affect any previous version that
libvirt supported. When upstream VirtualBox releases new version
bumping major/minor version tag it is usually coupled with new COM
IID
strings that are bundled in the SDK which essentially bumps the VBOX
API version as well. Adding those SDK headers to livirt, enables it
to
communicate with the updated VBOX COM interface and avoids
"unsupported
API version" error message when one does virsh -c vbox:///session
with
VirtualBox 5.1.x installed on the machine.
Regards,
Dawid
Another try after realizing it's for official NEWS entry :-)
"Added support for API compatibility with VitualBox 5.1.x"