Skip to main content

Large Root Disk Flavors

Flavors that include a large root disk for the operating system.

Hyperstack offers a range of flavors tailored to different storage and performance needs. Most standard flavors include a small root disk for the operating system and a separate ephemeral disk for high-speed temporary storage during runtime.

Large Root Disk Flavors, by contrast, eliminate the ephemeral disk and reallocate that capacity to the root disk, providing a single, large, persistent storage device ideal for workloads that require durability over temporary I/O performance. These flavors are suffixed with -bigroot and they are only available via the List Flavors API.

API Only Flavors

Large Root Disk Flavors are available via API only, are not visible in the Hyperstack UI, and do not support hibernation or snapshotting. View available options using the List Flavors API and provision instances via the Create Virtual Machine API.

About Large Root Disk Flavors​

Large Root Disk Flavors are variants of standard Hyperstack VM configurations that eliminate the ephemeral disk and reallocate its capacity to the root disk. In typical flavors, the root disk is used for the operating system and core system files, while the ephemeral disk provides fast, temporary storage for active workloads. In Large Root Disk Flavors, this separation is removed, and a single, larger root disk is used to handle both system and workload storage.

Unlike ephemeral disks, which are deleted when a VM is stopped or hibernated, root disks are persistent for the life of the virtual machine. However, these flavors are not designed for long-term data durability or recovery: they do not support snapshotting or hibernation. As such, while the disk is larger and persistent across reboots, it is local-only and cannot be recovered or reused once the VM is deleted.

If your workload requires any of the features not supported by Large Root Disk Flavors, see the complete list of available flavors in the Flavors – GPU/CPU Configurations documentation.

Additionally, since hibernation is not supported, stopping the VM will not pause billing. To avoid further charges, the VM must be deleted when not in use.

This design simplifies storage management for short-lived, high-I/O workloads that don't require advanced lifecycle operations or external storage volumes.

Intended Use Cases​

Large Root Disk Flavors are optimized for:

  • Container-heavy workloads (e.g., Docker-based pipelines)
  • Inference jobs or temporary batch runs with large intermediate disk requirements
  • Storage-sensitive ML workloads without external persistent volumes
  • Cost-optimized environments where the VM can be deleted when not in use and snapshotting is not required

These configurations are especially suited for scenarios where maximizing root disk space and simplifying lifecycle management is a priority. Since these flavors do not support features like snapshotting or hibernation, they are a natural fit for jobs where data persistence and recovery workflows are not required.

Large Root Disk Flavor Characteristics​

Large Root Disk Flavors consolidate both the system and workload storage into a single root disk. This configuration eliminates the ephemeral disk typically used for high-speed, temporary runtime data and reallocates that capacity to the root disk. As a result, the root disk is significantly larger and persistent for the full life of the virtual machine, simplifying local storage for short-lived or containerized workloads.

These flavors are available via API only, and are suffixed with -bigroot. They cannot be used in workflows that depend on advanced disk features such as hibernation or snapshotting. However, they offer the benefit of greater persistent storage capacity relative to most standard flavors, which rely on ephemeral storage.

FeatureSupport StatusDescription
HibernationNot supportedVMs using these flavors cannot be suspended and resumed. To stop billing, the VM must be deleted.
SnapshottingNot supportedThe state of the VM disk cannot be captured or restored.
Ephemeral DiskNot supportedEphemeral disk is removed, with its capacity reallocated to the root disk.
Root Disk SizeIncreasedTotal equals the sum of root and ephemeral from the original base flavor.

To learn more about Hyperstack Flavor features, labels, and restrictions, click here.

Example Large Root Disk Flavor API Response​

Below is a sample response from the List Flavors API for the n3-RTX-A6000x8-bigroot flavor:

{
  "id": 200,
  "name": "n3-RTX-A6000x8-bigroot",
  "display_name": null,
  "region_name": "CANADA-1",
  "cpu": 252,
  "ram": 464.0,
  "disk": 1500,
  "ephemeral": 0,
  "gpu": "RTX-A6000",
  "gpu_count": 8,
  "stock_available": true,
  "created_at": "2025-12-23T13:51:50",
  "labels": [
    {
      "id": 19318,
      "label": "no-hibernation"
    },
    {
      "id": 19319,
      "label": "no-snapshot"
    },
    {
      "id": 21648,
      "label": "api-only"
    }
  ],
  "features": {
    "network_optimised": false,
    "no_reboot": false,
    "no_hibernation": true,
    "no_snapshot": true,
    "local_storage_only": false,
    "api_only": true
  }
}

This response represents a large root disk flavor (-bigroot) with a total root disk size of 1500 GB and no ephemeral disk (ephemeral: 0).

The labels array shows metadata attached to this flavor:

  • no-hibernation – hibernation is disabled
  • no-snapshot – snapshotting is not supported
  • api-only – flavor can only be used through the API

All large root disk flavors follow this structure, with zero ephemeral storage and clearly defined restrictions on snapshotting and hibernation.

