VMWare throwing error

[PrashantBhatia]

Hello,

I had put my VMWare machine to suspend mode and then increased memeory of VMWare. Now, I am not able to run my machine as it is throwing below error:

Not enough physical memory is available to power on this virtual machine with its configured settings.

To fix this problem, adjust the additional memory settings to allow more virtual machine memory to be swapped.

If you were able to power on this virtual machine on this host computer in the past, try rebooting the host computer. Rebooting may allow you to use slightly more host memory to run virtual machines.

Also, I am not able to power off VMWare machine. Image is stuck.

If you have any knowledge about this. Let me know.

Regards,

Prashant

[kbhowmick123]

Hello Prashant,

Generally there are different scenario where the VM's goes offline and doesn't comes up even when we try to power on.

VM requires "hard space" that is memory equal to what is allocated to the memory of VM itself. If this space is not available, the VM will not start, or resume.

Refer the below link: VM doesn't start or resume because of lack of storage

Also I suggest you to power off your virtual machine(Assumed it's already in powered off state), try to decrease the memory to minimum of the reported virtual machine and increase the memory of other virtual machines (2256 MB) or adjust the additional memory settings to allow more virtual machine memory to be swapped.

If you're able to power on virtual machine in this host at past try rebooting the host, which release some amount of memory when comes up.

If above doesn't work share your infrastructure configuration details.

Regards

Koushik

[PrashantBhatia]

Hello Koushik,

I am not able to change memory setting of my image. It is disable and also, I am unable to power it off. I had increased the memory of my image from VM->Setting->HardWare option. And then it got stuck.

Thanks,

Prashant

[kbhowmick123]

Hi Prashant,

Is there any error it's throwing while you are re configuring the settings.

Can you brief me about your environment. if it's a cluster, try to vmotion the affected VM to another host and try to reconfigure the settings of the reported VM in the destination host..

Regards

Koushik