Contact UsGet started

Moving a VM to a different availability zone

Written by
Updated at October 30, 2024

When creating a VM, you can choose the Yandex Cloud availability zone where it will be located.

You can move an existing VM to a different availability zone using a special command in the management console or the CLI or by creating its copy in the target availability zone using disk snapshots.

Warning

To monitor the progress of migration and avoid possible issues during it, use disk snapshots or backups from Cloud Backup for migration. In this way, you yourself determine when to shut down your VM in the source availability zone and when to make it appear in the target availability zone. The VM in the source availability zone may continue to run until you make sure that the VM you created from a snapshot works properly in the new availability zone. For detailed recommendations, see Migrating resources to the ru-central1-d availability zone.

Currently, you can use the relocate command to migrate VMs and disks only to the ru-central1-d zone from any other zone.

Warning

The ru-central1-d zone does not support VMs based on the Intel Broadwell platform. To move such VMs to the ru-central1-d zone, do one of the following:

  • Take a disk snapshot and use it to create a new VM in the ru-central1-d zone on a different platform.
  • Stop the VM, change the platform, and move the VM by running relocate.

Moving a VM using disk snapshots

To move a VM to a different availability zone using snapshots, create its copy in the target availability zone and delete the original one.

Create a snapshot of each of the VM's disks

Prepare the disks

A disk snapshot only contains the data that had already been written to the disk when the snapshot was created. If the disk is attached to a running VM, the OS and app cache will not be included in the snapshot.

To ensure the integrity of the snapshot data:

  1. Stop all disk write operations in applications.

  2. Write the OS cache to the disk:

    sync

  3. Freeze the file system:

    sudo fsfreeze --freeze <mount_point>

    Where --freeze is the parameter to freeze the file system. Instead of <mount_point>, specify the folder the file system is connected to, e.g., /mnt/vdc2.

  4. Create a snapshot following the guide below.

  5. Unfreeze the file system:

    sudo fsfreeze --unfreeze <mount_point>

    Where --unfreeze is the parameter to unfreeze the file system. Instead of <mount_point>, specify the folder the file system is connected to, e.g., /mnt/vdc2.

  1. Stop the virtual machine (see Stop).
  2. Wait until the VM status changes to STOPPED.

Create snapshots

To create a disk snapshot:

  1. In the management console, select the folder where the disk is located.

  2. Select Compute Cloud.

  3. In the left-hand panel, select Disks.

  4. In the line of the disk, click and select Create snapshot.

  5. Enter a name for the snapshot. The naming requirements are as follows:

    • The name must be from 3 to 63 characters long.
    • It may contain lowercase Latin letters, numbers, and hyphens.
    • The first character must be a letter and the last character cannot be a hyphen.

  6. If necessary, enter a description of the snapshot.

  7. Click Create.

If you do not have the Yandex Cloud command line interface yet, install and initialize it.

The folder specified in the CLI profile is used by default. You can specify a different folder using the --folder-name or --folder-id parameter.

  1. View a description of the CLI create snapshot commands:

    yc compute snapshot create --help

  2. Select the disk to take a snapshot of. To get a list of disks in the default folder, run the command:

    yc compute disk list

    Result:

    +----------------------+--------------+-------------+-------------------+--------+----------------------+-----------------+-------------+
|          ID          |     NAME     |    SIZE     |       ZONE        | STATUS |     INSTANCE IDS     | PLACEMENT GROUP | DESCRIPTION |
+----------------------+--------------+-------------+-------------------+--------+----------------------+-----------------+-------------+
| a7lqgbt0bb9s******** | first-disk   | 20401094656 |   ru-central1-a   | READY  | a7lcvu28njbh******** |                 |             |
| a7lv5j5hm1p1******** | second-disk  | 21474836480 |   ru-central1-a   | READY  |                      |                 |             |
+----------------------+--------------+-------------+-------------------+--------+----------------------+-----------------+-------------+

  3. Create a snapshot in the default folder:

    yc compute snapshot create \
  --name first-snapshot \
  --description "my first snapshot via CLI" \
  --disk-id fhm4aq4hvq5g********

    As a result, a disk snapshot is created with the name first-snapshot and description my first snapshot via CLI.

    The snapshot naming requirements are as follows:

    • The name must be from 3 to 63 characters long.
    • It may contain lowercase Latin letters, numbers, and hyphens.
    • The first character must be a letter and the last character cannot be a hyphen.

