Memory setting and reservation must be the same for VM to function with PCI passthrough to avoid the error and power on the VM.
I realized that I had overlooked a "down arrow" underneath the memory settings when I was editing the VM's Virtual Hardware. However, it did get me on the right track. Unfortunately the link provided in the answer below did not explain the steps required to increase scheduled memory to the VM in ESXi 6.5, since it was written before the new HTML5 interface and the procedure has changed. vmx fileĬhanging the latency sensitivity from low to high, and everything betweenĭoes anyone have any idea what I'm doing wrong? I don't think this was a problem before I upgraded to ESXi 6.5Įdit: Updated to ESXi 6.5a Build 4887370 - it did not fix the problem. Increasing or decreasing the VM memory allotment The error is:įailed - Invalid memory setting: memory reservation () should be equal to memsize(2048)
The VMs boot fine once the controller is removed. I wanted to move the CP controller to another VM, but no matter which VM I try to pass the controller through to, it won't boot after I pass it through. I have a VM with PCI passthrough of a cougar point SATA controller from the SM X9SCL-F-O motherboard. I have an ESXi 6.5 server without vSphere I've been running for a couple years.
0 kommentar(er)
