TrueNASTrueNAS Nightly Development Documentation
This content follows experimental nightly development software. Pre-release software is intended for testing purposes only.
Use the Product and Version selectors above to view content specific to a stable software release.

Instances

Virtual Machines and Containers in TrueNAS 25.04 and Later

TrueNAS 25.04 replaces the previous KVM hypervisor (TrueNAS 24.10 and earlier) with Incus for virtual machine (VM) deployment. It also introduces support for Linux system containers (LXC), enabling lightweight isolation similar to jails in TrueNAS CORE.

With this change, the Instances (formerly Virtualization) screens in the TrueNAS UI are fully redesigned. We are actively updating Tutorials and UI Reference articles to reflect these changes. Please use the Docs Hub Feedback button (located to the right of any article) to report documentation issues or request improvements to the Instances documentation.

Migrating VMs from 24.10 to 25.04

Manual Migration Required

Due to configuration incompatibilities between the previous KVM hypervisor (TrueNAS 24.10 and earlier) and Incus in TrueNAS 25.04, existing VM configurations do not transfer automatically during the upgrade. However, TrueNAS retains storage zvols, allowing you to manually recreate the previous VM configurations and get them back online.

Instances are an experimental feature intended for community testing only. Users with production VMs on TrueNAS 24.10 should not upgrade to TrueNAS 25.04 until after this experimental feature stabilizes in a future TrueNAS release.

Manual Migration Instructions

To migrate VMs from TrueNAS 24.10 (latest) to 25.04:

  1. Prepare for migration by gathering VM configurations and storage details.
  2. Upgrade to 25.04.
  3. Recreate VMs using the saved configurations and attach existing zvol storage.

Preparing to Migrate VMs from 24.10

  1. Copy or write down the VM configuration:

    a. Go to the Virtualization screen and locate your VM.

    b. Click on the VM row to expand it, then click Edit.

    c. Take a screenshot or manually write down the VM settings, as they do not transfer to 25.04.

    d. Save this information externally for reference.

  2. Copy or write down the storage and virtual device configuration:

    a. Go to the Virtualization screen and locate your VM.

    b. Click on the VM row to expand it, then click Devices.

    c. Click in the Disk row and select Edit.

    d. Note the Zvol path, storage Mode, and Disk Sector Size.

    e. Document all VM devices and their configurations for later use.

Recreating VMs in 25.04

  1. Configure Instances settings:

    a. After upgrading to TrueNAS 25.04, go to Instances (formerly Virtualization).

    b. Click Select Pool to open Global Settings.

    c. Select the storage pool for virtualization from the Pool dropdown.

    d. Accept default networking settings or modify as needed, then click Save.

  2. Recreate the VM using the existing zvol:

    a. Click Create New Instance.

    b. Select VM as the Virtualization Method.

    c. Select Upload ISO, import a zvol or use another volume from VM Image Options.

    d. Click Select Volume to open the Volumes screen, then click Import Zvols to open the Import Zvol dialog.

    1. Enter the path or browse to select an existing Zvol in Select Zvols.

    2. Select the radio button to clone or move the existing zvol.

      • Select Clone to clone and promote a temporary snapshot of the zvol into a custom storage volume.

        This option retains the original zvol while creating an identical copy as an instances volume.

      • Select Move to relocate the existing zvol to the ix-virt dataset as a volume.Enter or browse to select the path to the existing zvol.

    f. Adjust VM settings (CPU, memory, networking, etc.) to match your previous configuration.

    g. Click Create.

Instances (Incus-powered containers and virtual machines) are an experimental feature intended for community testing only. Functionality could change significantly between releases, and instances might not upgrade reliably. Use this feature for testing purposes only—do not rely on it for production workloads. Long-term stability is planned for future TrueNAS Community Edition releases.

Make all configuration changes using the TrueNAS UI. Operations using the command line are not supported and might not persist on upgrade.

For assistance or to discuss this feature with other TrueNAS users, visit our community forums.
To report bugs, submit an issue on TrueNAS Jira.

