| Summary: | F11 virt-manager doesn't allow KVM memory ballooning | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Hollis Blanchard <hollis> |
| Component: | virt-manager | Assignee: | Cole Robinson <crobinso> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | low | ||
| Version: | 11 | CC: | berrange, crobinso, hbrock, markmc, virt-maint |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | 0.7.0-7.fc11 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2009-10-07 03:15:26 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | ||
| Bug Depends On: | |||
| Bug Blocks: | 480594 | ||
Okay, AFAIK this is fixed in Fedora 12 and the problem in Fedora 11 is some xen specific hack:
def is_memory_hotplug_capable(self):
...
# Running paravirt guests can change it, or any inactive guest
if self.vm.OSType() == "linux" \
or self.status() not in [libvirt.VIR_DOMAIN_RUNNING,\
libvirt.VIR_DOMAIN_PAUSED]:
return True
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. http://admin.fedoraproject.org/updates/virt-manager-0.7.0-7.fc11 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. |
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): libvirt-0.6.2-17.fc11.i586 virt-manager-0.7.0-5.fc11.i586 How reproducible: Always. 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. Actual results: Current allocation field is grayed out. Expected results: Current allocation field would allow user to change guest memory allocation (triggering balloon action in the guest). Additional info: