VM Instances Suspended – Possible Cause Related to Host Memory Overcommit?

[yyyyyyyyooooooo]

Hi everyone,

I'm experiencing an issue where VM instances are showing up in a suspended state on the following screens:

• Provisioning > Instances
• Infrastructure > Compute > Virtual Machines

I'm trying to understand the root cause of this behavior.

One possibility I'm considering is whether this could be related to memory overcommitment on the host. For example, in the Compute > Hosts screen, the Allocated Memory under Capacity Information is greater than the Maximum Memory of the host.

Could this memory over-allocation be causing the VMs to enter a suspended state?
Has anyone encountered a similar issue or know how to resolve it?

Also, I apologize if my English is not perfect — I'm translating this from Japanese.
I appreciate your understanding and any help you can offer!

Thank you very much.

[tsuneo]

こんにちは
HVMを私もいろいろ調べているのですが、CPU のオーバーコミットは実装されていると思いますが、メモリのオーバーコミットについては実装されていないのではないでしょうか？
そのため、仮想マシン作成時にホストに搭載されている以上のメモリは割り当ててはいけない認識でいます。

[PeterTzvetanov]

Hi Tsuneo,

some GuesOS systems goes by default in sleep mode and that will get the VM into the suspend mode. In some cases the "wake up" don't work and you might have to stop and start it. Better recommend to change the standby mode to disabled. Mostly Windows 10 and some linux distros/OVA compilations do this
behavior. The memory you can't overcommit in the VME, because it will not allow you create more VMs consumed memory then the capacity of the cluster.

With regards

Peter Tzvetanov

Support Engineer

Technical Support Phone Numbers