changing cpu/memory allocation in virt-manager does not work

[Jamie Strandboge]

If I attempt to change the cpu or memory allocation on an existing virtual machine, and press 'Apply', nothing happens. I checked the .xml file in /etc/libvirt/qemu and it is not updated. Using virsh dumpxml/define process works fine however.

This is on an amd64 dual-core up to date hardy host.

[Kevin (kevin-redhat-bugs)]

for some reason, neither virt-manager nor virsh will allow you to change the
number of cpus or memory allocated to kvm guests.

virt-manager:

You can pull up the details page, make changes and hit 'apply'. Nothing happens.
If you close the details window and re-open it all values are back to their old
settings.

virsh:

virsh # setvcpus fedora8-x86_64 4
libvir: error : this function is not supported by the hypervisor:
virDomainGetMaxVcpus

virsh # setmaxmem fedora8-x86_64 1024000
libvir: error : this function is not supported by the hypervisor:
virDomainSetMaxMemory
error: Unable to change MaxMemorySize

While kvm doesn't support changing these on a running guest, it should allow you
to do so on a inactive guest. (At least I think thats the case, it would be
lovely to change them on the fly too if possible).

Manually editing the guests xml file and restarting libvirt gets the new values
working fine.

[Scott Wegner (swegner)]

I've also noticed this. I'm able to change the settings in the input box, but the "Current allocation" stays the same. Moreover, if I close the window and come back, it has gone back to the previous value.

Also using AMD64 with updated Hardy beta.

[Ryan Bair (dr.bair)]

Bug is still present at final release. I think I've found more that doesn't work with virt-manager than does work.

[Kevin (kevin-redhat-bugs)]

Just retested this on F9.

setvcpus seems to behave the same.

setmaxmem seems to now accept the values, but it's not reflected in dumpxml or
the guest. :(

[Brian Pitts (bpitts)]

I wonder if this is related to Bug #235386

[Fastguy (erenoglu)]

I confirm this bug.

[Daniel (daniel123+launchpad)]

I can confirm this bug as well.

[Cole (cole-redhat-bugs)]

*** Bug 441653 has been marked as a duplicate of this bug. ***

[Cole (cole-redhat-bugs)]

*** Bug 444206 has been marked as a duplicate of this bug. ***

[Bug (bug-redhat-bugs)]

This message is a reminder that Fedora 8 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 8. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '8'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 8's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 8 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

The process we are following is described here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

[Kevin (kevin-redhat-bugs)]

Same retesting from comment #1, still happens in f10.

[Ilkka (ilkka-redhat-bugs)]

I'm the reporter of 441653, a duplicate for this one. Now that I made a reinstall (not upgrade) fc9 -> fc10, cpu setting works for me.

[Cole (cole-redhat-bugs)]

Sorry about the lack of communication on this issue, I did the original dupes and thought I updated the bug with status info, but I didn't :( Apologies.

Since libvirt 0.4.6, libvirt reports the correct max vcpu value for KVM. Since a while before that, the setvcpu and setmem/maxmem commands have been hooked up, so this bug is fully resolved. 0.5.0 is now in F9 and F10.

Kevin, in regards to Comment #1 and Comment #6, none of these commands will take effect on a running VM. That is a separate issue though: I don't think cpu hotplug is supported for kvm yet, though memory hotplug/ballooning is (I think), but we don't support it in libvirt. Please file a separate bug for those issues.

Closing as CURRENTRELEASE.

[Jamie Strandboge (jdstrand)]

This was fixed in 0.5.0 (see Fedora bug). Jaunty has libvirt 0.6.1-0ubuntu4 and virt-manager 0.6.1-1ubuntu4.