Description of problem:
The memory allocation field of virt-manager is disabled while a KVM guest is running.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Start KVM guest.
2. Run lspci in the guest to verify virtio-balloon device ("00:05.0 RAM memory: Qumranet, Inc. Virtio memory balloon") is present.
3. In virt-manager, click Details tab, then Memory.
Current allocation field is grayed out.
Current allocation field would allow user to change guest memory allocation (triggering balloon action in the guest).
Okay, AFAIK this is fixed in Fedora 12 and the problem in Fedora 11 is some xen specific hack:
# Running paravirt guests can change it, or any inactive guest
if self.vm.OSType() == "linux" \
or self.status() not in [libvirt.VIR_DOMAIN_RUNNING,\
Cole: feel free to close as fixed in rawhide if you don't think it'd be easy to fix in F11
virt-manager-0.7.0-7.fc11 has been submitted as an update for Fedora 11.
virt-manager-0.7.0-7.fc11 has been pushed to the Fedora 11 stable repository. If problems still persist, please make note of it in this bug report.