Hostname, password, and networking settings are configured automatically via cloud-init.
This applies to standard operating system installations that support cloud-init. However, if you are:
-
+
Installing from an ISO image
Configuring the operating system manually during installation
Using Windows (which does not support cloud-init)
-
+
You will need to manually configure networking, security settings, and hostname within the operating system, as cloud-init will not be available in these scenarios.
Determines the sequence in which the virtual machine attempts to boot from available devices. The system will try each device in the specified order until it finds a bootable medium.
-
+
Note: If no explicit boot order is configured, QEMU uses the default platform boot sequence. Changes take effect on the next power event (start, reboot, or reset). The boot order is populated directly from the QEMU configuration via the QEMU API.
@@ -127,7 +127,7 @@
-
+
Control the sequence used when attempting to boot this virtual machine. The list below is
populated directly from the QEMU configuration via the API.
Adds a virtual optical drive to your VM using the next available IDE or SATA slot. The system automatically selects an unused slot (IDE0-IDE4 or SATA0-SATA5).
-
+
Limitations: Cloud-init media devices are automatically ignored. Maximum of 2 CD/DVD-ROM drives per virtual machine.
@@ -203,11 +203,11 @@
-
+
Use the next available IDE or SATA slot to add a virtual optical drive. Cloud-init media is ignored. Maximum of 2 drives allowed.
Attach or detach ISO files from cephfs storage to the virtual CD/DVD-ROM drive. Select an ISO from the dropdown to mount it, or choose "None" to leave the drive empty.
-
+
Apply: Commits your selection and immediately mounts the ISO to the drive.
@@ -288,7 +288,7 @@
-
+
Attach or detach an ISO from cephfs storage for the drive on {{ strtoupper($drive) }}.
Shows the current boot sequence for your virtual machine. Devices are listed in order from highest to lowest priority. The VM will attempt to boot from each device in sequence until it finds a bootable medium.
-
+
Move up/down: Reorder devices to adjust boot priority.
Lists all bootable devices detected in your VM configuration that are not currently part of the boot sequence.
-
+
Device Types: Disk drives (VirtIO, SCSI, SATA, IDE, NVMe), network adapters, and CD/DVD-ROM drives. Each device shows its type, identifier, and configuration details.
@@ -631,9 +631,9 @@
-
These devices can be part of the boot sequence.
+
These devices can be part of the boot sequence.
- {{ count($remainingDevices) }} available
+ {{ count($remainingDevices) }} available
Discards any unsaved changes to the boot order and restores it to match the last saved configuration.
-
+
This button is only enabled when there are unsaved changes. Use this if you want to undo modifications without refreshing the entire configuration from the server.
Commits your boot order changes to the QEMU server configuration. The new boot sequence will be applied to the virtual machine and will take effect on the next power event (start, reboot, or reset).
-
+
If the boot order is empty, the system will reset to the default platform boot sequence.
Cloud-init controls the metadata injected into your VM on first boot and whenever you regenerate the cloud-init drive.
Use Apply to save and regenerate the ISO, Refresh to pull fresh values, and Reset to discard local edits.
Manual installs (ISO workflows, Windows, or images without cloud-init) still require in-guest configuration.
@@ -50,12 +50,12 @@
Cloud-init Settings
-
+
-
@@ -71,7 +71,7 @@
Configure cloud-init metadata that is injected into your virtual machine. These settings control user accounts, SSH keys, hostname, networking, and other first-boot configuration.
-
+
Apply: Saves your changes and regenerates the cloud-init ISO drive. Changes take effect on the next boot.
@@ -86,25 +86,25 @@
-
+
These values map directly to the QEMU configuration (`ciuser`, `nameserver`, `ipconfigX`, etc.). Changes take effect on the next cloud-init run or boot.
-
Access & Credentials
-
+
-
@@ -120,7 +120,7 @@
Configure the default user account and SSH access for your virtual machine. These settings are used by cloud-init to create accounts and configure SSH keys on first boot.
-
+
Username: The default user account created by cloud-init. This user typically has sudo privileges.
@@ -135,7 +135,7 @@
-
Defaults used by cloud-init to create accounts and authorize SSH.
+
Defaults used by cloud-init to create accounts and authorize SSH.
Save writes the password to the database. Save & Apply also pushes it to the hypervisor; reboot for cloud-init to configure the guest OS.
@@ -316,7 +316,7 @@
@forelse($sshKeys as $keyIndex => $key)
-
{{ $key }}
@@ -342,7 +342,7 @@
-
SSH Public Key
@@ -376,11 +376,11 @@
Add Key
-
Add as many keys as needed. The platform management key is always kept but never shown.
+
Add as many keys as needed. The platform management key is always kept but never shown.
-
Add SSH Public Key
@@ -392,7 +392,7 @@
-
+
@@ -415,24 +415,24 @@
-
+
Runs apt/yum update && upgrade when cloud-init executes. Enable only if your template supports unattended upgrades.
-
Network Configuration
-
+
-
@@ -448,7 +448,7 @@
Configure network interfaces for your virtual machine. Each network card corresponds to an ipconfigX parameter in the QEMU configuration, allowing you to set IPv4 and IPv6 addresses independently.
-
+
IP Configuration: Each network interface can have separate IPv4 and IPv6 configurations. Use CIDR notation (e.g., 192.168.1.100/24) for IP addresses.
@@ -463,9 +463,9 @@
-
Each card corresponds to an ipconfigX. Configure IPv4 and IPv6 independently.
+
Each card corresponds to an ipconfigX. Configure IPv4 and IPv6 independently.
Leave fields blank to remove static addressing. If both IPv4 fields are empty, cloud-init omits the IPv4 stanza.
@@ -527,7 +527,7 @@
-
Edit Network Configuration
@@ -542,27 +542,27 @@
-
+
-
+
-
+
-
+
-
+
Leave fields blank to remove static addressing. If both IPv4 fields are empty, cloud-init omits the IPv4 stanza.
@@ -580,18 +580,18 @@
-
+
DNS Settings
-
+
-
@@ -607,7 +607,7 @@
Configure DNS (Domain Name System) settings for your virtual machine. These settings control how the guest OS resolves domain names to IP addresses.
-
+
Search Domain: The default domain suffix appended to hostnames that don't contain a domain. For example, with "example.com" as search domain, "server" resolves to "server.example.com".
Specifies the operating system type for cloud-init metadata generation. This setting helps cloud-init apply the correct configuration format and optimizations for your guest OS.
-
+
Linux: Standard Linux distributions (Ubuntu, Debian, CentOS, etc.). Uses standard cloud-init configuration format.
@@ -844,7 +844,7 @@
-
Controls the ostype option used when generating cloud-init media.
+
Controls the ostype option used when generating cloud-init media.
Determines whether the guest receives nocloud or config-drive metadata. Choose the entry that matches your template.
-
+
Tip: Pick a Windows option only for cloud-ready Windows images (cloudbase-init). Using a Windows entry on Linux templates prevents the nocloud ISO from mounting.