Yandex Cloud
Search
Contact UsTry it for free
  • Customer Stories
  • Documentation
  • Blog
  • All Services
  • System Status
  • Marketplace
    • Featured
    • Infrastructure & Network
    • Data Platform
    • AI for business
    • Security
    • DevOps tools
    • Serverless
    • Monitoring & Resources
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Start testing with double trial credits
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Center for Technologies and Society
    • Yandex Cloud Partner program
    • Price calculator
    • Pricing plans
  • Customer Stories
  • Documentation
  • Blog
© 2026 Direct Cursus Technology L.L.C.
All solutions
    • All solutions for Compute Cloud
    • You are unable to add a committed volume of services (CVoS) for Compute Cloud
    • Resolving the `Permission denied` error when connecting to a VM created with Terraform
    • Nested virtualization is not supported
    • Fixing the "Not enough resources" error on launching a virtual machine
    • Recovering access to a VM with a lost SSH key
    • Resolving issues with creating disk snapshots
    • Boot disk size failed to increase
    • VM shuts down on the `Instance guest stop processing` operation
    • Resolving the `WARNING REMOTE HOST IDENTIFICATION HAS CHANGED` error
    • Fixing a non-replicated disk failure
    • Resolving connection issues with Kosmos VM
    • Resolving password reset issues for VMs based on a Kosmos image
    • Resolving the `The limit on maximum number of cores has exceeded` error
    • CUDA unavailable on GPU platform
    • Resolving issues with performance of disk and network input/output on a VM
    • Resolving the `FAILED_PRECONDITION Relocation to zone `ru-central1-a/b/c` is disabled` error
    • Options to migrate a VM image to Yandex Cloud
    • How to change a boot disk type for a VM
    • How to get details about RAM consumption for Compute Cloud VMs
    • How to create VMs with multiple network interfaces
    • How to reduce the VM disk size
    • How to export Compute Cloud VM disk images
    • How to move a VM across folders or clouds
    • How to set up GUI and graphical environment on VMs running Linux
    • How to use an ISO image for deploying VMs
    • How to view incoming or outgoing traffic logs for a VM
    • How to use WinSCP to connect to a Linux VM in Yandex Cloud with a key generated on VM creation
    • How to back up a VM with rollback support
    • How to connect over SSH as root with `-X` or key
    • How to monitor memory usage
    • How to change an internal IP address
    • How to read the `Connections quota utilization` chart
    • How to check the disk access speed for a VM
    • How to create a VM instance with password access
    • How to increase the number of network connections
    • How to secure RDP connections on Microsoft Windows®

In this article:

  • Issue description
  • Solution
  • If the issue persists
  1. Compute Cloud
  2. Fixing the "Not enough resources" error on launching a virtual machine

Fixing the Not enough resources error when starting a VM instance

Written by
Yandex Cloud
Updated at December 17, 2025
  • Issue description
  • Solution
  • If the issue persists

Issue descriptionIssue description

You get the Not enough resources error when creating or starting a VM instance.

SolutionSolution

The Not enough resources error when creating a VM instance means that the availability zone you selected lacks resources to create and start a VM. Resources are checked for availability when you try to start a preemptible VM instance.

Here are some possible solutions to this issue:

  • Change the availability zone for the VM instance and try to create or launch it again.
  • Change the configuration of VM instance computing resources: Decrease the number of allocated CPU cores, RAM, disk space, and the number of GPUs attached to the VM instance (if any).
  • Change the placement policy for the VM: If you set up a placement group for the VM, check its parameters. The issue may occur because of the limitations of the VM placement policy in the availability zone or the host from the host group. Try changing the group parameters by setting less stringent requirements for VM placement, and try creating or starting a VM instance again.

If you use preemptible VM instances, consider changing the type of your affected VMs from preemptible to regular using this guide.
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 their group.

If the issue persistsIf the issue persists

If the above actions did not help, create a support ticket. Provide the following information in your ticket:

  1. ID of the VM instance you cannot start.
  2. Issue description.

Was the article helpful?

Previous
Nested virtualization is not supported
Next
Recovering access to a VM with a lost SSH key
© 2026 Direct Cursus Technology L.L.C.