OPERATIONAL DEFECT DATABASE
...
...
Unable to power on or migrate VM that reserved memory on DRS clusterIn the vpxd.log file, you see entries similar to: <YYYY-MM-DD>T<time> info vpxd[000000001234] [Originator@1234 sub=vpxLro opID=<opID>] [VpxLRO] -- BEGIN task-internal-0001234 -- PowerOnMainStep -- vim.modularity.WorkflowStepHandler.executeStep -- 85a5dr87-1584-a85d-c857-a7c847595423(0458e858-8547-154d-f158-a4b585fd4751)<YYYY-MM-DD>T<time> error vpxd[000000001234] [Originator@1234 sub=VmProv opID=<opID>] [WorkflowImpl] Get exception while executing action vpx.vmprov.PowerOnVm: vim.fault.InsufficientMemoryResourcesFault --> --> [backtrace begin] product: VMware VirtualCenter, version: 6.0.0, build: build-<build number>, tag: vpxd--> backtrace[00] libvmacore.so[0x003C5FC4]: Vmacore::System::Stacktrace::CaptureWork(unsigned int) --> backtrace[01] libvmacore.so[0x001F0743]: Vmacore::System::SystemFactoryImpl::CreateQuickBacktrace(Vmacore::Ref<Vmacore::System::Backtrace>&) <YYYY-MM-DD>T<time> info vpxd[000000000123] [Originator@1234 sub=Default opID=<opID>] [VpxLRO] -- ERROR task-internal-0001234 -- -- VmprovWorkflow: vim.fault.InsufficientMemoryResourcesFault:--> Result:--> (vim.fault.InsufficientMemoryResourcesFault) {--> faultCause = (vmodl.MethodFault) null, --> faultMessage = (vmodl.LocalizableMessage) [--> (vmodl.LocalizableMessage) {--> key = "vob.sched.group.mem.invalid3", --> arg = (vmodl.KeyAnyValue) [...--> message = "Group vmm.7252779: Failed to apply memory configuration for VMM group vmm0:<VM Name>. (min: 2097152, max: -1, minLimit: -1, shares: -3, units: pages)"--> }, --> (vmodl.LocalizableMessage) {--> key = "msg.vmmonVMK.admitFailed", --> arg = (vmodl.KeyAnyValue) [--> (vmodl.KeyAnyValue) {--> key = "1", --> value = "msg.vmk.status.VMK_MEM_ADMIT_FAILED"--> }, --> (vmodl.KeyAnyValue) {--> key = "2", --> value = "VMware ESX"--> }--> ], --> message = "Could not power on virtual machine: Admission check failed for memory resource. See the VMware ESX Resource Management Guide for information on resource management settings."--> }, --> (vmodl.LocalizableMessage) {--> key = "msg.monitorLoop.createVMFailed.vmk", --> message = "Failed to power on VM.", --> }, --> (vmodl.LocalizableMessage) { --> key = "vpxd.vm.poweron.unexpectedfailure", --> arg = (vmodl.KeyAnyValue) [ --> (vmodl.KeyAnyValue) { --> key = "1", --> value = "<VM Name>" --> } --> ], --> message = "An unexpected error was received from the ESX host while powering on VM <VM Name>." --> } --> ], --> unreserved = -1, --> requested = -1 --> msg = "The available Memory resources in the parent resource pool are insufficient for the operation." --> } --> Args: --> <YYYY-MM-DD>T<time> error vpxd[000000000123] [Originator@1234 sub=PowerOnMainStepHandler opID=<opID>] [ExecuteStep] Failed to power on the VM. Got methodFault N3Vim5Fault32InsufficientMemoryResourcesFault9ExceptionE(vim.fault.InsufficientMemoryResourcesFault) In the hostd.log file, you see entries similar to: <YYYY-MM-DD>T<time> verbose hostd[00001234] [Originator@1234 sub=Vmsvc.vm:/vmfs/volumes/987b5869-e5a788df-a957-fd8511ab173d/<VM_Name>/<VM_Name>.vmx] Handling vmx message 136702730: Group vmm.7252779: Failed to apply memory configuration for VMM group vmm0:<VM_Name>. (min: 2097152, max: 18446744073709551615, minLimit: 18446744073709551615, shares: 4294967293, units: pages)--> Could not power on virtual machine: Admission check failed for memory resource.--> See the VMware ESX Resource Management Guide for information on resource management settings.--> Failed to power on VM.--> In the vmkernel.log file, you see entries similar to: <YYYY-MM-DD>T<time> cpu2:7252779)WARNING: MemSched: vm 7252780: 6090: invalid memory allocation for VMM group: Admission check failed for memory resource
DRS underestimates memory reservation on VM.
This issue is resolved in VMware ESXi 6.0 Patch Release ESXi600-201807001 available at, VMware Patch Downloads.
To workaround this issue, Disable memory reservation on Virtual Machine.Login to ESXi and power on Virtual Machine.
Click on a version to see all relevant bugs
VMware Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.