If you don't have Terraform, install it and configure the Yandex Cloud provider.

  1. Describe the resource parameters in the yandex_compute_snapshot configuration file.

    Here is an example of the configuration file structure:

    resource "yandex_compute_snapshot" "snapshot-1" {
  name           = "disk-snapshot"
  source_disk_id = "<disk_ID>"
}

    For more information about resources you can create with Terraform, see the provider documentation.

  2. Make sure the configuration files are valid.

    1. In the command line, go to the directory where you created the configuration file.

    2. Run a check using this command:

      terraform plan

    If the configuration is described correctly, the terminal will display a list of created resources and their parameters. If the configuration contains any errors, Terraform will point them out.

  3. Deploy cloud resources.

    1. If the configuration does not contain any errors, run this command:

      terraform apply

    2. Confirm that you want to create the resources.

    All the resources you need will then be created in the specified folder. You can check the new resources and their configuration using the management console.

  1. Get the list of disks using the list REST API method for the Disk resource or the DiskService/List gRPC API call.
  2. Create a snapshot using the create REST API method for the Snapshot resource or the SnapshotService/Create gRPC API call.

Repeat the steps to create a snapshot of each disk.

Create a VM in a different availability zone with the disks from the snapshots

To create a VM in a different availability zone with the disks from the snapshots:

  1. In the management console, select the folder to create your VM in.

  2. In the list of services, select Compute Cloud.

  3. In the left-hand panel, select Virtual machines.

  4. Click Create virtual machine.

  5. Under Boot disk image:

    • Go to the Custom tab.
    • Click , and, in the window that opens, select Create new.
    • In the Contents field, select Snapshot and then select the disk snapshot you need from the list below. Use filters if you need to.
    • Enter a name for the new boot disk.
    • Select the disk type.
    • Specify the required disk and block size.
    • (Optional) Enable the Delete along with the virtual machine option in the Additional field if you need to automatically delete this disk when deleting the VM.
    • Click Add disk.

  6. Under Location, select an availability zone to place your VM in.

  7. Add a secondary disk:

    • Under Disks and file storages, click Add
    • In the window that opens, select Disk → Create new.
    • In the Contents field, select Snapshot.
    • Enter a name for the new disk.
    • Select the disk type.
    • Specify the required disk and block size.
    • (Optional) Enable the Delete along with the virtual machine option in the Additional field if you need to automatically delete this disk when deleting the VM.
    • Click Add disk.

  8. (Optional) To encrypt a boot disk or a secondary disk, under Disks and file storages, click to the right of the disk name and set encryption parameters for the disk:

    • Select Encrypted disk.
    • In the KMS key field, select the key to encrypt the disk with. To create a new key, click Create new key.
    • In the Service account field, select a service account with the kms.keys.encrypterDecrypter role for the specified key. To create a service account, click Create new account.

    The encryption feature in Compute Cloud is currently at the Preview stage. To access it, open the resource creation page and click Request access under Encryption or contact support.

    If you deactivate the key used to encrypt a disk or snapshot, access to the data will be suspended until you reactivate the key.

    Alert

    If you destroy the key or its version used to encrypt a disk or snapshot, access to the data will be irrevocably lost. Learn more in Destroying key versions.

  9. (Optional) Connect a file storage:

    • Under Disks and file storages, click Add.

      • In the window that opens, select File storage and select the storage you want to connect from the list.

        If you do not have any file storages, click Create file storage to create a new one.

      • Click Add file storage.

  10. Under Computing resources, select a preset configuration or create a new one. To create a configuration:

  11. Under Network settings:

    • In the Subnet field, enter the ID of a subnet in the new VM’s availability zone. Alternatively, you can select a cloud network from the list.

      • Each network must have at least one subnet. If there is no subnet, create one by selecting Create subnet.

      • If you do not have a network, click Create network to create one:

        • In the window that opens, enter the network name and select the folder to host the network.
        • (Optional) Select the Create subnets option to automatically create subnets in all availability zones.
        • Click Create network.

    • In the Public IP field, choose a method for assigning an IP address:

      • Auto: Assign a random IP address from the Yandex Cloud IP address pool. In this case, you can enable DDoS protection using the option below.
      • List: Select a public IP address from the list of previously reserved static addresses. For more information, see Converting a dynamic public IP address to static.
      • No address: Do not assign a public IP address.

    • Select the appropriate security groups. If you leave this field empty, the default security group will be assigned to the VM.

    • Expand the Additional section and select a method for internal IP address assignment in the Internal IPv4 address field:

      • Auto: Assign a random IP address from the pool of IP addresses available in the selected subnet.
      • List: Select a private IP address from the list of previously reserved IP addresses. Click Reserve to reserve a private IP address in the selected subnet if needed.
      • Enable the DDoS protection option, if needed. The option is available if you previously selected the automatic IP assignment method in the public address settings.

    • (Optional) Create records for the VM in the DNS zone:

      • Expand the DNS settings for internal addresses section and click Add record.
      • Specify the zone, FQDN, and TTL for the record. When setting the FQDN, you can select Detect automatically for the zone.
        You can add multiple records to internal DNS zones. For more information, see Cloud DNS integration with Compute Cloud.
      • To create another record, click Add record.

    If you want to attach an additional network interface to your VM, click Add network interface and repeat the settings from this step for the new interface. You can add up to eight network interfaces to a single VM.

  12. Under Access, specify the data for access to the VM:

    • (Optional) Enable VM access via OS Login. The option is available for Linux images from Cloud Marketplace with OS Login in their names.

    • Enter the username into the Login field.

      Alert

      Do not use root or other usernames reserved by the OS. To perform operations requiring superuser permissions, use the sudo command.

    • In the SSH key field, paste the contents of the public key file. You need to create a key pair for the SSH connection yourself. To learn how, see Connecting to a VM via SSH.

    If you want to add several users with SSH keys to the VM at the same time, specify these users' data under Metadata. You can also use metadata to install additional software on a VM when creating it.

    In public Linux images provided by Yandex Cloud, the functionality of connecting over SSH using login and password is disabled by default.

  13. Under General information, specify the VM name:

    • The name must be from 3 to 63 characters long.
    • It may contain lowercase Latin letters, numbers, and hyphens.
    • The first character must be a letter and the last character cannot be a hyphen.

    Note

    The VM name is used to generate an internal FQDN only once: when creating a VM. If the internal FQDN is important to you, choose an appropriate name for the VM at the creation stage.

  14. Under Additional:

  15. Click Create VM.

