CentOS 5.6, x86_64 In Virt-Manager, when attempting to either change a guest's memory allocation or even just clicking "Apply" on the memory tab and not actually changing the values, the following error pops up: "Error changing memory values: this function is not supported by the connection driver: virDomainSetMaxMemory" When Googling around, I am finding reports of this error as early as two days ago, and as late as a year ago. Is there an option in KVM/Virt-Manager I am missing in order to resolve this problem, or is this bug really over a year old and not fixed in CentOS 5.6?
On Sat, Apr 9, 2011 at 11:54 AM, Russell Jones <rjones at eggycrew.com> wrote:> CentOS 5.6, x86_64 > > In Virt-Manager, when attempting to either change a guest's memory > allocation or even just clicking "Apply" on the memory tab and not > actually changing the values, the following error pops up: > > "Error changing memory values: this function is not supported by the > connection driver: virDomainSetMaxMemory" > > When Googling around, I am finding reports of this error as early as two > days ago, and as late as a year ago. Is there an option in > KVM/Virt-Manager I am missing in order to resolve this problem, or is > this bug really over a year old and not fixed in CentOS 5.6?I think it is this bug: https://bugzilla.redhat.com/show_bug.cgi?id=645285 But, "Red Hat does not plan to fix this issue". :-( Akemi
On Sat, 2011-04-09 at 13:54 -0500, Russell Jones wrote:> In Virt-Manager, when attempting to either change a guest's memory > allocation or even just clicking "Apply" on the memory tab and not > actually changing the values, the following error pops up: > > "Error changing memory values: this function is not supported by the > connection driver: virDomainSetMaxMemory" > > When Googling around, I am finding reports of this error as early as two > days ago, and as late as a year ago. Is there an option in > KVM/Virt-Manager I am missing in order to resolve this problem, or is > this bug really over a year old and not fixed in CentOS 5.6?I had this problem with a KVM recently. Instead of wasting time with virt-manager, I did this: # virsh shutdown [kvm] # virsh dumpxml [kvm] > guest.xml # vim guest.xml - I changed the memory parameters to be what I wanted, saved, and quit # virsh define guest.xml Done. Regards, Ranbir -- Kanwar Ranbir Sandhu Linux 2.6.32.26-175.fc12.x86_64 x86_64 GNU/Linux 21:41:35 up 4 days, 20:21, 2 users, load average: 0.08, 0.21, 0.16