Skip to main content
When you create a virtual machine (VM) or edit its configuration, you operate with VM settings. Below is the list of the VM settings available in the web console, on the VM creation page.

​
Computing resources

In the Computing resources section, you configure the following settings:
  • Whether a VM should have GPUs.
  • VM type, regular or preemptible, for a VM with GPUs. Containers over VMs and VMs without GPUs are always based on regular VMs, so the selection of the VM type is unavailable for them.
  • Platform and preset.
  • (Optional) GPU cluster. Allows accelerating tasks that require high-performance computing (HPC) power, such as training a model. A GPU cluster only helps if you add at least two VMs with 8 GPUs each to the cluster. For containers over VMs, you can assign a GPU cluster in the Advanced settings section.

​
Disks

In the VM configuration, you can add a boot disk and additional disks. In their configuration, you specify their type, size and block size. A boot disk is additionally based on an operating system. Maximum size of a boot disk is 30,720 GiB (30 TiB). For more information about these settings, see Volume parameters. Boot disks are unavailable for containers over VMs. Only additional disks are available in advanced settings.

​
Shared filesystems

In the Shared filesystems section, you attach a filesystem to a VM. A filesystem has the following settings:
  • Name, size and block size.
  • Mount tag for mounting the filesystem to the VM. Create your own tag, such as my-filesystem. Make sure that it is unique within a VM.
  • Auto mount option enabled to mount the filesystem to the VM automatically.

​
Network

In the Network section, you select a network and subnet. Also, you manage the VM addresses:
  • Private address: Select whether to allocate a random private IP address for the VM or to attach an allocation of a private address.
  • Public address: Specify whether the VM should have a public IP address and whether it should be static or dynamic.
If you need to secure your VM and make it isolated, you can create a VM without a public IP address. If you need to connect to this VM from the internet, you can set up a WireGuard jump server. It has an IP address in the internet and an IP address in the VM’s network. As a result, you can access the VM via the jump server from the internet. This approach enhances security and still provides access to the VM. For more information about the settings of the addresses, see Private and public IP addresses of Compute virtual machines.

​
Access

In the Access section, you add a username and SSH key. As a result, you add credentials of the user on behalf of whom you can connect to the VM. The access settings include the following:
  • Username of the VM user. Cannot be root or admin. These usernames are reserved for internal needs and are not allowed to connect to a VM by SSH.
  • Public key of your SSH key pair. To generate an SSH key pair, run the ssh-keygen -t ed25519 command.
  • Name of credentials to recognize the key in the list of keys.

​
Additional

In the Additional section, specify a service account that will perform actions on behalf of the VM, for example, run scripts.