You will see the new VM in the list. Every new VM gets an IP address and host name (FQDN).

If you do not have the Yandex Cloud command line interface yet, install and initialize it.

The folder specified in the CLI profile is used by default. You can specify a different folder using the --folder-name or --folder-id parameter.

  1. View the description of the CLI command for creating a VM:

    yc compute instance create --help

  2. Prepare the snapshots of the disks, see Creating a disk snapshot.

  3. Get a list of snapshots in the default folder:

    yc compute snapshot list

    Result:

    +----------------------+-----------------+----------------------+--------+----------------------------+
|          ID          |       NAME      |     PRODUCT IDS      | STATUS |        DESCRIPTION         |
+----------------------+-----------------+----------------------+--------+----------------------------+
| fd8rlt1u2rf0l******* | first-snapshot  | f2ecl5vhsftd******** | READY  | my first snapshot via CLI  |
| fhmolt1u2rf0******** | second-snapshot | f2eclmol5lps******** | READY  | my second snapshot via CLI |
+----------------------+-----------------+----------------------+--------+----------------------------+

  4. Select the IDs (ID) or names (NAME) of the snapshots you need.

  5. Create a VM in the default folder:

    yc compute instance create \
  --name first-instance \
  --zone ru-central1-a \
  --public-ip \
  --create-boot-disk snapshot-name=first-snapshot \
  --create-disk snapshot-name=second-snapshot \
  --ssh-key ~/.ssh/id_ed25519.pub

    This command creates a VM named first-instance in the ru-central1-a availability zone, with a public IP and disks from the snapshots.

    Note

    The VM name is used to generate an internal FQDN only once: when creating a VM. If the internal FQDN is important to you, choose an appropriate name for the VM at the creation stage.

    To create a VM without a public IP address, remove the --public-ip flag.

    If you want to add multiple network interfaces to the VM, specify the --network-interface parameter as many times as you need. You can add up to eight network interfaces to a single VM.