Comparison with a Standard Flavor​

Large root disk flavors are based on existing standard flavors, but differ in how storage is allocated. Both versions offer identical compute resources (vCPU, RAM, and GPU), but the disk configuration changes significantly.

  • n3-RTX-A6000x8
    Includes a standard root disk for the operating system and a separate ephemeral disk for temporary runtime data. The ephemeral disk is high-speed but non-persistent and is deleted when the VM is stopped or hibernated.

  • n3-RTX-A6000x8-bigroot
    Eliminates the ephemeral disk and reallocates its capacity to the root disk. This results in a single, larger persistent root disk (1500 GB) that is retained for the life of the VM but does not support snapshotting or hibernation.

Deploying Virtual Machines with Large Root Disk Flavors​

To deploy a VM using a large root disk flavor:

  1. Choose a Large Root Disk Flavor
    Call the List Flavors API and identify a flavor with the -bigroot suffix in the name field.

  2. Deploy the Virtual Machine
    Use the selected flavor in a Create Virtual Machine API request to provision the VM.

Example request
curl -X POST "https://infrahub-api.nexgencloud.com/v1/core/virtual-machines" \
  -H "accept: application/json"\
  -H "api_key: YOUR API KEY"\
  -H "content-type: application/json" \
  -d '{
    "name": "example-vm",
    "environment_name": "example-env",
    "image_name": "Ubuntu Server 22.04 LTS R535 CUDA 12.2",
    "flavor_name": "n3-RTX-A6000x8-bigroot",
    "key_name": "example-key",
    "count": 1,
    "assign_floating_ip": true
  }'

This request provisions a VM using the n3-RTX-A6000x8-bigroot flavor, which includes a large, persistent root disk and no ephemeral storage. The VM will benefit from increased persistent local disk capacity (1500 GB root disk), will not include ephemeral storage (ephemeral: 0), and will not support snapshotting or hibernation. Because hibernation is not supported, you must delete the VM when not in use to avoid ongoing billing.

Large Root Disk Flavor VMs in Hyperstack UI

Although large root disk flavors must be provisioned using the API, virtual machines deployed with these flavors will still appear in the Hyperstack UI on the My Virtual Machines page and can be managed like any other VM, including deletion and monitoring.

Available Large Root Disk Flavors​

The following Large Root Disk (Big Root) GPU flavors are currently available via the Hyperstack API. View the latest details by using the List Flavors API.

L40 GPU Flavors​

Flavor NameGPU CountCPU CoresRAM (GB)Root Disk (GB)Ephemeral
Disk (GB)		Region
n3-L40x1-bigroot128588250CANADA‑1
n3-L40x2-bigroot26011616500CANADA‑1
n3-L40x4-bigroot412423233000CANADA‑1
n3-L40x8-bigroot825246466000CANADA‑1

L40 spot GPU Flavors​

Flavor NameGPU CountCPU CoresRAM (GB)Root Disk (GB)Ephemeral
Disk (GB)		Region
n3-L40x1-bigroot-spot128588250CANADA‑1
n3-L40x2-bigroot-spot26011616500CANADA‑1
n3-L40x4-bigroot-spot412423233000CANADA‑1
n3-L40x8-bigroot-spot825246466000CANADA‑1

RTX A6000 GPU Flavors​

Flavor NameGPU CountCPU CoresRAM (GB)Root Disk (GB)Ephemeral
Disk (GB)		Region
n3-RTX-A6000x2-bigroot2601163000CANADA‑1
n3-RTX-A6000x4-bigroot41242327500CANADA‑1
n3-RTX-A6000x8-bigroot825246415000CANADA‑1

RTX A6000 spot GPU Flavors​

Flavor NameGPU CountCPU CoresRAM (GB)Root Disk (GB)Ephemeral
Disk (GB)		Region
n3-RTX-A6000x2-bigroot-spot2601163000CANADA‑1
n3-RTX-A6000x4-bigroot-spot41242327500CANADA‑1
n3-RTX-A6000x8-bigroot-spot825246415000CANADA‑1

H100 GPU Flavors​

Flavor NameGPU CountCPU CoresRAM (GB)Root Disk (GB)Ephemeral
Disk (GB)		Region
n3-H100x1-bigroot1281808500CANADA‑1
n3-H100x2-bigroot26036016000CANADA‑1
n3-H100x4-bigroot412472033000CANADA‑1
n3-H100x8-bigroot8252144066000CANADA‑1
Flavor NameGPU CountCPU CoresRAM (GB)Root Disk (GB)Ephemeral
Disk (GB)		Region
n3-H100x8-NVLink-bigroot8252144066000CANADA‑1

H100 SXM5 GPU Flavors​

Flavor NameGPU CountCPU CoresRAM (GB)Root Disk (GB)Ephemeral
Disk (GB)		Region
n3-H100-SXM5x8-bigroot81921800321000CANADA‑1

Back to top

On this page