Instances Screen

The Instances screen allows users to add, edit, or manage virtual machines (VMs) and Linux containers.

The screen header displays a Pool is not selected status before a pool for instances is selected. See Global Settings for more information.

Pool Is Not Selected
Figure 1: Pool Is Not Selected

After setting the pool, Initialized shows on the screen header.

The Instances screen displays No Instances before you create the first instance.

Instances Screen No Instances
Figure 2: Instances Screen No Instances

The Configuration dropdown menu includes Global Settings, Manage Volumes, and Map User/Group IDs options.

Create New Instance at the top right of the screen opens the Create Instance wizard.

Configuration Menu

Configuration on the Instances screen header displays service-level settings that apply to all instances.

Global Settings

Global Settings opens the Global Settings screen showing global options that apply to all instances, including selecting the storage pool for instances and network settings.

Global Settings Screen
Figure 3: Global Settings Screen

Storage Settings

The Pool dropdown list shows a list of available pools on the system. [Disabled] deactivates the pool and disables the instances service.

The screen header displays a Pool is not selected status before a pool for instances is selected.

Default Network Settings

Default Network settings configure global networking defaults for the instances service.

SettingDescription
BridgeSpecifies the network bridge. Automatic uses the default network bridge for communication between instances and the TrueNAS host. The dropdown list option shows existing bridges. See Accessing NAS from VMs and Containers for more information.
IPv4 NetworkSpecifies the IPv4 address for the bridge specified when Bridge is set to Automatic. Enter the IPv4 address and subnet (e.g., 192.168.1.0/24) for the instances to use or leave empty to allow TrueNAS to use the default address.
IPv6 NetworkSpecifies the IPv6 address for the bridge specified when Bridge is set to Automatic. Enter the IPv6 address and subnet (e.g., fd42:96dd:aef2:483c::1/64) for the instances to use or leave empty to allow TrueNAS to use the default address.

Manage Volumes

The Volumes screen lists all volumes currently configured for the instances service.

Volumes Screen
Figure 4: Volumes Screen

Create Volume opens the Create New Volume dialog to configure a new instances volume.

Import Zvols opens the Import Zvol dialog to import an existing Zvol as an instances volume.

Upload ISO opens a file browser to select an .iso file from the client computer and upload it to TrueNAS for use in instances.

Image Filename Requirements

Valid instance names must meet the following conditions:

  • The name must be between 1 and 63 characters long.
  • The name must contain only letters, numbers and dashes from the ASCII table.
  • The name must not start with a digit or a dash.
  • The name must not end with a dash.

Create Volumes

Create Volume on the Volumes screen opens the Create New Volume dialog.

Create New Volume Dialog
Figure 5: Create New Volume Dialog
SettingDescription
NameName of the volume. Enter a name for the volume.
SizeSize of the volume. Enter a size for the volume, for example 1 GiB.

Create creates the new volume.

Import Zvol

Import Zvols on the Volumes screen opens the Import Zvol dialog.

Import Zvol Dialog
Figure 6: Import Zvol Dialog
SettingDescription
Select ZvolsSpecifies the Zvol to import. Enter or browse to select an existing Zvol.
CloneClones and promotes a temporary snapshot of the zvol into a custom storage volume. This option retains the original zvol while creating an identical copy as an instances volume.
MoveRelocates the existing zvol to the ix-virt dataset as a volume.

Delete Volumes

Delete on an image row deletes that image. A Delete volume dialog displays.

Delete Volume Dialog
Figure 7: Delete Volume Dialog

Confirm and then Continue deletes the image. Delete is disabled for active images.

Map User And Group IDs

The Map User and Group IDs screen allows users to manually configure UID and GID mappings inside instances.

Existing mappings are shown in a table containing the group or user name, host ID, and instance ID. Delete on a row deletes that mapping.

Map User and Group IDs Screen
Figure 8: Map User and Group IDs Screen

The Users or Groups tabs display mappings for individual user or group accounts, respectively.

