Check Capacity

Note

You need to have a Dedicated Hypervisor behind a Deployment target to proceed.

Getting Started

Before starting, please note the following aspects and restrictions:

Ensure that Exoscale Support has provisioned your dedicated resources and provided you with the relevant Deploy Target. Without this you will not be able to launch instances on your dedicated Hypervisor.
Exoscale CLI - Download the latest (≥ v1.45) binary for macOS, Linux, or Windows from GitHub.
API Key/Secret - Configure via the CLI with exo config.

Confirm Deployment Target

A Deployment Target is a virtual abstraction layer that allows you to provision Compute Instances onto dedicated hypervisors.

Run the following command with valid credentials for the target account, be sure to use the correct Zone:

exo api list-deploy-targets  --zone=ch-gva-2

Example output

exo api list-deploy-targets  --zone=ch-gva-2 
{
  "deploy-targets": [
  {
    "description": "dedicated resources group",
    "id": "c9a64f12-3ba7-4c19-bd93-61f2d84c3e55",
    "name": "Dedicated-ch-gva-coe",
    "type": "dedicated"
  }
]
}

Check the instances running on your Dedicated Hypervisor

Run the following command to check the following :

Dedicated Hosts (Hypervisors) that are running behind the deployment target.
Which instances (VM’s) are running on those hosts.

Note

This command requires the Deployment Target ID from the previous step (in our example below we use Deployment Target ID c9a64f12-3ba7-4c19-bd93-61f2d84c3e55)

exo api get-deploy-target c9a64f12-3ba7-4c19-bd93-61f2d84c3e55 --zone=ch-gva-2

Example output


exo api get-deploy-target c9a64f12-3ba7-4c19-bd93-61f2d84c3e55 --zone=ch-gva-2

{
  "allocation": [
    {
      "hypervisor": {
        "id": "b3c8f2a1-6d4e-419a-9e7b-c3f2b8a1d4e0",
        "name": "virt-hv416.gv2.p.exoscale.net"
      },
      "instances": [
        {
          "id": "7f9a1c3e-5b8d-426f-bd02-a4e7c1f8d3b6",
          "name": "pool-willdemo-b01a8-hnuqt"
        },
        {
          "id": "8be57fff-10b9-4a15-a20d-6493b517324d",
          "name": "pool-willdemo-b01a8-jcoog"
        }
      ]
    },
    {
      "hypervisor": {
        "id": "f8e7d6c5-b4a3-4210-9f8e-7d6c5b4a3f2e",
        "name": "virt-hv731.gv2.p.exoscale.net"
      },
      "instances": [
        {
          "id": "ad4c5e6f-7a8b-49c0-be1f-2a3b4c5d6e7f",
          "name": "pool-willdemo-b01a8-pryrh"
        },
        {
          "id": "6b7c8d9e-0f1a-42bc-ad3e-4f5a6b7c8d9e",
          "name": "test-instance-002"
        }
      ]
    }
  ],
  "description": "dedicated resources group",
  "id": "c9a64f12-3ba7-4c19-bd93-61f2d84c3e55",
  "name": "Dedicated-ch-gva-2",
  "type": "dedicated"
}

If you review the output, we can see that there are 4 instances running across both the Hypervisors virt-hv731.gv2.p.exoscale.net and virt-hv416.gv2.p.exoscale.net in the Geneva Zone.

You can estimate your capacity by correlating:

The placement information from get-deploy-target
The list of instances and their service offering specifications for CPU, RAM, Disk and potential accelerators
The Dedicated Hypervisors quantity, type and specifications contracted by your organization

Next Steps

Learn more about the Exoscale Dedicated Hypervisor architecture and concepts in the Overview. For advanced usage check the How-To section for other guides.

Last updated on July 21, 2026