Use the create REST API method for the Instance resource or the InstanceService/Create gRPC API call.

Delete the original VM

To delete the original VM:

  1. In the management console, select the folder the VM belongs to.

  2. Select Compute Cloud.

  3. In the line with the appropriate VM, click , and then click Delete.

    To delete multiple VMs, select the VMs you need to delete in the list and click Delete at the bottom of the screen.

  4. In the window that opens, click Delete.

If you do not have the Yandex Cloud command line interface yet, install and initialize it.

The folder specified in the CLI profile is used by default. You can specify a different folder using the --folder-name or --folder-id parameter.

  1. View a description of the CLI instance delete command below:

    yc compute instance delete --help

  2. Get a list of VMs in the default folder:

    yc compute instance list

    Result:

    +----------------------+-----------------+---------------+---------+----------------------+
|          ID          |       NAME      |    ZONE ID    | STATUS  |     DESCRIPTION      |
+----------------------+-----------------+---------------+---------+----------------------+
| fhm0b28lgfp4******** | first-instance  | ru-central1-a | RUNNING | my first vm via CLI  |
| fhm9gk85nj7g******** | second-instance | ru-central1-a | RUNNING | my second vm via CLI |
+----------------------+-----------------+---------------+---------+----------------------+

  3. Select the ID or NAME of the VM, e.g., first-instance.

  4. Delete the VM instance:

    yc compute instance delete first-instance

If you don't have Terraform, install it and configure the Yandex Cloud provider.

If you created an instance using Terraform, you can delete it:

  1. In the command line, go to the directory with the Terraform configuration file.

  2. Delete the resources using this command:

    terraform destroy

    Alert

    Terraform deletes all the resources that you created in the current configuration, such as clusters, networks, subnets, and instances.

  3. Type yes and press Enter.

Use the delete REST API method for the Instance resource or the InstanceService/Delete gRPC API call.

Moving a VM using a special command

When a VM is moved to a different availability zone using the management console or the CLI, its metadata and ID will be preserved. The VM will be moved to the new availability zone together with all the disks attached to it.

Note

The time it takes to move a VM to a different availability zone depends on the size of its disks. It takes about 10 minutes to move a 100 GB disk.

In some cases, the migration may take longer if you are moving it to the ru-central1-d availability zone.

Warning

