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.
Boot Order
Boot Order Configuration
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.
Control the sequence used when attempting to boot this virtual machine. The list below is
populated directly from the QEMU configuration via the API.
Currently applied:
@if (count($currentOrder))
{{ implode(' → ', array_map(fn ($device) => $availableDevices[$device]['label'] ?? strtoupper($device), $currentOrder)) }}
@else
Default platform order (no explicit devices configured)
@endif
@if(count($cdDrives) < 2)
Create CD/DVD-ROM Drive
Create CD/DVD-ROM Drive
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.
Once created, the drive will appear in the boot order and can be used to mount ISO images for operating system installation or other purposes.
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.
Eject: Quickly removes the currently mounted ISO, setting the drive to empty.
ISO images are stored in cephfs storage and can be used for operating system installation, recovery, or running live environments. The storage prefix is hidden in the dropdown for clarity.
Attach or detach an ISO from cephfs storage for the drive on {{ strtoupper($drive) }}.
ISO Selection
Displays all available ISO images from cephfs storage. Select an ISO to mount it to the drive, or choose "None" to leave the drive empty.
The dropdown shows only the filename (storage prefix is hidden for clarity). Changes to the selection are tracked in real-time, but you must click Apply to actually mount the ISO.
The Apply button will be disabled if the selected ISO matches what's currently mounted.
ApplyApplying...EjectEjecting...
Select "None" to leave the drive empty. Storage prefix is hidden for clarity.
Currently mounted: {{ $this->formatIsoLabel($currentIsos[$drive]) }}
@endif
@endforeach
@if(count($cdDrives) > 0)
Request ISO
Request ISO Image
Opens a support ticket form where you can request that a specific ISO image be added to the cephfs storage.
When submitting a request, include:
An active public URL of the image in .iso format
A project page of the distribution
Name and version of the distribution
Submit your request under the "ISO Request" department for faster processing. Once added, the ISO will appear in the ISO selection dropdown for all users.
Submit a support ticket to request an ISO image be added to cephfs storage.
Request ISO
When requesting an ISO, please ensure your ticket includes:
An active public URL of the image in .iso format
A project page of the distribution
Name and version of the distribution
Please submit your request under the "ISO Request" department.
@endif
Boot priority
Boot Priority
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.
Remove: Exclude a device from the boot sequence.
The "Synced" indicator shows when your changes match the saved configuration; "Unsaved changes" indicates modifications that need to be saved. Changes take effect on the next power event.
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.
Click Add to include a device in the boot priority list. Devices are automatically detected from the QEMU configuration via the QEMU API.
All detected devices are already part of the boot priority list.
@endforelse
Refresh
Reset to current
Reset to Current
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.
Save boot order
Save Boot Order
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.
This button is only enabled when there are unsaved changes.