Existing mappings are shown in a table containing the group or user name, host ID, and instance ID. Delete on a row deletes that mapping.

Add New Mapping Settings
SettingDescription
User/GroupSpecifies the user or group account name. Begin typing an account name to search for it or select it from the dropdown menu.
Map to the same UID/GID in the instance(Default) Specifies the host ID-to-instance user or group ID mapping. Select to map the host ID to the same ID in instances.
Instance UID/GID(Displays when Map to the same UID/GID in the instance is not selected)
Specified the user or group ID. Enter the ID number (e.g., 1000) to map the host user or group ID to in instances.

Set creates the mapping. Changes take effect immediately, but instances might require a restart to reflect the changes.

Create Instance Wizard

The Create Instance configuration wizard displays all settings to set up a new container or virtual machine.

Instance Configuration

The Instance Configuration settings specify the instance name, virtualization method or type, and operating system image.

Instance Configuration - Container
Figure 9: Instance Configuration - Container
Instance Configuration Settings - Container
SettingDescription
NameRequired. Enter an alphanumeric name for the instance.
Virtualization MethodRequired. Select Container to create a lightweight Linux container that shares the TrueNAS OS kernel.
ImageBrowse Catalog opens the Select Image screen with available Linux image choices from linuxcontainers.org. Search or browse to locate your desired image and click Select.

Instance Name Requirements

An instance name must meet these criteria:

  • It must be between 1 and 63 characters long.

  • It can only include letters, numbers, and dashes from the ASCII character set.

  • It cannot begin with a number or a dash.

  • It cannot end with a dash.

Instance Configuration Settings - VM
SettingDescription
NameRequired. Enter an alphanumeric name for the instance.
Virtualization MethodRequired. Select VM to create a fully isolated virtual machine using any operating system.
VM Image Options(Shows when Virtualization Method is set to VM)
Use a Linux imageSelect to choose a Linux image from linuxcontainers.org. Browse Catalog opens the Select Image screen with available image choices. Search or browse to locate your desired image and click Select.
Upload ISO, import a zvol or use another volumeSets the method to use to for the storage option. Select to create the VM using an .iso image, import a zvol from a previously installed VM, or use an existing instances volume. Select ISO opens the Volumes screen. See Volumes for more information.

Instance Name Requirements

An instance name must meet these criteria:

  • It must be between 1 and 63 characters long.

  • It can only include letters, numbers, and dashes from the ASCII character set.

  • It cannot begin with a number or a dash.

  • It cannot end with a dash.

CPU & Memory

The CPU & Memory settings specify the number of virtual CPU cores to allocate to the virtual machine and memory size.

CPU & Memory
Figure 11: CPU & Memory

CPU and Memory Settings
SettingDescription
CPU Configuration(Required for VMs) Enter the number of virtual CPU (vCPU) cores to allocate to the instance. Set to an integer to expose that number of full vCPU cores to the instance.

Set to a range or comma-separated list to pin vCPUs to specific physical cores. For better cache locality and performance, select cores that share the same cache hierarchy or NUMA node. For example, to assign cores 0,1,2,5,9,10,11, you can write: 1-2,5,9-11.

For Linux containers, you can set CPU limits or leave this field blank to allow access to all host CPUs.
Memory Size(Required for VMs) Allocate RAM for the instance. This field accepts human-readable input (Ex. 50 GiB, 500M, 2 TB). If units are not specified, the value defaults to mebibytes (MiB). The minimum value is 32 MiB.

For Linux containers, you can set memory limits or leave this field blank to allow access to all host memory.

Environment

The Environment settings configure optional environment variables to run on boot or execute. These settings are only available for containers and cannot be used with VMs.

Add displays a set of environment fields.

Environment
Figure 12: Environment

Environment Settings
SettingDescription
NameEnter the name of the environment variable to set (for example, LANG).
ValueEnter the value to assign to the environment variable (for example, en_US.UTF-8).

Disks

