Bug 253354

Summary: Virt-Manager does not allow changing RAM allocation for KVM guest
Product: [Fedora] Fedora Reporter: Jonathan Steffan <jonathansteffan>
Component: libvirtAssignee: Daniel Veillard <veillard>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: low    
Version: 7   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-12-01 10:34:05 EST Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description Jonathan Steffan 2007-08-18 01:04:47 EDT
Description of problem:
Try adjusting a kvm guests RAM allocation.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Run virt-manager
2. Try adjusting RAM for an existing KVM guest.
Actual results:
[jon@damaestro ~]$ virt-manager 
libvir: error : this function is not supported by the hypervisor:
Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/details.py", line 448, in
  File "/usr/share/virt-manager/virtManager/domain.py", line 626, in set_max_memory
  File "/usr/lib64/python2.5/site-packages/libvirt.py", line 321, in setMaxMemory
    if ret == -1: raise libvirtError ('virDomainSetMaxMemory() failed', dom=self)
libvirt.libvirtError: virDomainSetMaxMemory() failed this function is not
supported by the hypervisor: virDomainSetMaxMemory

Expected results:
RAM allocation changes or is not offered as being able to change.

Additional info:
Comment 1 Daniel Berrange 2007-12-01 10:34:05 EST
This is not a bug in libvirt. This is a limitation of KVM virtualization - it
has no support for changing guest RAM allocation on the fly.