Red Hat Bugzilla – Bug 214346
VM started with "maximum memory".
Last modified: 2007-11-30 17:11:48 EST
Description of problem:
VM alsways started with "maximum memory" instead of "start up memory", which
was defined by virt-manager GUI.
I set "400" for "start up memory" and "512" for "maximum memory" with virt-
But with checking on configuration file, "memory" was set as "512".
I though it should be "400".
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Launch virt-manager and connect to the local xen instance.
2. Click "New" button and create a VM.
3. Set the items were set as follows.
start up memory: 400
maximum memory : 512
domain name : rhel4u2_dom01
virtualization method : Fully virtualized
installation source : /var/rhel4u2/rhel4.0as_u2_x86_cd1.iso
disk type : file
disk image : /root/rhel4u2_dom01.img
disk size : 4000
vcpus : 1
4. After finish guest OS installation, boot the VM by running following
# xm create /etc/xen/rhel4u2_dom01
5. Check the memory size by running following command.
# xm list
"maximum memory" value is used as VM memory when booted.
"start up memory" value is used as VM memory when booted.
The configuration file, "rhel4u2_dom01", is attached with this report.
This is fixed in virt-manager-0.4.0 with libvirt-0.2.3. Note that until hvm
supports memory hotplug there is still no way to increase memory from start-up
to max -- but the guest starts with the amount of memory specified in
startup-memory, not the amount specified in max-mem.