Red Hat Bugzilla – Bug 1439216
Unable to allocate 32GB of RAM to Windows 10x64
Last modified: 2018-05-15 13:43:01 EDT
Description of problem: It is not possible to allocate more than 20GB of RAM when is OS Type Windows 10x64 set. Error messages: Cannot edit VM. Maximum memory cannot exceed platform limit. Cannot run VM. Memory size exceeds supported limit for given cluster version. Version-Release number of selected component (if applicable): RHV 4.x How reproducible: 100% Steps to Reproduce: 1. Allocate more than 20GB of RAM to VM 2. Error message about the exceed limit appears engine.log 2017-04-05 09:51:42,579 WARN [org.ovirt.engine.core.bll.RunVmCommand] (default task-24) [27a49aa5] Validation of action 'RunVm' failed for user Reasons: VAR__ACTION__RUN,VAR__TYPE__VM,ACTION_TYPE_FAILED_MEMORY_EXCEEDS_SUPPORTED_LIMIT Actual results: Not possible for Windows 10x64 Expected results: Able to allocate > 20GB of RAM Additional info: This is possible if OS Type is set to Other or Windows[7,8,2012,2016]x64 Thank you
WARN: Bug status wasn't changed from MODIFIED to ON_QA due to the following reason: [FOUND CLONE FLAGS: ['rhevm-4.1.z', 'rhevm-4.2-ga'], ] For more info please contact: rhv-devops@redhat.com
Verify with: Software version:4.2.0-0.0.master.20171108151837.gita7de53e.el7.centos Steps: Create windows 10 64bit V and set memory to 32GB and run vm Results: VM is up No errors
Israel, what about 2008 32b?
(In reply to Yaniv Kaul from comment #8) > Israel, what about 2008 32b? windows 2008 32B is derived from other (going through windows 2003 --> XP --> other) os.other.resources.minimum.ram.value = 256 os.other.resources.maximum.ram.value = 65536 # Windows2003(3, OsType.Windows, false), os.windows_2003.derivedFrom.value = windows_xp # Windows2008(4, OsType.Windows, false), os.windows_2008.derivedFrom.value = windows_2003 So it looks like bug in configuration should be 32B according to: https://msdn.microsoft.com/en-us/library/windows/desktop/aa366778(v=vs.85).aspx
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. https://access.redhat.com/errata/RHEA-2018:1488