On 03/11/2010 10:39 AM, Daniel Veillard wrote:
> On Wed, Mar 10, 2010 at 02:18:37PM -0500, Chris Lalancette wrote:
>> As previously discussed[1], this patch removes the
>> qemudDomainSetMaxMemory() function, since it doesn't
>> work. This means that instead of getting somewhat
>> cryptic errors, y
On Wed, Mar 10, 2010 at 02:18:37PM -0500, Chris Lalancette wrote:
> As previously discussed[1], this patch removes the
> qemudDomainSetMaxMemory() function, since it doesn't
> work. This means that instead of getting somewhat
> cryptic errors, you will now get:
>
> error: Unable to change MaxMemo
As previously discussed[1], this patch removes the
qemudDomainSetMaxMemory() function, since it doesn't
work. This means that instead of getting somewhat
cryptic errors, you will now get:
error: Unable to change MaxMemorySize
error: this function is not supported by the hypervisor: virDomainSetMa