Currently, the management console only allows moving VMs from the ru-central1-c availability zone. To move VMs from other availability zones, use the CLI or disk snapshots.

  1. In the management console, select the folder the VM belongs to.

  2. Select Compute Cloud.

  3. In the left-hand panel, select Virtual machines.

  4. In the line with the appropriate VM, click → Relocate to another zone. In the window that opens:

    1. In the Availability zone field, choose the availability zone to move the VM to, e.g., ru-central1-d.

    2. Under Network settings, configure each network interface of your VM as follows:

      1. In the Subnet field, select the subnet that corresponds to the selected availability zone.

      2. In the Public IP field, choose a method for public IP address assignment:

        • Auto: Assign a random IP address from the Yandex Cloud IP address pool. In this case, you can enable DDoS protection in additional settings.
        • List: Select a public IP address from the list of previously reserved static addresses. For more information, see Converting a dynamic public IP address to static.
        • No address: Do not assign a public IP address.

      3. Select the appropriate security groups in the Security groups field.

      4. To set up an internal IP address for a VM and enable DDoS protection, expand the Additional section and select a method for internal IP address assignment in the Internal IPv4 address field:

        • Auto: Assign a random IP address from the pool of IP addresses available in the selected subnet.
        • List: Select an internal IP address from the list of previously reserved IP addresses. Click Reserve to reserve an internal IP address in the selected subnet if needed.

      5. Enable the DDoS protection option, if needed. The option is available if you previously selected the automatic IP assignment method in the public address settings.

    3. Click Start relocation to start moving the VM to a different availability zone.

If you do not have the Yandex Cloud command line interface yet, install and initialize it.

The folder specified in the CLI profile is used by default. You can specify a different folder using the --folder-name or --folder-id parameter.

  1. See the description of the CLI command for moving a VM to a different availability zone:

    yc compute instance relocate --help

  2. Get a list of all subnets in the default folder:

    yc vpc subnet list

    Result:

    +----------------------+-----------------------+----------------------+----------------+---------------+-------------------+
|          ID          |         NAME          |      NETWORK ID      | ROUTE TABLE ID |     ZONE      |       RANGE       |
+----------------------+-----------------------+----------------------+----------------+---------------+-------------------+
| bucqps2lt75g******** | subnet-ru-central1-a1 | c64pv6m0aqq6******** |                | ru-central1-a | [192.168.11.0/24] |
| e2lrucutusnd******** | subnet-ru-central1-a2 | c64pv6m0aqq6******** |                | ru-central1-a | [192.168.12.0/24] |
| e2lv9c6aek1d******** | subnet-ru-central1-a3 | c64pv6m0aqq6******** |                | ru-central1-a | [192.168.13.0/24] |
| bltign9kcffv******** | default-ru-central1-b | c64pv6m0aqq6******** |                | ru-central1-b | [192.168.1.0/24]  |
+----------------------+-----------------------+----------------------+----------------+---------------+-------------------+

  3. Get a list of all security groups in the default folder:

    yc vpc sg list

    Result:

    +----------------------+---------------------------------+--------------------------------+----------------------+
|          ID          |              NAME               |          DESCRIPTION           |      NETWORK-ID      |
+----------------------+---------------------------------+--------------------------------+----------------------+
| c646ev94tb6k******** | my-sg-group                     |                                | c64pv6m0aqq6******** |
| c64r84tbt32j******** | default-sg-c64pv6m0aqq6******** | Default security group for     | c64pv6m0aqq6******** |
|                      |                                 | network                        |                      |
+----------------------+---------------------------------+--------------------------------+----------------------+

  4. Get a list of all VMs in the default folder:

    yc compute instance list

    Result:

    +----------------------+---------+---------------+---------+---------------+-------------+
|          ID          |  NAME   |    ZONE ID    | STATUS  |  EXTERNAL IP  | INTERNAL IP |
+----------------------+---------+---------------+---------+---------------+-------------+
| a7lh48f5jvlk******** | my-vm-1 | ru-central1-a | RUNNING |               | 192.168.0.7 |
| epdsj30mndgj******** | my-vm-2 | ru-central1-b | RUNNING |               | 192.168.1.7 |
+----------------------+---------+---------------+---------+---------------+-------------+

  5. Get a list of network interfaces of the VM in question by specifying the VM ID:

    yc compute instance get <VM_ID>

    Result:

    ...
