KR> I think this could be used in device_parsing.c:
KR> _change_device()
KR> change_memory()
KR> change_vcpus()
Yeah, agreed.
KR> Didn't we discuss using virGetLastError() /
KR> virConnGetLastError(conn) to determine whether we should return an
KR> error that indicates a failure versus a error that indicates the
KR> given action isn't supported by libvirt?
Well, it will certainly help a human client make that sort of
determination. However, I'm not sure it will be useful in practice
since you wouldn't expect the client to parse the error string.
--
Dan Smith
IBM Linux Technology Center
Open Hypervisor Team
email: danms(a)us.ibm.com