Unable to add memory to a VM when Latency Sensitivity is high from vCenter error: "A specified parameter was not correct: spec.memoryAllocation"
search cancel

Unable to add memory to a VM when Latency Sensitivity is high from vCenter error: "A specified parameter was not correct: spec.memoryAllocation"

book

Article ID: 301501

calendar_today

Updated On:

Products

VMware vCenter Server VMware vSphere ESXi

Issue/Introduction

Symptoms:

Trying to add memory to a powered OFF VM which has Latency Sensitivity set to high, you get an error error: "A specified parameter was not correct: spec.memoryAllocation"

 

In vpxd logs you will see entry similar to

 

2024-03-06T06:38:59.182Z error vpxd[61775] [Originator@6876 sub=vpxLro opID=ltcwhx1o-16179-auto-chg-h5:70006847-8c-01] [VpxLRO] Unexpected Exception: N5Vmomi5Fault15InvalidArgument9ExceptionE(Fault cause: vmodl.fault.InvalidArgument

--> )

--> [context]zKq7AVECAQAAAHNYHQEldnB4ZAAA2uc3bGlidm1hY29yZS5zbwAA64gsAHN7LQBB+DIB700abGlidm1vbWkuc28AAVMjDgLbBnF2cHhkAIK5o2ABgjioYAGC5ZgrAYIA/y8BghgQLQGCUmQsAYKjgiwBgsGILAGC+6tgAYI8rWABgmq8YAGCzelfAYKcQmABgqq1KgGCS7YqAQK4NPQCzTf0Akw49IMB9QUBbGlidmltLXR5cGVzLnNvAIIAqWEBgvurYAGCPK1gAYJqvGABgs3pXwGCmJNgAQCXWiMAP7AjAJhzNwSHfwBsaWJwdGhyZWFkLnNvLjAABe81D2xpYmMuc28uNgA=[/context]

2024-03-06T06:38:59.185Z info vpxd[61775] [Originator@6876 sub=vpxLro opID=ltcwhx1o-16179-auto-chg-h5:70006847-8c-01] [VpxLRO] -- FINISH lro-329035

2024-03-06T06:38:59.185Z info vpxd[61775] [Originator@6876 sub=Default opID=ltcwhx1o-16179-auto-chg-h5:70006847-8c-01] [VpxLRO] -- ERROR lro-329035 -- vm-10003 -- vim.VirtualMachine.reconfigure: vmodl.fault.InvalidArgument:

--> Result:

--> (vmodl.fault.InvalidArgument) {

--> faultCause = (vmodl.MethodFault) null,

--> faultMessage = (vmodl.LocalizableMessage) [

--> (vmodl.LocalizableMessage) {

--> key = "msg.hostd.configSpec.latencySensitivity.memory",

--> arg = <unset>,

--> message = "The latency-sensitive virtual machine must have the memory reservation set to the memory size."

--> }

--> ],

--> invalidProperty = "spec.memoryAllocation"

--> msg = "A specified parameter was not correct: spec.memoryAllocation"

--> }

--> Args:

-->

 

hostd log will have these entries

 

2024-03-06T06:39:03.868Z warning hostd[264143] [Originator@6876 sub=Vmsvc.vm:/vmfs/volumes/64eef960-ea64e6cc-a87c-005056014326/cm-test02/cm-test02.vmx opID=ltcwhx1o-16179-auto-chg-h5:70006847-8c-01-e2-dfd4 user=vpxuser:VSPHERE.LOCAL\Administrator] Insufficient memory reservation for latency-sensitive VM. Expected memory reservation: 4096 MB, actual: 2048 MB

2024-03-06T06:39:03.868Z info hostd[264143] [Originator@6876 sub=Vmsvc.vm:/vmfs/volumes/64eef960-ea64e6cc-a87c-005056014326/cm-test02/cm-test02.vmx opID=ltcwhx1o-16179-auto-chg-h5:70006847-8c-01-e2-dfd4 user=vpxuser:VSPHERE.LOCAL\Administrator] Reconfigure failed: N5Vmomi5Fault15InvalidArgument9ExceptionE(Fault cause: vmodl.fault.InvalidArgument

--> )

--> [context]zKq7AVICAgAAAAd9HAEUaG9zdGQAAOJCF2xpYnZtYWNvcmUuc28AAd/bDmxpYnZtb21pLnNvAAHCSB8CdtdRaG9zdGQAAguMUQJl3sIC2uLCAt4UxALrIcQCSyHAAqf6wAIrCMECGgzBA0KJ8WxpYnZpbS10eXBlcy5zbwACsH9SAJzFLQAkAS4A0g4/BDt9AGxpYnB0aHJlYWQuc28uMAAFvacObGliYy5zby42AA==[/context]

2024-03-06T06:39:03.871Z warning hostd[264143] [Originator@6876 sub=Vmsvc.vm:/vmfs/volumes/64eef960-ea64e6cc-a87c-005056014326/cm-test02/cm-test02.vmx opID=ltcwhx1o-16179-auto-chg-h5:70006847-8c-01-e2-dfd4 user=vpxuser:VSPHERE.LOCAL\Administrator] Exception thrown during reconfigure: (vim.vm.ConfigSpec) {

--> changeVersion = "2024-02-29T05:08:08.726145Z",

--> createDate = "2024-02-20T10:24:36.518999Z",

--> memoryMB = 4096,

--> memoryReservationLockedToMax = true,

--> }

--> N5Vmomi5Fault15InvalidArgument9ExceptionE(Fault cause: vmodl.fault.InvalidArgument

--> )

-->


Environment

VMware vCenter Server 7.0.x
VMware vSphere ESXi 7.0
VMware vCenter Server 6.7.x
VMware vSphere 6.7.x

Resolution

This is a known issue currently impacting vSphere 6.7 and 7.0.

Engineering team is working on a fix and will be available in a future release of vSphere 7.0


Workaround:

Set Latency Sensitivity set to Normal and then increase the memory.

Once done set the Latency Sensitivity set to high and power ON the VM


Additional Information

vSphere 6.5 and vSphere 8.0 are not impacted with this issue