Red Hat Bugzilla – Bug 217372
VM started with "maximum memory".
Last modified: 2010-10-22 03:07:32 EDT
+++ This bug was initially created as a clone of Bug #214346 +++
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 request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release. Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release. This request is not yet committed for
The new virt-manager-0.4.0-1.el5 build is pushed to dist-5E-qu-candidate which
should resolve this issue.
The new VM wizard will now honour the max mem & memory settings correctly. In
this example log see maxmem=700 and memory=500:
Thu, 14 Jun 2007 23:25:16 DEBUG Creating a VM dan
Max Memory: 700
# VCPUs: 1
Disk image: /var/lib/xen/images/dan.img
Non-sparse file: True
After starting install you can verify with virsh:
# virsh dominfo dan | grep memory
Max memory: 716800 kB
Used memory: 511744 kB
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.