I've been going over the interface to libvirt, trying out every call
locally and remotely with all possible combinations of parameters that I
can think of. Not surprisingly one or two problems have cropped up. So
here's a short series of patches to fix the problems I've found.
virConnectGetMaxVcpus has a second "type" parameter. In practice this
isn't used and can be passed as NULL. However that fails in the remote
case. The fix is simple enough -- attached.
Rich.
--
Emerging Technologies, Red Hat -
http://et.redhat.com/~rjones/
Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod
Street, Windsor, Berkshire, SL4 1TE, United Kingdom. Registered in
England and Wales under Company Registration No. 03798903