The Disks settings allow mounting storage volumes to an instance. Container options include creating a new dataset or using an existing one. VMs use the Volumes screen to select or create a new volume. VMs must specify the I/O bus and size of the root disk.

Add displays a set of fields to create or mount a disk.

Disks - VM
Figure 13: Disks - VM
Disks Settings
SettingDescription
Root Disk I/O Bus(Required for VMs only) Set the root disk I/O bus type to the option that best suits system needs. Options are:
  • NVMe – Ideal for high-performance storage with faster read and write speeds.
  • Virtio-BLK – Efficient for virtualized environments, offering direct block device access with lower overhead.
  • Virtio-SCSI – Flexible and scalable, supporting advanced features like hot-swapping and multiple devices.
Root Disk Size (in GiB)(Required for VMs only) Enter a plain integer to configure the size of the VM root disk (default 10).
Source(Required) Displays after clicking Add in Disks. Enter an existing zvol or create a new dataset using the Create Dataset option that allows creating a new dataset after entering a path or browsing to select a parent dataset from the dropdown list of datasets on the system. Enter a name for the new dataset in the Create Dataset window. Create adds the dataset.

To use an existing zvol, select an existing zvol from the dropdown list.
Destination(Required for containers only) Specifies the file system path to mount the disk in the container, for example /media or /var/lib/data.
I/O Bus(Required for VMs only) Sets the disk I/O bus type to what best suits system needs. Options are NVMe, Virtio-BLK, or Virtio-SCSI.

Proxies

The Proxies settings allow you to forward network connections between the host and the instance. This routes traffic from a specific address on the host to an address inside the instance, or vice versa, allowing the instance to connect externally through the host. These settings are only available for containers and cannot be used with VMs.

Add displays a set of proxy configuration settings.

Proxies
Figure 14: Proxies
Proxies Settings

SettingDescription
Host ProtocolSets the connection protocol for the TrueNAS host. Options are TCP or UDP.
Host PortSets TrueNAS host port to map to the instance port on the container, for example 3600.
Instance ProtocolSets the connection protocol for the container. Select from the options TCP or UDP.
Instance PortSets the port number within the container. Enter a port number to use, for example 80.

Network

The Network settings configure how the instance connects to the host and external networks. Options include the default network bridge, an existing bridge interface, or a MACVLAN.

See Accessing NAS from VMs and Containers for more information.

Default Network Settings
Figure 15: Default Network Settings
Network Settings
SettingDescription
Use default network settingsSelect to use default network settings to connect the instance to the host using the automatic bridge defined in Global Settings. Selected by default. Disable to display the Bridged NICs (if available) and Macvlan NICs settings.
Bridged NICsSelect an existing bridge on the TrueNAS host to connect to the instance. Displays when one or more existing bridge interface(s) is available.
Macvlan NICsSelect an existing interface to create a virtual network interface based on it, assigning a unique MAC address so the instance appears as a separate device on the network.

A MACVLAN NIC on the same physical interface as the TrueNAS host cannot directly communicate with the host. MACVLAN sends traffic directly to the external network without passing through the host network stack. The host does not recognize MACVLAN packets as local, so any traffic between them must be routed through an external switch, use a separate NIC, or use a network bridge.

USB Devices

USB Devices displays a list of available devices to attach to an instance, allowing the device to function as if physically connected.

USB Devices
Figure 17: USB Devices

GPU Devices

GPU Devices displays available GPU devices to attach to an instance, enabling it to utilize hardware acceleration for graphics or computation tasks.

GPU Devices
Figure 18: GPU Devices

PCI Passthrough

PCI Passthrough settings enable assigning a physical PCI device, such as a network card or controller, directly to a VM, allowing it to use the device as if physically attached. These settings are only available for VMs and cannot be used with containers.

The selected PCI device(s) cannot be in use by the host or share an IOMMU group with devices the host requires.

PCI Passthrough
Figure 19: PCI Passthrough

Add PCI Passthrough opens the Add PCI Passthrough Device screen.

