Dan Smith wrote:
This set adds a function to help us report more rich error messages,
where
appropriate. I've added in a couple that I think are critical, but would
like to hear suggestions for where else we need to include the libvirt
error in the CIM status.
Very useful addition. +1
I think this could be used in device_parsing.c:
_change_device()
change_memory()
change_vcpus()
Didn't we discuss using virGetLastError() / virConnGetLastError(conn) to
determine whether we should return an error that indicates a failure
versus a error that indicates the given action isn't supported by libvirt?
--
Kaitlin Rupert
IBM Linux Technology Center
kaitlin(a)linux.vnet.ibm.com