Not enough resources error
Creating a VM may fail with the Not enough resources error if the availability zone lacks sufficient hardware resources.
Solution
Here are some possible solutions to this issue:
Select a different availability zone
Select a different availability zone on the VM creation page under General information.
Specify a different availability zone in the --zone parameter of the command you will use to create your VM. You can get a list of availability zones for this parameter by running yc compute zone list.
If you already have stopped VMs that are failing to start due to the error, you can move them to a different availability zone.
Reduce the VM computing resources
Reduce the number of vCPUs, amount of RAM, disk space, and the number of GPUs connected to the VM.
Reduce resource allocation on the VM creation or update page under Computing resources.
Reduce resource allocation in the following parameters of the command you will use to create or update you VM:
--cores: Number of 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 configured a placement group for your VMs, the issue might be related to the limitations of the VM placement policy for the availability zone or a host in the host group. Try less restrictive 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 Preemptible. Retry creating the VM or restart the existing VM.
Set --preemptible=false when updating a stopped VM. If you are creating a new VM, skip the --preemptible parameter.
For more information, see Changing the VM type.
In scenarios with preemptible VMs, you can also use instance groups of one or multiple VM instances. To restart preemptible VMs, set up auto-recovery policies for the group.
If the issue persists
If the issue persists, create a support request.
In your request, specify the following information:
- ID of the VM instance you cannot start.
- Issue description.