# failed to launch VM: insufficient resources to create new machine

**URL:** <https://community.fly.io/t/failed-to-launch-vm-insufficient-resources-to-create-new-machine/26674>\
**Category:** Questions / Help\
**Tags:** machines, volumes, gpu, login-only\
**Created:** [December 19, 2025, 10:49pm UTC](https://community.fly.io/t/failed-to-launch-vm-insufficient-resources-to-create-new-machine/26674 "2025-12-19T22:49:56Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![mayailurus](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/mayailurus/32/17593_2.png) [@mayailurus](https://community.fly.io/u/mayailurus)\
**Post date:** [December 19, 2025, 11:14pm UTC](https://community.fly.io/t/failed-to-launch-vm-insufficient-resources-to-create-new-machine/26674/3 "2025-12-19T23:14:13Z")

</div>

Hi… It would probably help to post the exact commands that you’ve been trying, since some ways of creating Machines will stubbornly cling to older volumes, etc.

Also, is it complaining about the same volume ID each time, and the like?

> [@jesus-agv](#):
>
> According to the CLI `fly platform regions` output, ams region has available capacity

This just shows its default Machine size (which is `performance-1x`, non-GPU), whereas GPU hosts are a completely disjoint subset, as I understand it.

You can try to use the [underlying Machines API](https://community.fly.io/t/regional-capacity-in-machines-api-and-flyctl/24843) to query instead for the desired GPU flavor, but that part of the infrastructure is suspect lately (unfortunately). For example, `iad` is currently showing _negative_ capacity (for the default `performance-1x`).

---

_[View the full topic](https://community.fly.io/t/failed-to-launch-vm-insufficient-resources-to-create-new-machine/26674)._