On 04/05/2017 09:11 PM, Vasiliy Tolstov wrote:
2017-04-05 17:53 GMT+03:00 Andrea Bolognani <abologna@xxxxxxxxxx>:
That is true as long as you stick with the public API.
If you start messing with the internal RPC and a change
in libvirt breaks your code, you get to keep both pieces.
I think in case of internal rpc i need to monitor each libvirt release
and check git diff or src/remote/remote_protocol.x
Still, you will lack support for some drivers (e.g. ESX, Hyperv, XEN,
local test driver). Why do you want to hook on the RPC anyway?
Michal
--
libvir-list mailing list
libvir-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/libvir-list
