"Not enough resources" error
If there are insufficient hardware resources in an availability zone, creating a VM may fail with the Not enough resources error.
Solution
The possible ways to solve this issue include:
Select a different availability zone
Select another availability zone on the VM creation page under General information.
Specify a different availability zone in the --zone parameter of the VM create command. You can get the list of availability zones for this parameter by running the yc compute zone list command.
If you already have stopped VMs that fail to start due to the error, you can move them to a different availability zone.
Reduce the amount of VM computing resources
Reduce the number of cores, the amount of RAM, disk space, and the number of GPUs connected to the VM.
Reduce the amount of employed resources on the VM creation or update page under Computing resources.
Reduce the amount of resources in the following parameters of the VM create or update command:
--cores: Number of cores (vCPUs)--memory: Amount of RAM--gpus: Number of GPUs
For more information, see Changing VM computing resources.
Change the VM placement policy
If you have a placement group set up for your VM, the issue might be related to the limitations of the VM placement policy in the availability zone or a host from the host group. Try softening your VM placement requirements.
Change the VM type from preemptible to non-preemptible
On the page for creating a new VM or updating a stopped one, disable the Preemptible option. Retry to create a new VM or restart an existing one.
Provide the --preemptible=false parameter when updating a stopped VM. If creating a new VM, do not specify the --preemptible parameter.
For more information, see Changing a VM's type.
In scenarios with preemptible VMs, you can also use instance groups of one or more VM instances. To restart preemptible VMs, set up auto-recovery policies for their groups.
If the issue persists
If the issue persists, create a request for technical support.
In the request, specify the following information:
- ID of the VM instance you cannot launch.
- Problem description.