network_interfaces:
  - index: "0"
    mac_address: d0:0d:24:**:**:**
    subnet_id: bucqps2lt75g********
    primary_v4_address:
      address: 192.168.11.23
      one_to_one_nat:
        address: 158.160.**.***
        ip_version: IPV4
  - index: "1"
    mac_address: d0:1d:24:**:**:**
    subnet_id: e2lrucutusnd********
    primary_v4_address:
      address: 192.168.12.32
  - index: "2"
    mac_address: d0:2d:24:**:**:**
    subnet_id: e2lv9c6aek1d********
    primary_v4_address:
      address: 192.168.13.26
...

  6. Move the VM to a different availability zone:

    yc compute instance relocate <VM_ID> \
  --destination-zone-id <availability_zone_ID> \
  --network-interface subnet-id=<subnet_ID>,security-group-ids=<security_group_ID>

    Where:

    • <VM_ID>: ID of the VM to move to a different availability zone.

    • --destination-zone-id: ID of the availability zone to move the VM to.

    • --network-interface: VM network interface settings:

      • subnet-id: ID of the subnet in the availability zone to move the VM to.
      • security-group-ids: ID of the security group to link to the VM you are moving. You can link multiple security groups to a single VM by providing a comma-separated list of security group IDs in [id1,id2] format.

      If a VM has multiple network interfaces, specify the --network-interface parameter as many times as needed (for each network interface).

    For more information about the yc compute instance relocate command, see the CLI reference.

    Examples:

    yc compute instance relocate a7lh48f5jvlk******** \
  --destination-zone-id ru-central1-b \
  --network-interface \
    subnet-id=bltign9kcffv********,security-group-ids=c646ev94tb6k********

    In this example, we are moving a VM named my-vm-1 from the ru-central1-a availability zone to ru-central1-b.

    Result:

    done (3m15s)
id: a7lh48f5jvlk********
folder_id: aoeg2e07onia********
created_at: "2023-10-13T19:47:40Z"
name: my-vm-1
zone_id: ru-central1-b
platform_id: standard-v3
resources:
  memory: "2147483648"
  cores: "2"
  core_fraction: "100"
status: RUNNING
metadata_options:
  gce_http_endpoint: ENABLED
  aws_v1_http_endpoint: ENABLED
  gce_http_token: ENABLED
  aws_v1_http_token: DISABLED
boot_disk:
  mode: READ_WRITE
  device_name: a7lp7jpslu59********
  auto_delete: true
  disk_id: a7lp7jpslu59********
network_interfaces:
  - index: "0"
    mac_address: d0:0d:11:**:**:**
    subnet_id: bltign9kcffv********
    primary_v4_address:
      address: 192.168.1.17
    security_group_ids:
      - c646ev94tb6k********
gpu_settings: {}
fqdn: my-vm-1.ru-central1.internal
scheduling_policy: {}
network_settings:
  type: STANDARD
placement_policy: {}

    If you are moving a VM with a disk in a placement group, use this command:

    yc compute instance relocate <VM_ID> \
  --destination-zone-id <availability_zone_ID> \
  --network-interface subnet-id=<subnet_ID>,security-group-ids=<security_group_ID> \
  --boot-disk-placement-group-id <disk_placement_group_ID> \
  --boot-disk-placement-group-partition <partition_number> \
  --secondary-disk-placement disk-name=<disk_name>,disk-placement-group-id=<disk_placement_group_ID>,disk-placement-group-partition=<partition_number>

    Where:

    • --boot-disk-placement-group-id: Disk placement group ID.

    • --boot-disk-placement-group-partition: Partition number in the disk placement group with the partition placement strategy.

    • --secondary-disk-placement: Placement policy for secondary disks. Parameters:

      • disk-name: Disk name.
      • disk-placement-group-id: ID of the disk placement group to place the disk in.
      • disk-placement-group-partition: Partition number in the disk placement group.

    For more information about the yc compute instance relocate command, see the CLI reference.

