Red Hat Bugzilla – Bug 996816
Unable to create a windows 2012 ( 64bit ) VM with 32GB memory
Last modified: 2015-09-22 09:09 EDT
Description of problem:
When trying to create a windows 2012 VM ( 64 bit) with 32G of Virtual memory, the process fails with the error message "Maximum memory size is 20480 MB."
(Image file attached for reference )
Other supported 64 bit VMs can be created without any issues with >= 32G of Virtual memory.
( Have attached engine.log and vdsm.log if needed )
The VM being created is "EpicorAppServer"
what is the value of VM64BitMaxMemorySizeInMB in VdcOptions(engine-config)?
(In reply to Michal Skrivanek from comment #4)
> what is the value of VM64BitMaxMemorySizeInMB in VdcOptions(engine-config)?
The value is VM64BitMaxMemorySizeInMB | 2097152
Like I mentioned earlier, the Customer is able to create VMs with 32G memory for all other OSes.
I also see that windows 2012 is indeed supported ( https://bugzilla.redhat.com/show_bug.cgi?id=878674 ).. will change the summay accordingly.
I did not find anything relevant in the logs. Not sure if I missed anything.
Verified that the customer is using RHEV 3.2 ( rhevm-3.2.1-0.39.el6ev.noarch ) via the rpms installed through log-collector output.
For 3.3. this is addressed by osinfo changes (http://www.ovirt.org/OS_info)
This bug is currently attached to errata RHEA-2013:15231. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag.
Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information:
* Cause: What actions or circumstances cause this bug to present.
* Consequence: What happens when the bug presents.
* Fix: What was done to fix the bug.
* Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore')
Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug.
For further details on the Cause, Consequence, Fix, Result format please refer to:
Thanks in advance.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.