Hugh Brock wrote:
Maybe in the future we want to block or unblock them based on what's in the capabilities XML that comes out of libvirt? Be kind of a neat trick to work out that a fullvirt guest did in fact have a paravirt balloon driver involved, though...
Capabilities statically describes what the hypervisor is capable of. It doesn't say anything about what drivers, etc. happen to be loaded into the guest. For that I guess you'd want to use virDomainGetXMLDesc (?)
Rich. -- Emerging Technologies, Red Hat http://et.redhat.com/~rjones/ 64 Baker Street, London, W1U 7DF Mobile: +44 7866 314 421 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. 3798903 Directors: Michael Cunningham (USA), Charlie Peters (USA) and David Owens (Ireland)
Attachment:
smime.p7s
Description: S/MIME Cryptographic Signature
