This document explains how to create virtual machine (VM) instances in bulk that
use A4X machine types. To learn more about this accelerator-optimized machine
type, see [A4X](https://docs.cloud.google.com/ai-hypercomputer/docs/evaluate-clustered-gpus.md.txt#a4x-machine).

To learn about other ways to create VMs or clusters, see
[Deployment options overview](https://docs.cloud.google.com/ai-hypercomputer/docs/create/create-overview.md.txt).

## Limitations

When you create A4X VMs in bulk, the following limitations apply:

> [!CAUTION]
> **Caution:** The [Compute Engine Service Level Agreement (SLA)](https://cloud.google.com/compute/sla) doesn't apply to the A4X machine series.

- You don't receive [sustained
  use discounts](https://docs.cloud.google.com/compute/docs/sustained-use-discounts) or [flexible committed use](https://docs.cloud.google.com/compute/docs/instances/committed-use-discounts-overview.md.txt#spend_based) discounts for instances that use this machine type.
- You can only create instances in certain [regions and zones](https://docs.cloud.google.com/compute/docs/regions-zones/gpu-regions-zones.md.txt#view-using-table).
- You can't use Persistent Disk (regional or zonal). You can only use [Google Cloud Hyperdisk](https://docs.cloud.google.com/compute/docs/disks/hyperdisks.md.txt).
- This machine type is only available on the [NVIDIA Grace platform](https://docs.cloud.google.com/compute/docs/cpu-platforms.md.txt#arm_processors).
- Machine type changes aren't supported for A4X. To switch to or from this machine type, you must create a new instance.
- You can't run Windows operating systems on this machine type. For a list of supported Linux operating systems, review the [supported operating systems for GPU instances](https://docs.cloud.google.com/compute/docs/images/os-details.md.txt#gpu-support).
- For A4X instances, when you use `ethtool -S` to monitor GPU networking, the physical port counters that end in `_phy` don't update. This is expected behavior for instances that use the MRDMA Virtual Function (VF) architecture. For more information, see [MRDMA functions and network monitoring tools](https://docs.cloud.google.com/compute/docs/gpus/gpu-network-bandwidth.md.txt#mrdma-monitoring).
- A4X instances don't support the following:
  - [Sole-tenancy](https://docs.cloud.google.com/compute/docs/nodes/sole-tenant-nodes.md.txt)
  - [Spot VMs](https://docs.cloud.google.com/compute/docs/instances/spot.md.txt)
  - [Flex-start VMs](https://docs.cloud.google.com/compute/docs/instances/about-flex-start-vms.md.txt)
- You can't attach Hyperdisk ML disks created before February 4, 2026 to A4X machine types.

Also review the [restrictions for placement policies](https://docs.cloud.google.com/compute/docs/instances/placement-policies-overview.md.txt#restrictions).

## Before you begin

Before creating VMs in bulk, if you haven't already done so, complete the following
steps:

1. **Choose a consumption option** : your choice of consumption option determines how you get and use GPU resources. To learn more, see [Choose a consumption option](https://docs.cloud.google.com/ai-hypercomputer/docs/consumption-models.md.txt).
2. **Obtain capacity** : the process to obtain capacity differs for each consumption option. To learn about the process to obtain capacity for your chosen consumption option, see [Capacity overview](https://docs.cloud.google.com/ai-hypercomputer/docs/obtain-capacity.md.txt).

   > [!NOTE]
   > **Note:** When you request A4X Max or A4X capacity, you obtain it in the *all capacity mode*. This mode is the only supported reservation operational mode for A4X Max or A4X machine types. For more information about all capacity mode, see [Reservation operational mode](https://docs.cloud.google.com/ai-hypercomputer/docs/create/review-configurations.md.txt#reservation-operational-mode).

Select the tab for how you plan to use the samples on this page:

### Console


When you use the Google Cloud console to access Google Cloud services and
APIs, you don't need to set up authentication.

### gcloud

In the Google Cloud console, activate Cloud Shell.

[Activate Cloud Shell](https://console.cloud.google.com/?cloudshell=true)


At the bottom of the Google Cloud console, a
[Cloud Shell](https://docs.cloud.google.com/shell/docs/how-cloud-shell-works.md.txt)
session starts and displays a command-line prompt. Cloud Shell is a shell environment
with the Google Cloud CLI
already installed and with values already set for
your current project. It can take a few seconds for the session to initialize.

### REST


To use the REST API samples on this page in a local development environment, you use the
credentials you provide to the gcloud CLI.

1. [Install](https://docs.cloud.google.com/sdk/docs/install) the Google Cloud CLI.
2. If you're using an external identity provider (IdP), you must first [sign in to the gcloud CLI with your federated identity](https://docs.cloud.google.com/iam/docs/workforce-log-in-gcloud.md.txt).


For more information, see
[Authenticate for using REST](https://docs.cloud.google.com/docs/authentication/rest.md.txt)
in the Google Cloud authentication documentation.

### Required roles


To get the permissions that
you need to create VMs in bulk,

ask your administrator to grant you the
[Compute Instance Admin (v1)](https://docs.cloud.google.com/iam/docs/roles-permissions/compute.md.txt#compute.instanceAdmin.v1) (`roles/compute.instanceAdmin.v1`) IAM role on the project.


For more information about granting roles, see [Manage access to projects, folders, and organizations](https://docs.cloud.google.com/iam/docs/granting-changing-revoking-access.md.txt).


This predefined role contains

the permissions required to create VMs in bulk. To see the exact permissions that are
required, expand the **Required permissions** section:


#### Required permissions

The following permissions are required to create VMs in bulk:

- `compute.instances.create` on the project
- To use a custom image to create the VM: `compute.images.useReadOnly` on the image
- To use a snapshot to create the VM: `compute.snapshots.useReadOnly` on the snapshot
- To use an instance template to create the VM: `compute.instanceTemplates.useReadOnly` on the instance template
- To specify a subnet for your VM: `compute.subnetworks.use` on the project or on the chosen subnet
- To specify a static IP address for the VM: `compute.addresses.use` on the project
- To assign an external IP address to the VM when using a VPC network: `compute.subnetworks.useExternalIp` on the project or on the chosen subnet
- To assign a [legacy network](https://docs.cloud.google.com/vpc/docs/legacy.md.txt) to the VM: `compute.networks.use` on the project
- To assign an external IP address to the VM when using a legacy network: `compute.networks.useExternalIp` on the project
- To set VM instance metadata for the VM: `compute.instances.setMetadata` on the project
- To set tags for the VM: `compute.instances.setTags` on the VM
- To set labels for the VM: `compute.instances.setLabels` on the VM
- To set a service account for the VM to use: `compute.instances.setServiceAccount` on the VM
- To create a new disk for the VM: `compute.disks.create` on the project
- To attach an existing disk in read-only or read-write mode: `compute.disks.use` on the disk
- To attach an existing disk in read-only mode: `compute.disks.useReadOnly` on the disk


You might also be able to get
these permissions
with [custom roles](https://docs.cloud.google.com/iam/docs/creating-custom-roles.md.txt) or
other [predefined roles](https://docs.cloud.google.com/iam/docs/roles-overview.md.txt#predefined).

## A4X fundamentals

An A4X cluster is organized into a hierarchy of blocks and sub-blocks to
facilitate large-scale, non-blocking network performance. Understanding this topology is key when
reserving capacity and deploying workloads.

A4X instance
:   An A4X instance is a single A4X machine type that has 4 GPUs
    attached.

Sub-block
:   A sub-block is the fundamental unit of A4X
    capacity. For A4X, a sub-block consists of 18 A4X
    instances (72 GPUs); these instances form an NVLink domain and are connected
    using a [multi-node NVLink](https://docs.nvidia.com/multi-node-nvlink-systems/mnnvl-user-guide/overview.html)
    system. You create an A4X sub-block by applying a
    compact placement policy that specifies a `1x72` topology.

Block
:   An A4X block is composed of 25 sub-blocks (NVLink domains), totalling up to
    450 A4X instances (1,800 GPUs). The sub-blocks are rail-aligned for efficient
    scaling. Each sub-block requires a
    compact placement policy.
    Therefore, for a single A4X block, you can create 25
    compact placement policies.

The following table shows the supported topology options for A4X instances:

| Topology (`gpuTopology`) | Number of GPUs | Number of instances |
|---|---|---|
| `1x72` | 72 | 18 |

<br />

## Overview

Creating instances in bulk with the A4X machine type includes the following steps:

1. [Create VPC networks](https://docs.cloud.google.com/ai-hypercomputer/docs/create/create-vms-in-bulk-a4x.md.txt#setup-network)
2. [Create a compact placement policy](https://docs.cloud.google.com/ai-hypercomputer/docs/create/create-vms-in-bulk-a4x.md.txt#create-compact-placement-policy)
3. [Create instances in bulk](https://docs.cloud.google.com/ai-hypercomputer/docs/create/create-vms-in-bulk-a4x.md.txt#create-instances-in-bulk)
4. [Install GPU drivers](https://docs.cloud.google.com/ai-hypercomputer/docs/create/create-vms-in-bulk-a4x.md.txt#install-drivers)
5. Optional: [Enable NVIDIA Multi-Instance GPU mode](https://docs.cloud.google.com/ai-hypercomputer/docs/create/create-vms-in-bulk-a4x.md.txt#multi-instance-gpu-mode)

### Create VPC networks

> [!TIP]
> **Tip:** If you are setting up a quick test, you can skip this step and specify a single NIC `--network-interface=nic-type=GVNIC` instead.

To set up the network for A4X machine types, create
three VPC networks for the following network interfaces:

- 2 regular VPC networks for the [gVNIC](https://docs.cloud.google.com/compute/docs/networking/using-gvnic.md.txt) network interfaces (NICs). The NICs then use these VPC networks for host-to-host communication.
- 1 VPC network with the [RoCE network profile](https://docs.cloud.google.com/vpc/docs/rdma-network-profiles.md.txt) for the CX-7 NICs when creating multiple A4X subblocks. The RoCE VPC network for VM instances must have 4 subnets, one subnet for each CX-7 NIC. These NICs use RDMA over Converged Ethernet (RoCE), providing the high-bandwidth, low-latency communication that's essential for scaling out to multiple A4X subblocks.

**Important:** For a single A4X subblock, you don't need to create a VPC network with the RoCE network profile because within a single subblock, direct GPU-to-GPU communication is handled by the multi-node NVLink.

For more information about NIC arrangement, see
[Review network bandwidth and NIC arrangement](https://docs.cloud.google.com/compute/docs/gpus/gpu-network-bandwidth.md.txt#review-network-nic).

Create the networks either manually by following the instruction guides or
automatically by using the provided script.

### Instruction guides

To create the networks, you can use the following instructions:

- To create the regular VPC networks for the gVNIC network interfaces, see [Create and manage
  Virtual Private Cloud networks](https://docs.cloud.google.com/vpc/docs/create-modify-vpc-networks).
- To create the RoCE VPC network for VM instances (`roce`), see [Create a Virtual Private Cloud network for RDMA NICs](https://docs.cloud.google.com/vpc/docs/create-vpc-network-rdma.md.txt).

For these VPC networks, set the
[maximum transmission unit (MTU)](https://docs.cloud.google.com/vpc/docs/mtu.md.txt) to a larger value.
For A4X machine types, the recommended MTU is
`8896` bytes.
To review the recommended MTU settings for other GPU machine types, see
[MTU settings for GPU machine types](https://docs.cloud.google.com/compute/docs/gpus/gpu-network-bandwidth.md.txt#mtu-gpu).

### Script

To create the networks, follow these steps.

For these VPC networks, set the
[maximum transmission unit (MTU)](https://docs.cloud.google.com/vpc/docs/mtu.md.txt) to a larger value.
For A4X machine types, the recommended MTU is
`8896` bytes.
To review the recommended MTU settings for other GPU machine types, see
[MTU settings for GPU machine types](https://docs.cloud.google.com/compute/docs/gpus/gpu-network-bandwidth.md.txt#mtu-gpu).

1.
   Use the following script to create regular VPC networks
   for the

   gVNICs.

   ```bash
       #!/bin/bash

       # Create regular VPC networks and subnets for the gVNICs
       for N in $(seq 0 1); do
         gcloud compute networks create GVNIC_NAME_PREFIX-net-$N \
           --subnet-mode=custom \
           --mtu=8896

         gcloud compute networks subnets create GVNIC_NAME_PREFIX-sub-$N \
           --network=GVNIC_NAME_PREFIX-net-$N \
           --region=REGION \
           --range=192.168.$N.0/24

         gcloud compute firewall-rules create GVNIC_NAME_PREFIX-internal-$N \
           --network=GVNIC_NAME_PREFIX-net-$N \
           --action=ALLOW \
           --rules=tcp:0-65535,udp:0-65535,icmp \
           --source-ranges=192.168.0.0/16
       done

       # Create SSH firewall rules
       gcloud compute firewall-rules create GVNIC_NAME_PREFIX-ssh \
         --network=GVNIC_NAME_PREFIX-net-0 \
         --action=ALLOW \
         --rules=tcp:22 \
         --source-ranges=IP_RANGE

       # Assumes that an external IP is only created for vNIC 0
       gcloud compute firewall-rules create GVNIC_NAME_PREFIX-allow-ping-net-0 \
         --network=GVNIC_NAME_PREFIX-net-0 \
         --action=ALLOW \
         --rules=icmp \
         --source-ranges=IP_RANGE


         
   ```
2. If you require multiple A4X subblocks, use the following
   script to create the

   RoCE VPC network for VM instances (`roce`) and subnets for the four CX-7 NICs on each A4X
   instance.

   **Important:** If your deployment consists of only a single A4X subblock, you can skip this step.

   ```bash
       #!/bin/bash

       # List and make sure network profiles exist in the machine type's zone
       gcloud compute network-profiles list --filter "location.name=ZONE"

       # Create network for RDMA NICs
       gcloud compute networks create RDMA_NAME_PREFIX-mrdma \
         --network-profile=ZONE-vpc-roce \
         --subnet-mode custom \
         --mtu=8896

       # Create subnets
       for N in $(seq 0 3); do
         gcloud compute networks subnets create RDMA_NAME_PREFIX-mrdma-sub-$N \
           --network=RDMA_NAME_PREFIX-mrdma \
           --region=REGION \
           --range=192.168.$((N+2)).0/24 # offset to avoid overlap with gVNICs
       done


         
   ```
3. Replace the following:
   - `GVNIC_NAME_PREFIX`: the custom name prefix to use for the regular VPC networks and subnets for the gVNICs.
   - `RDMA_NAME_PREFIX`: the custom name prefix to use for the RoCE VPC network for VM instances (`roce`) and subnets for the CX-7 NICs.
   - `ZONE`: specify a zone in which the machine type that you want to use is available, such as `us-central1-a`. For information about regions, see [GPU availability by regions and zones](https://docs.cloud.google.com/compute/docs/regions-zones/gpu-regions-zones.md.txt#view-using-table).
   - `REGION`: the region where you want to create the subnets. This region must correspond to the zone specified. For example, if your zone is `us-central1-a`, then your region is `us-central1`.
   - `IP_RANGE`: the IP range to use for the [SSH firewall rules](https://docs.cloud.google.com/compute/docs/connect/ssh-best-practices/network-access.md.txt#use-firewall-policies).
4. Optional: To verify that the VPC network resources are created successfully, check the network settings in the Google Cloud console:
   1. In the Google Cloud console, go to the **VPC networks** page.

      [Go to VPC networks](https://console.cloud.google.com/networking/networks/list)
   2. Search the list for the networks that you created in the previous step.
   3. To view the subnets, firewall rules, and other network settings, click the name of the network.

### Create a compact placement policy

**Important:** To create multiple NVLink domains in a block, create
separate compact placement policy for each NVLink domain. If you reuse a compact placement policy,
Compute Engine attempts to place the instances in the same subblock, which is already in
use.
To create a compact placement policy, select one of the following options:

### gcloud

To create a compact placement policy, use the
[`gcloud compute resource-policies create group-placement` command](https://docs.cloud.google.com/sdk/gcloud/reference/compute/resource-policies/create/group-placement):

```
gcloud compute resource-policies create group-placement POLICY_NAME \
    --collocation=collocated \
    --gpu-topology=1x72 \
    --region=REGION
```

Replace the following:

- `POLICY_NAME`: the name of the compact placement policy.
- `REGION`: the region where you want to create the compact placement policy. Specify the region that contains the zone where you plan to create instances, and verify that the machine type that you want to use is available in that region. For information about regions, see [GPU availability by regions and zones](https://docs.cloud.google.com/compute/docs/regions-zones/gpu-regions-zones.md.txt#view-using-table).

### REST

To create a compact placement policy, make a `POST` request to the
[`resourcePolicies.insert` method](https://docs.cloud.google.com/compute/docs/reference/rest/v1/resourcePolicies.md.txt).

```
POST https://compute.googleapis.com/compute/v1/projects/PROJECT_ID/regions/REGION/resourcePolicies
  {
    "name": "POLICY_NAME",
    "groupPlacementPolicy": {
      "collocation": "COLLOCATED",
      "gpuTopology": "1x72"
    }
  }
```

Replace the following:

- `PROJECT_ID`: your project ID.
- `POLICY_NAME`: the name of the compact placement policy.
- `REGION`: the region where you want to create the compact placement policy. Specify the region that contains the zone where you plan to create instances, and verify that the machine type that you want to use is available in that region. For information about regions, see [GPU availability by regions and zones](https://docs.cloud.google.com/compute/docs/regions-zones/gpu-regions-zones.md.txt#view-using-table).

<br />

### Create A4X instances in bulk

To obtain a GPU topology of `1x72`, create
18 A4X instances. When you create the instances, apply the compact placement policy that specifies the `gpuTopology`
field. Applying the policy ensures that Compute Engine creates all 18 A4X
instances in one sub-block to use an NVLink domain.


If a sub-block lacks capacity for all 18 A4X instances, then the bulk creation fails
and doesn't create any instance.

If your workload can operate with less than 18 A4X instances, then you can set the
[`minCount` field](https://docs.cloud.google.com/compute/docs/reference/rest/v1/instances/bulkInsert.md.txt#body.request_body.FIELDS.min_count)
to the minimum number of instances required for your workload. If you want to use any available
capacity, then set the `minCount` field to `1`.


**Important:**

When you create
A4X instances in bulk with a `1x72`
topology, Compute Engine allocates an entire 18-instance sub-block
(NVLink domain) to the placement policy used in the creation. If you create
fewer than 18 instances, the unused instances in that sub-block remain idle and
are unavailable for other requests that use a different placement policy.
However, it's possible to provision these unused instances by using the same
policy. To maximize resource efficiency, we recommend that you create exactly
18 instances.


<br />

To create A4X instances in bulk, select one of the following options.
The following commands also set the access scope for your instances. To simplify permissions management, Google recommends that you set the access scope on an instance to `cloud-platform` access and then use IAM roles to define what services the instance can access. For more information, see [Scopes best practice](https://docs.cloud.google.com/compute/docs/access/service-accounts.md.txt#scopes_best_practice).

### gcloud


To create
A4X instances in
bulk, use the [`gcloud compute instances bulk create` command](https://docs.cloud.google.com/sdk/gcloud/reference/compute/instances/bulk/create.md.txt).
**Important:** The following example uses the networking setup for multiple sub-blocks. If
you're creating only a single A4X sub-block and you only created the
gVNIC network in the [Create VPC networks](https://docs.cloud.google.com/ai-hypercomputer/docs/create/create-vms-in-bulk-a4x.md.txt#setup-network) step, then remove the
four RDMA subnets
indicated by the `MRDMA` NIC type from the example.

A4X instances support the following
[types of reservations](https://docs.cloud.google.com/compute/docs/instances/choose-reservation-type.md.txt):

- Future reservations for capacity blocks
- Future reservations in calendar mode

To consume these types of reservations, an instance must use the
*reservation-bound provisioning model*. For example, use the following creation parameters.

```
gcloud compute instances bulk create \
    --name-pattern=NAME_PATTERN \
    --count=COUNT \
     --machine-type=a4x-highgpu-4g \
    --image-family=IMAGE_FAMILY \
    --image-project=IMAGE_PROJECT \
    --region=REGION \
    --boot-disk-type=hyperdisk-balanced \
    --boot-disk-size=DISK_SIZE \
    --scopes=cloud-platform \
    --network-interface=nic-type=GVNIC,network=GVNIC_NAME_PREFIX-net-0,subnet=GVNIC_NAME_PREFIX-sub-0 \
    --network-interface=nic-type=GVNIC,network=GVNIC_NAME_PREFIX-net-1,subnet=GVNIC_NAME_PREFIX-sub-1,no-address 
    --network-interface=nic-type=MRDMA,network=RDMA_NAME_PREFIX-mrdma,subnet=RDMA_NAME_PREFIX-mrdma-sub-0,no-address \
    --network-interface=nic-type=MRDMA,network=RDMA_NAME_PREFIX-mrdma,subnet=RDMA_NAME_PREFIX-mrdma-sub-1,no-address \
    --network-interface=nic-type=MRDMA,network=RDMA_NAME_PREFIX-mrdma,subnet=RDMA_NAME_PREFIX-mrdma-sub-2,no-address \
    --network-interface=nic-type=MRDMA,network=RDMA_NAME_PREFIX-mrdma,subnet=RDMA_NAME_PREFIX-mrdma-sub-3,no-address \
    --reservation-affinity=specific \
    --reservation=RESERVATION \
    --provisioning-model=RESERVATION_BOUND \
    --instance-termination-action=TERMINATION_ACTION \
    --maintenance-policy=TERMINATE \
    --restart-on-failure \
    --resource-policies=POLICY_NAME
```

Replace the following:

- `NAME_PATTERN`: the name pattern to use for the A4X instances. For example, using `instance-#` for the name pattern generates A4X instances with names such as `instance-1` and `instance-2`, up to the number of A4X instances specified by `--count`.
- `COUNT`: the number of A4X instances to create.
- `IMAGE_FAMILY`: the image family of the OS image that you want to use. For a list of all supported operating systems, see [Supported operating systems](https://docs.cloud.google.com/compute/docs/images/os-details.md.txt#gpu-support).

  > [!TIP]
  > **Tip:** We recommend using [accelerator OS images](https://docs.cloud.google.com/ai-hypercomputer/docs/images.md.txt#accelerator-os-images) for AI-optimized workloads. Unless you have unique GPU driver requirements, these images install all required GPU drivers automatically. For more information about GPU driver requirements, see [Install GPU drivers](https://docs.cloud.google.com/ai-hypercomputer/docs/create/create-vms-in-bulk-a4x.md.txt#install-drivers) in this document.

- `IMAGE_PROJECT`: the project ID of the OS image.
- `REGION`: specify a region in which the machine type that you want to use is available. You must use the same region as the compact placement policy. For information about regions, see [GPU availability by regions and zones](https://docs.cloud.google.com/compute/docs/regions-zones/gpu-regions-zones.md.txt#view-using-table).
- `DISK_SIZE`: the size of the boot disk in GB. For more information, see either [Google Cloud Hyperdisk size limits](https://docs.cloud.google.com/compute/docs/disks/hyperdisks.md.txt#size-limits) or [Persistent Disk size limits](https://docs.cloud.google.com/compute/docs/disks/resize-persistent-disk.md.txt#size_limits) based on the type of disk.
- `GVNIC_NAME_PREFIX`: the name prefix that you specified when creating the standard VPC networks and subnets that use gVNIC NICs.
- `RDMA_NAME_PREFIX`: the name prefix that you specified when creating the VPC networks and subnets that use RDMA NICs.
- `RESERVATION`: the reservation name, a block, or a subblock within a reservation. To get the reservation name or the available blocks, see [View reserved capacity](https://docs.cloud.google.com/ai-hypercomputer/docs/view-reserved-capacity.md.txt). Based on your requirements for instance placement, choose one of the following:
  - To create A4X instances on any single block:

    ```
        projects/RESERVATION_OWNER_PROJECT_ID/reservations/RESERVATION_NAME
        
    ```
  - To create A4X instances on a specific block:

    ```
        projects/RESERVATION_OWNER_PROJECT_ID/reservations/RESERVATION_NAME/reservationBlocks/RESERVATION_BLOCK_NAME
        
    ```
  - To create A4X instances in a specific subblock:

    ```
        projects/RESERVATION_OWNER_PROJECT_ID/reservations/RESERVATION_NAME/reservationBlocks/RESERVATION_BLOCK_NAME/reservationSubBlocks/RESERVATION_SUBBLOCK_NAME
        
    ```

  > [!TIP]
  > **Tip:** If the reservation exists in the current project, then you can omit `projects/RESERVATION_OWNER_PROJECT_ID/reservations/` from the `RESERVATION` value.

- `TERMINATION_ACTION`: whether Compute Engine stops
  (`STOP`) or deletes (`DELETE`) the A4X instance at the
  end of the reservation period.

- `POLICY_NAME`: the name of the compact placement policy.

<br />

### REST


To create
A4X instances in
bulk, make a `POST` request to the
[`instances.bulkInsert` method](https://docs.cloud.google.com/compute/docs/reference/rest/v1/instances/bulkInsert.md.txt).
**Important:** The following example uses the networking setup for multiple sub-blocks. If
you're creating only a single A4X sub-block and you only created the
gVNIC network in the [Create VPC networks](https://docs.cloud.google.com/ai-hypercomputer/docs/create/create-vms-in-bulk-a4x.md.txt#setup-network) step, then remove the
four RDMA subnets
indicated by the `MRDMA` NIC type from the example.

A4X instances support the following
[types of reservations](https://docs.cloud.google.com/compute/docs/instances/choose-reservation-type.md.txt):

- Future reservations for capacity blocks
- Future reservations in calendar mode

To consume these types of reservations, an instance must use the
*reservation-bound provisioning model*. For example, use the following creation parameters.

```
POST https://compute.googleapis.com/compute/v1/projects/PROJECT_ID/zones/ZONE/instances/bulkInsert
{
  "namePattern": "NAME_PATTERN",
  "count": "COUNT",
  "instanceProperties": {
    "machineType": "a4x-highgpu-4g",
    "disks": [
      {
        "boot": true,
        "initializeParams": {
          "diskSizeGb": "DISK_SIZE",
          "diskType": "hyperdisk-balanced",
          "sourceImage": "projects/IMAGE_PROJECT/global/images/family/IMAGE_FAMILY"
        },
        "mode": "READ_WRITE",
        "type": "PERSISTENT"
      }
    ],
    "serviceAccounts": [
      {
        "email": "default",
        "scopes": [
          "https://www.googleapis.com/auth/cloud-platform"
        ]
      }
    ],
    "networkInterfaces": [
      {
        "accessConfigs": [
          {
            "name": "external-nat",
            "type": "ONE_TO_ONE_NAT"
          }
        ],
        "network": "projects/NETWORK_PROJECT_ID/global/networks/GVNIC_NAME_PREFIX-net-0",
        "nicType": "GVNIC",
        "subnetwork": "projects/NETWORK_PROJECT_ID/region/REGION/subnetworks/GVNIC_NAME_PREFIX-sub-0"
      },
      {
        "network": "projects/NETWORK_PROJECT_ID/global/networks/GVNIC_NAME_PREFIX-net-1",
        "nicType": "GVNIC",
        "subnetwork": "projects/NETWORK_PROJECT_ID/region/REGION/subnetworks/GVNIC_NAME_PREFIX-sub-1"
      },
      {
        "network": "projects/NETWORK_PROJECT_ID/global/networks/RDMA_NAME_PREFIX-mrdma",
        "nicType": "MRDMA",
        "subnetwork": "projects/NETWORK_PROJECT_ID/region/REGION/subnetworks/RDMA_NAME_PREFIX-mrdma-sub-0"
      },
      {
        "network": "projects/NETWORK_PROJECT_ID/global/networks/RDMA_NAME_PREFIX-mrdma",
        "nicType": "MRDMA",
        "subnetwork": "projects/NETWORK_PROJECT_ID/region/REGION/subnetworks/RDMA_NAME_PREFIX-mrdma-sub-1"
      },
      {
        "network": "projects/NETWORK_PROJECT_ID/global/networks/RDMA_NAME_PREFIX-mrdma",
        "nicType": "MRDMA",
        "subnetwork": "projects/NETWORK_PROJECT_ID/region/REGION/subnetworks/RDMA_NAME_PREFIX-mrdma-sub-2"
      },
      {
        "network": "projects/NETWORK_PROJECT_ID/global/networks/RDMA_NAME_PREFIX-mrdma",
        "nicType": "MRDMA",
        "subnetwork": "projects/NETWORK_PROJECT_ID/region/REGION/subnetworks/RDMA_NAME_PREFIX-mrdma-sub-3"
      }
     ],
    "reservationAffinity": {
        "consumeReservationType": "SPECIFIC_RESERVATION",
        "key": "compute.googleapis.com/reservation-name",
        "values": [
          "RESERVATION"
        ]
      },
    "scheduling": {
        "provisioningModel": "RESERVATION_BOUND",
        "instanceTerminationAction": "DELETE",
        "onHostMaintenance": "TERMINATE",
        "automaticRestart": true
      },
    "resourcePolicies": [
      "projects/PROJECT_ID/regions/REGION/resourcePolicies/POLICY_NAME"
    ]
  }
}
```

Replace the following:

- `PROJECT_ID`: the project ID of the project where you want to create the A4X instance.
- `ZONE`: specify a zone in which the machine type that you want to use is available. You must use a zone in the same region as the compact placement policy. For information about regions, see [GPU availability by regions and zones](https://docs.cloud.google.com/compute/docs/regions-zones/gpu-regions-zones.md.txt#view-using-table).
- `NAME_PATTERN`: the name pattern to use for the A4X instances. For example, using `instance-#` for the name pattern generates A4X instances with names such as `instance-1` and `instance-2`, up to the number of A4X instances specified by `--count`.
- `COUNT`: the number of A4X instances to create.
- `DISK_SIZE`: the size of the boot disk in GB. For more information, see either [Google Cloud Hyperdisk size limits](https://docs.cloud.google.com/compute/docs/disks/hyperdisks.md.txt#size-limits) or [Persistent Disk size limits](https://docs.cloud.google.com/compute/docs/disks/resize-persistent-disk.md.txt#size_limits) based on the type of disk.
- `IMAGE_PROJECT`: the project ID of the OS image.
- `IMAGE_FAMILY`: the image family of the OS image that you want to use. For a list of all supported operating systems, see [Supported operating systems](https://docs.cloud.google.com/compute/docs/images/os-details.md.txt#gpu-support).

  > [!TIP]
  > **Tip:** We recommend using [accelerator OS images](https://docs.cloud.google.com/ai-hypercomputer/docs/images.md.txt#accelerator-os-images) for AI-optimized workloads. Unless you have unique GPU driver requirements, these images install all required GPU drivers automatically. For more information about GPU driver requirements, see [Install GPU drivers](https://docs.cloud.google.com/ai-hypercomputer/docs/create/create-vms-in-bulk-a4x.md.txt#install-drivers) in this document.

- `NETWORK_PROJECT_ID`: the project ID of the network.
- `GVNIC_NAME_PREFIX`: the name prefix that you specified when creating the standard VPC networks and subnets that use gVNIC NICs.
- `REGION`: the region of the subnetwork.
- `RDMA_NAME_PREFIX`: the name prefix that you specified when creating the VPC networks and subnets that use RDMA NICs.
- `RESERVATION`: the reservation name, a block, or a subblock within a reservation. To get the reservation name or the available blocks, see [View reserved capacity](https://docs.cloud.google.com/ai-hypercomputer/docs/view-reserved-capacity.md.txt). Based on your requirements for instance placement, choose one of the following:
  - To create A4X instances on any single block:

    ```
        projects/RESERVATION_OWNER_PROJECT_ID/reservations/RESERVATION_NAME
        
    ```
  - To create A4X instances on a specific block:

    ```
        projects/RESERVATION_OWNER_PROJECT_ID/reservations/RESERVATION_NAME/reservationBlocks/RESERVATION_BLOCK_NAME
        
    ```
  - To create A4X instances in a specific subblock:

    ```
        projects/RESERVATION_OWNER_PROJECT_ID/reservations/RESERVATION_NAME/reservationBlocks/RESERVATION_BLOCK_NAME/reservationSubBlocks/RESERVATION_SUBBLOCK_NAME
        
    ```

  > [!TIP]
  > **Tip:** If the reservation exists in the current project, then you can omit `projects/RESERVATION_OWNER_PROJECT_ID/reservations/` from the `RESERVATION` value.

- `TERMINATION_ACTION`: whether Compute Engine stops
  (`STOP`) or deletes (`DELETE`) the A4X instance at the
  end of the reservation period.

- `PROJECT_ID`: the project ID of the compact placement policy.
- `REGION`: the region of the compact placement policy.
- `POLICY_NAME`: the name of the compact placement policy.

<br />

For more information about the configuration options when creating VMs in bulk,
see [Create VMs in bulk](https://docs.cloud.google.com/compute/docs/instances/multiple/create-in-bulk.md.txt) in the
Compute Engine documentation.

### Install GPU drivers

After you create an instance, the instance can't use its GPUs unless the correct GPU drivers are
already installed.


If you didn't specify an [OS image that includes GPU drivers](https://docs.cloud.google.com/ai-hypercomputer/docs/images.md.txt#accelerator-os-images), then see
[Install GPU drivers](https://docs.cloud.google.com/compute/docs/gpus/install-drivers-gpu.md.txt) in the
Compute Engine documentation.

### Optional: Enable NVIDIA Multi-Instance GPU mode

Multi-Instance GPU (MIG) mode is a feature that you can enable for a [supported NVIDIA GPU](https://docs.nvidia.com/datacenter/tesla/mig-user-guide/latest/supported-gpus.html). After you create an instance, you can enable MIG mode on a single GPU that is attached to your machine. With MIG mode enabled, the single GPU is partitioned into as many as seven independent GPU instances. Each instance runs simultaneously, each with its own memory, cache, and streaming multiprocessors. You can then run different workloads on these GPU instances in parallel. For more information about using MIG mode, see the [Multi-Instance GPU (MIG) User Guide](https://docs.nvidia.com/datacenter/tesla/mig-user-guide/index.html#getting-started-with-mig) in the NVIDIA documentation.

## What's next

- [Run workloads overview](https://docs.cloud.google.com/ai-hypercomputer/docs/workloads/overview.md.txt)
- [Troubleshoot reservation consumption](https://docs.cloud.google.com/compute/docs/troubleshooting/troubleshooting-reservation-consumption.md.txt)
- [View the topology of a compute instance](https://docs.cloud.google.com/ai-hypercomputer/docs/manage/instance-topology.md.txt)