Not following the recommended option “Store files in the same directory as the virtual machine.” We can use a different Datastore to allocate all our Swapfiles, but we do not use that here, and someone did a wrong configuration of the host.
VMWARE ESXI 6.7 RESOURCE POOL SOFTWARE
That information we get in ESXi hosts – Configuration Tab – in the Software area – “Virtual Machines Swapfile Location.”Īs we can see in the image above, is saving the Swapfiles in a different location of the VM folder. So we need to check the ESXi host configuration regarding the Virtual Machine Swap files location. But by default swap files should stick together in the same VM folder/Datastore.
VMWARE ESXI 6.7 RESOURCE POOL FULL
In the image above we check all Datastores that are in this ESXi, and we can see that one local Datastore is full and there is no free space.
There is a similar VMware KB for this logs errors: KB1030719 So we need to identify the VMFS volume /vmfs/volumes/5253f39e-5cc0b637-0a9f-d89d67180e96/ but also wh y is full. So ESXi is not allowing the VM to start because of lack of space to save the swap files, but as we have seen in the previous image, there is more than enough space to allocate swap or any VM.
T12:39:06.137Z| vmx| I120: Module MonitorLoop power on failed. T12:39:06.134Z| vmx| I120: Could not power on virtual machine: No space left on device. T12:39:05.200Z| vmx| I120: Disk_GetDigestDiskCount: numDigestDisks = 0 T12:39:05.199Z| vmx| I120: CreateVM: Swap: generating normal swap file name. T12:39:05.199Z| vmx| I120: numaHost: 1 virtual nodes, 1 virtual sockets, 1 physical domains So the next step is to check VMkernel logs. If is not ESXi resources or VM reservations we check if the Datastore where the VM is allocated to have enough free space.Īgain, as we can see the Datastore have 1.4Tb Free space, so the issue is Datastore related(at least the one where VM is allocated).
Looking at the VM reservations to see if any reservations values can trigger this problem, but again no reservations are in the this particularly VM. So we need to troubleshoot the issue and check what is triggering this problem.įirst, we check the ESXi resources, and as we can see, there are more enough resources to run a VM. Was a strange error, since we know that this ESXi host has enough resources to run more VMs. When users click the start button, always have an error “Insufficient Resources.” We had an ESXi host with an issue when powering any VM.
0 kommentar(er)