Please note that connecting VM's network interfaces to new subnets changes their IP addressing. If you need to specify internal IP addresses for the VM's network interfaces, use the ipv4-address=<internal_IP_address> property of the network-interface parameter; for public IP addresses, use the nat-address=<public_IP_address> property. Other than that, setting up network interface parameters when moving a VM to a different availability zone is similar to setting up the same parameters when creating a VM.

Note

If the VM disks are being written to, moving them may end in an error. In this case, stop writing to the disks or shut down the VM and restart the move.

Examples

Moving a VM to a different zone

In this example, we are moving a VM named my-vm-1 from the ru-central1-a availability zone to ru-central1-d.

yc compute instance relocate a7lh48f5jvlk******** \
  --destination-zone-id ru-central1-d \
  --network-interface \
    subnet-id=bltign9kcffv********,security-group-ids=c646ev94tb6k********

Result:

done (3m15s)
id: a7lh48f5jvlk********
folder_id: aoeg2e07onia********
created_at: "2023-10-13T19:47:40Z"
name: my-vm-1
zone_id: ru-central1-d
platform_id: standard-v3
resources:
  memory: "2147483648"
  cores: "2"
  core_fraction: "100"
status: RUNNING
metadata_options:
  gce_http_endpoint: ENABLED
  aws_v1_http_endpoint: ENABLED
  gce_http_token: ENABLED
  aws_v1_http_token: DISABLED
boot_disk:
  mode: READ_WRITE
  device_name: a7lp7jpslu59********
  auto_delete: true
  disk_id: a7lp7jpslu59********
network_interfaces:
  - index: "0"
mac_address: d0:0d:11:**:**:**
subnet_id: bltign9kcffv********
primary_v4_address:
  address: 192.168.1.17
security_group_ids:
  - c646ev94tb6k********
gpu_settings: {}
fqdn: my-vm-1.ru-central1.internal
scheduling_policy: {}
network_settings:
  type: STANDARD
placement_policy: {}

Moving a VM with disks in a placement group

In this example, we are moving a VM named my-vm-1 with two disks in the placement group from the ru-central1-b availability zone to ru-central1-d.

yc compute instance relocate epd6qtn128k1******** \
  --destination-zone-id ru-central1-d \
  --network-interface \
    subnet-id=fl8glc5v0lqj********,security-group-ids=enp1gjh3q042******** \
  --boot-disk-placement-group-id fv4pfmor782v******** \
  --boot-disk-placement-group-partition 1 \
  --secondary-disk-placement \
    disk-name=disk-two,fv4pfmor782v********,disk-placement-group-partition=2

Result:

done (9m0s)
id: epd6qtn128k1********
folder_id: b1gmit33ngp3********
created_at: "2023-12-07T19:30:20Z"
name: my-vm-1
zone_id: ru-central1-d
platform_id: standard-v3
resources:
  memory: "2147483648"
  cores: "2"
  core_fraction: "100"
status: RUNNING
metadata_options:
  gce_http_endpoint: ENABLED
  aws_v1_http_endpoint: ENABLED
  gce_http_token: ENABLED
  aws_v1_http_token: DISABLED
boot_disk:
  mode: READ_WRITE
  device_name: epdeqrm6g38j********
  auto_delete: true
  disk_id: epdeqrm6g38j********
secondary_disks:
  - mode: READ_WRITE
    device_name: epdi54snn7t6********
    disk_id: epdi54snn7t6********
network_interfaces:
  - index: "0"
    mac_address: d0:0d:6d:76:e1:12
    subnet_id: fl8glc5v0lqj********
    primary_v4_address:
      address: 10.130.0.12
    security_group_ids:
      - enp1gjh3q042********
gpu_settings: {}
fqdn: my-vm-1.ru-central1.internal
scheduling_policy: {}
network_settings:
  type: STANDARD
placement_policy: {}
Previous
Detaching a disk from a VM
Next
Moving a VM to another folder