VNC

The VNC settings allow you to enable VNC access for a VM, configure the VNC port, and set a VNC password for remote access. These settings are only available for VMs and cannot be used with containers.

VNC Settings
Figure 20: VNC Settings

VNC Settings
SettingDescription
Enable VNCSelect to allow remote desktop access via VNC.
VNC PortEnter a port number to configure the port that the VM VNC server listens for connections on.
VNC PasswordEnter a password to authenticate VNC access to the VM. Note: A VNC password is not cryptographically secure. You should not rely on it as a single authentication mechanism for your VMs.

Security

The Security settings control various system security features, including Trusted Platform Module (TPM) and Secure Boot options. These options help to ensure a secure environment by enabling advanced hardware-based security features during system startup and operation. These settings are only available for VMs and cannot be used with containers.

Security Settings
Figure 21: Security Settings
Security Settings
SettingDescription
Add Trusted Platform Module (TPM)Enables TPM, a hardware-based security feature that protects sensitive data and ensures integrity. Adds a Trusted Platform Module (TPM) device to the VM.
Secure BootSets boot to ensure that only trusted, signed software is loaded during the system boot process. Can be incompatible with some images.

Instances Table

The Instances table lists each configured instance, displaying its name, type, current state, and options to restart or stop it. Stopped instances show the option to start the instance.

Instances Screen - Populated
Figure 22: Instances Screen - Populated

The Details for Instance widgets show information and management options for the selected instance.

restarts or stops a running instance. starts a stopped instance.

Search above the Instances table allows entering the name of an instance to locate a configured instance.

The checkbox on each instance row shows the Bulk Actions dropdown.

Bulk Actions

The Bulk Actions dropdown list allows you to apply actions to one or more instances on your system. Options are Start All Selected, Stop All Selected, and Restart All Selected.

Bulk Actions
Figure 23: Bulk Actions

Instances Widgets

The Details for Instance widgets display information and configuration options for the selected instance.

General Info Widget

The General Info widget displays the instance status, autostart setting, base image, CPU, memory, and secure boot configuration. It includes the Edit and Delete buttons for the instance.

General Info Widget
Figure 24: General Info Widget

Delete opens the Delete dialog.

Edit opens an Edit Instance: Instance configuration screen populated with editable settings also found on the install wizard screen for the instance.

Delete Instances

The Delete dialog asks for confirmation to delete the selected instance.

Delete Instance Dialog
Figure 25: Delete Instance Dialog

Confirm activates the Continue button. Continue starts the delete operation.

Devices Widget

The Devices widget displays all USB, GPU, Trusted Platform Module (TPM), and PCI Passthrough devices attached to the instance.

Devices Widget
Figure 26: Devices Widget

Add opens a list of available USB Devices, GPUs, TPM, and PCI Passthrough devices.

Add Device under PCI Passthrough opens the Add PCI Passthrough Device screen.

Disks Widget

The Disks widget shows the storage devices attached to the instance, along with their associated paths. It allows you to manage the disks, including adding new ones or modifying existing ones.

Disks Widget
Figure 27: Disks Widget

Add opens the Add Disk screen for adding new disks to the instance.

For existing disks, the more_vert actions include options to Edit or Delete the disk mount.

For VMs, the widget displays the current root disk size. The root disk stores the OS and serves as the boot disk for the VM. Change opens the Change Root Disk Setup dialog.

Add/Edit Disk Screen

The Add/Edit Disk screen allows you to configure a new disk or modify an existing one attached to an instance.

Add Disk Screen - VM
Figure 28: Add Disk Screen - VM
Add/Edit Disk Settings - VM
SettingDescription
VolumeSelect Volume opens the Volumes screen to create or select a volume to attach.
Boot PrioritySets the order in which to boot disks. By default, the root disk is set to 1, which is the highest priority.
I/O BusSets the I/O bus for the disk. Options are NVMe, Virtio-BLK, and Virtio-SCSI.
Add/Edit Disk Settings - Container
SettingDescription
SourceEnter or browse to select the host source path for the disk. For a new dataset, enter or browse to select the parent path.
DestinationEnter the destination path to mount the disk in the instance.

