Bug 524297 - F11 virt-manager doesn't allow KVM memory ballooning
Summary: F11 virt-manager doesn't allow KVM memory ballooning
Alias: None
Product: Fedora
Classification: Fedora
Component: virt-manager
Version: 11
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Cole Robinson
QA Contact: Fedora Extras Quality Assurance
Depends On:
Blocks: F11VirtTarget
TreeView+ depends on / blocked
Reported: 2009-09-18 18:42 UTC by Hollis Blanchard
Modified: 2009-10-07 03:15 UTC (History)
5 users (show)

Fixed In Version: 0.7.0-7.fc11
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2009-10-07 03:15:26 UTC
Type: ---

Attachments (Terms of Use)

Description Hollis Blanchard 2009-09-18 18:42:27 UTC
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):

How reproducible:

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:

Comment 1 Mark McLoughlin 2009-09-21 17:16:15 UTC
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,\
        return True

Cole: feel free to close as fixed in rawhide if you don't think it'd be easy to fix in F11

Comment 2 Fedora Update System 2009-10-05 19:27:08 UTC
virt-manager-0.7.0-7.fc11 has been submitted as an update for Fedora 11.

Comment 3 Fedora Update System 2009-10-07 03:15:17 UTC
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.

Note You need to log in before you can comment on or make changes to this bug.