Save applies changes.

Delete Disk Mounts

The Delete Item dialog asks for confirmation to delete the selected disk mount.

Delete Item Dialog
Figure 30: Delete Item Dialog

Confirm activates the Continue button. Continue starts the delete operation.

Change Root Disk Setup

The Change Root Disk Setup dialog allows you to configure the size of the disk a VM stores its OS on and boots from and change the root disk I/O bus.

Increase Root Disk Size Widget
Figure 31: Increase Root Disk Size Widget
SettingDescription
Root Disk Size (in GiB)Increases the size of the VM root disk. Enter a new root disk size in GiB, such as 20.
Root Disk I/O BusSets the communication pathway type for the root disk. Options are NVMe, Virtio-BLK, and Virtio-SCSI.

Save applies changes.

NIC Widget

The NIC Widget displays the network interfaces (NICs) attached to the instance, along with their names and types. It allows you to add new NICs and manage existing ones.

NIC Widget
Figure 32: NIC Widget

Add opens a menu with available NIC choices, allowing you to select and attach a new NIC to the instance.

For existing NICs, the more_vert actions menu allows you to delete the NIC.

Delete NICs

The Delete Item dialog asks for confirmation to delete the selected NIC.

Delete Item Dialog
Figure 33: Delete Item Dialog

Confirm activates the Continue button. Continue starts the delete operation.

Proxies Widget

The Proxies widget displays the network proxy settings configured for the instance. It allows you to manage these settings, including adding, editing, or removing proxies. These settings are only available for containers and cannot be used with VMs.

Proxies Widget
Figure 34: Proxies Widget

Add opens the Add Proxy screen to configure a new proxy for the instance.

For existing proxies, the more_vert actions menu includes options to Edit or Delete the proxy.

Add/Edit Proxy Screen

The Add/Edit Proxy screen allows you to configure or modify a proxy setting attached to an instance.

Add Proxy Screen
Figure 35: Add Proxy Screen

SettingDescription
Host ProtocolSets the connection protocol for the TrueNAS host. Options are TCP or UDP.
Host PortSets TrueNAS host port to map to the instance port on the container, for example 3600.
Instance ProtocolSets the connection protocol for the container. Select from the options TCP or UDP.
Instance PortSets the port number within the container. Enter a port number to use, for example 80.

Save applies changes.

Delete Proxies

The Delete Item dialog asks for confirmation to delete the selected proxy configuration.

Delete Item Dialog
Figure 36: Delete Item Dialog

Confirm activates the Continue button. Continue starts the delete operation.

Idmap Widget

The Idmap widget shows the user ID (UID) and group ID (GID) mappings used by the instance to translate IDs between the host and the container or VM. It provides details such as the Host ID, Maprange, and NS ID for both UIDs and GIDs. These settings are only available for containers and cannot be used with VMs.

Idmap Widget
Figure 37: Idmap Widget
  • Host ID shows the starting ID used by the host for mapping to the instance IDs.
  • Maprange indicates the range of IDs that the host allocates for the instance.
  • NS ID represents the namespace ID used for the mapping.

For example, if the Host ID is 2147000001 and the Maprange is 458752, the container UID 0 (root) is mapped to the host UID 2147000001. This ensures proper isolation and user/group identity management between the host and the instance.

Tools Widget

The Tools widget provides quick access to various tools and utilities for managing your instance. You can open a shell, console, or VNC session directly from this widget.

Tools Widget - VM
Figure 38: Tools Widget

Shell opens an Instance Shell session for command-line interaction with the instance.

Serial Console (VM only) opens an Instance Console session to access the system console for the instance.

VNC (VM only) opens a VNC connection using your preferred client. It uses a VNC URL scheme (for example, vnc://hostname.domain.com:5930) to launch the session directly in the application. If your environment does not support VNC URLs, you can manually connect using a VNC client by entering the host name or IP address followed by the port number without vnc:// (for example, hostname.domain.com:5930 or IP:5930).

Metrics Widget

The Metrics widget displays real-time graphs that monitor instance performance, including CPU usage, memory usage, and disk I/O pressure.

Metrics Widget
Figure 39: Metrics Widget

CPU (%) shows the percentage of CPU usage over time.

Memory (MiB) displays the memory usage in MiB over time.

Disk I/O Full Pressure (%) tracks the disk input/output pressure as a percentage over time.

Edit Instance Screen

The Edit Instance: Instance screen settings are a subset of those found on the Create Instance Wizard screens. It includes the general Instance Configuration and CPU and Memory settings for all instances. Additionally, containers include Environment settings. VMs include VNC and Security settings. To edit device, disk, network, or proxy settings, use the Instances Widgets on the Instances screen.

Edit Instance Configuration Settings

The Instance Configuration settings on the Edit screen allow you to modify basic parameters for the instance, such as startup behavior.

Edit Instance Configuration
Figure 40: Edit Instance Configuration

Autostart automatically starts the instance when the system boots.

Edit CPU and Memory Settings

The CPU & Memory settings on the Edit screen are the same as those in the Create Instance wizard.

Edit CPU & Memory
Figure 41: Edit CPU & Memory

CPU and Memory Settings
SettingDescription
CPU Configuration(Required for VMs) Enter the number of virtual CPU (vCPU) cores to allocate to the instance. Set to an integer to expose that number of full vCPU cores to the instance.

Set to a range or comma-separated list to pin vCPUs to specific physical cores. For better cache locality and performance, select cores that share the same cache hierarchy or NUMA node. For example, to assign cores 0,1,2,5,9,10,11, you can write: 1-2,5,9-11.

For Linux containers, you can set CPU limits or leave this field blank to allow access to all host CPUs.
Memory Size(Required for VMs) Allocate RAM for the instance. This field accepts human-readable input (Ex. 50 GiB, 500M, 2 TB). If units are not specified, the value defaults to mebibytes (MiB). The minimum value is 32 MiB.

For Linux containers, you can set memory limits or leave this field blank to allow access to all host memory.

Edit VNC Settings

The VNC settings on the Edit screen are the same as those in the Create Instance wizard. These settings are only available for VMs and cannot be used with containers.

Edit VNC
Figure 42: Edit VNC

VNC Settings
SettingDescription
Enable VNCSelect to allow remote desktop access via VNC.
VNC PortEnter a port number to configure the port that the VM VNC server listens for connections on.
VNC PasswordEnter a password to authenticate VNC access to the VM. Note: A VNC password is not cryptographically secure. You should not rely on it as a single authentication mechanism for your VMs.

Edit Environment Settings

The Environment settings on the Edit screen are the same as those in the Create Instance wizard. These settings are only available for containers and cannot be used with VMs.

Add displays a set of environment fields.

Environment Settings
Figure 43: Environment Settings

Environment Settings
SettingDescription
NameEnter the name of the environment variable to set (for example, LANG).
ValueEnter the value to assign to the environment variable (for example, en_US.UTF-8).

Edit Security Settings

The Security settings on the Edit screen allow you to enable Secure Boot for the instance, ensuring that only trusted, signed software runs during the startup process. These settings are only available for VMs and cannot be used with containers.

Security Settings
Figure 44: Security Settings
Security Settings
SettingDescription
Secure BootSelect to ensure only trusted, signed software runs during startup. Some images are not compatible with Secure Boot.

Add PCI Passthrough Device Screen

The Add PCI Passthrough Device screen lists the available physical PCI devices that can be attached to an instance.

Add PCI Passthrough Device Screen
Figure 45: Add PCI Passthrough Device Screen

Use Search Devices or the Type dropdown to filter available devices. The selected PCI device(s) must not be in use by the host or share an IOMMU group with any device the host requires.

Select attaches the selected device.