| _(Name)_: | -- |
-- -Give the VM a name (e.g. Work, Gaming, Media Player, Firewall, Bitcoin Miner)
-
| _(Description)_: | -- |
--Give the VM a brief description (optional field).
-
| _(Override Storage Location)_: | - |
-- - - -Specify the overide storage pool for VM. This option allows you to specify the physical pool/disk used to store the disk images and snapshot data. - Default will follow standard processing and store images in the default location for the share defined in the settings. - A pool/disk(Volume) will be the location for images if the default is overridden. -
-
| _(CPU)_ _(Mode)_: | -- - >_(Migratable)_: - - - | -
--There are two CPU modes available to choose:
-- Host Passthrough
-
- With this mode, the CPU visible to the guest should be exactly the same as the host CPU even in the aspects that libvirt does not understand. For the best possible performance, use this setting. -- Emulated
-
- If you are having difficulties with Host Passthrough mode, you can try the emulated mode which doesn't expose the guest to host-based CPU features. This may impact the performance of your VM. -- Migratable
-
- Migratable attribute may be used to explicitly request such features to be removed from (on) or kept in (off) the virtual CPU. Off will not remove any host features when using Host Passthrough. Not support on emulated. -
| _(Logical CPUs)_: | -
-
- 1 ? 'checked' : 'checked disabled') : '';
- if (!$cpu2) {
- echo "";
- } else {
- echo "";
- $extra = ($arrConfig['domain']['vcpu'] && in_array($cpu2, $arrConfig['domain']['vcpu'])) ? ($arrConfig['domain']['vcpus'] > 1 ? 'checked' : 'checked disabled') : '';
- echo "";
- }
- }
- ?>
-
- |
-
-- -The number of logical CPUs in your system is determined by multiplying the number of CPU cores on your processor(s) by the number of threads.
-Select which logical CPUs you wish to allow your VM to use. (minimum 1).
-
| _(Initial)_ _(Memory)_: | -- - - _(Max)_ _(Memory)_: - - | -
--Select how much memory to allocate to the VM at boot.
-
--For VMs where no PCI devices are being passed through (GPUs, sound, etc.), you can set different values to initial and max memory to allow for memory ballooning. If you are passing through a PCI device, only the initial memory value is used and the max memory value is ignored. For more information on KVM memory ballooning, see here.
-
| _(Machine)_: | -- - | -
--The machine type option primarily affects the success some users may have with various hardware and GPU pass through. For more information on the various QEMU machine types, see these links:
- http://wiki.qemu.org/Documentation/Platforms/PC
- http://wiki.qemu.org/Features/Q35
-As a rule of thumb, try to get your configuration working with i440fx first and if that fails, try adjusting to Q35 to see if that changes anything.
-
| _(BIOS)_: | -- - - - >_(Enable USB boot)_: - - - | -
--- SeaBIOS
-
- is the default virtual BIOS used to create virtual machines and is compatible with all guest operating systems (Windows, Linux, etc.). -- OVMF
-
- (Open Virtual Machine Firmware) adds support for booting VMs using UEFI, but virtual machine guests must also support UEFI. Assigning graphics devices to a OVMF-based virtual machine requires that the graphics device also support UEFI. -- OVMF TPM
-
- (Open Virtual Machine Firmware) adds support for booting VMs using UEFI with TPM and Secure Boot available, but virtual machine guests must also support UEFI. Assigning graphics devices to a OVMF-based virtual machine requires that the graphics device also support UEFI.
-- Once a VM is created this setting cannot be adjusted. -
-- USB Boot
-
- Adds support for booting from USB devices using UEFI. No device boot orders can be specified at the same time as this option.
-
| _(Hyper-V)_: | -- - | -
--Exposes the guest to hyper-v extensions for Microsoft operating systems.
-
| _(USB Controller)_: | -- - | -
--- USB Controller
-
- Select the USB Controller to emulate. Some OSes won't support USB3 (e.g. Windows 7). Qemu XHCI is the same code base as Nec XHCI but without several hacks applied over the years. Recommended to try qemu XHCI before resorting to nec XHCI. -
| _(OS Install ISO)_: | -- - | -
| _(OS Install CDRom Bus)_: | -- - _(Boot Order)_: - - | - -
-- -Select the virtual CD-ROM (ISO) that contains the installation media for your operating system. Clicking this field displays a list of ISOs found in the directory specified on the Settings page.
-- CDRom Bus
-
- Specify what interface this virtual cdrom uses to connect inside the VM. -
| _(VirtIO Drivers ISO)_: | -- - | -
| _(VirtIO Drivers CDRom Bus)_: | -- - | -
--Specify the virtual CD-ROM (ISO) that contains the VirtIO Windows drivers as provided by the Fedora Project. Download the latest ISO from here: https://docs.fedoraproject.org/en-US/quick-docs/creating-windows-virtual-machines-using-virtio-drivers/index.html#virtio-win-direct-downloads
-When installing Windows, you will reach a step where no disk devices will be found. There is an option to browse for drivers on that screen. Click browse and locate the additional CD-ROM in the menu. Inside there will be various folders for the different versions of Windows. Open the folder for the version of Windows you are installing and then select the AMD64 subfolder inside (even if you are on an Intel system, select AMD64). Three drivers will be found. Select them all, click next, and the vDisks you have assigned will appear.
-- CDRom Bus
-
- Specify what interface this virtual cdrom uses to connect inside the VM. -
| _(vDisk Location)_: | -- - | -
| _(vDisk Size)_: | -- - | -
| _(vDisk Type)_: | -- - | -
| _(vDisk Bus)_: | -- - _(Boot Order)_: - - - >_(SSD)_: - title="_(Set SDD flag)_" value="" > - | -
| _(Serial)_: | -- - | -
-- - - - - $arrShare) { - $strLabel = ($i > 0) ? appendOrdinalSuffix($i + 1) : ''; - - ?> -- vDisk Location
- -
- Specify a path to a user share in which you wish to store the VM or specify an existing vDisk. The primary vDisk will store the operating system for your VM. -- NOTE: Unraid will automatically "dereference" vdisk paths when starting a VM. - That is, if a vdisk path is specified as being on a user share, we use the SYSTEM.LOCATION extended attribute to find out what physical disk the image exists on. - We then pass this path when starting a VM via qemu. This ensures that VM I/O bypasses shfs (FUSE user share file system) for better performance. - It also means that a vdisk image file can be moved from one physical device to another without changing the VM XML file. -
- -- Example: /mnt/user/domains/Windows/vdisk1.img will be dereferenced to /mnt/cache/domains/Windows/vdisk1.img (for vdisk1.img physically located in the "cache" volume). -
- -- vDisk Size
- -
- Specify a number followed by a letter. M for megabytes, G for gigabytes. -- vDisk Type
- -
- Select RAW for best performance. QCOW2 implementation is still in development. -- vDisk Bus
- -
- Select virtio for best performance. -- vDisk Boot Order
- -
- Specify the order the devices are used for booting. -- vDisk SSD Flag
- -
- Specify the vdisk shows as SSD within the guest, only supported on SCSI, SATA and IDE bus types. -- vDisk Serial
- -
- Set the device serial number presented to the VM. -Additional devices can be added/removed by clicking the symbols to the left.
-
| _(Unraid Share Mode)_: | -- - _(Unraid Share)_: - - | -
|
- |
- - id="shares[][source]" name="shares[][source]" autocomplete="off" data-pickfolders="true" data-pickfilter="NO_FILES_FILTER" data-pickroot="/mnt/" value="" placeholder="_(e.g.)_ /mnt/user/..." title="_(path of Unraid share)_" /> - | -
| - | - name="shares[][target]" id="shares[][target]" value="" placeholder="_(e.g.)_ _(shares)_ (_(name of mount tag inside vm)_)" title="_(mount tag inside vm)_" /> - | -
--- Unraid Share Mode
- - -
- Used to create a VirtFS mapping to a Linux-based guest. Specify the mode you want to use either 9p or Virtiofs. -- Unraid Share
- -
- Set tag and path to match the selected Unraid share. -- Unraid Source Path
- -
- Specify the path on the host here. -- Unraid Mount tag
-
- Specify the mount tag that you will use for mounting the VirtFS share inside the VM. See this page for how to do this on a Linux-based guest: http://wiki.qemu.org/Documentation/9psetup -- For Windows additional software needs to be installed: https://virtio-fs.gitlab.io/howto-windows.html -
- -Additional devices can be added/removed by clicking the symbols to the left.
-
| _(Graphics Card)_: | -- - - _(Multifunction)_: - - - | -
| _(VM Console Protocol)_: | -- - | -
| _(VM Console enable Copy/paste)_: | -- - |
| _(VM Console AutoPort)_: | -- - - >_(VM Console Port)_: - - > - - >_(VM Console WS Port)_: - - > - | -
| _(VM Console Video Driver)_: | -- - | -
| _(VM Console Password)_: | -- |
| _(VM Console Keyboard)_: | -- - | -
| _(Graphics ROM BIOS)_: | -- - | -
-- - - - - $arrAudio) { - $strLabel = ($i > 0) ? appendOrdinalSuffix($i + 1) : ''; - - ?> -- Graphics Card
- -
- If you wish to assign a graphics card to the VM, select it from this list, otherwise leave it set to virtual. -- Virtual video protocol VNC/SPICE
- -
- If you wish to assign a protocol type, specify one here. -- Virtual enable copy paste for VNC/SPICE
- -
- If you enable copy paste you need to install additional software on the client in addition to the QEMU agent if that has been installed. https://www.spice-space.org/download.html is the location for spice-vdagent for both window and linux. Note copy paste function will not work with web spice viewer you need to use virt-viewer. -- Virtual auto port
- -
- Set it you want to specify a manual port for VNC or Spice. VNC needs two ports where Spice only requires one. Leave as auto yes for the system to set. -- Virtual Video Driver
- -
- If you wish to assign a different video driver to use for a VM Console connection, specify one here. -- Virtual Password
- -
- If you wish to require a password to connect to the VM over a VM Console connection, specify one here. -- Virtual Keyboard
- -
- If you wish to assign a different keyboard layout to use for a VM Console connection, specify one here. -- Graphics ROM BIOS
- -
- If you wish to use a custom ROM BIOS for a Graphics card, specify one here. -Additional devices can be added/removed by clicking the symbols to the left.
-
| _(Sound Card)_: | -- - | -
-- - - - - $domain_bridge, - 'mac' => "", - 'model' => 'virtio-net' - ]; - } - foreach ($arrConfig['nic'] as $i => $arrNic) { - $strLabel = ($i > 0) ? appendOrdinalSuffix($i + 1) : ''; - - ?> -Select a sound device to assign to your VM. Most modern GPUs have a built-in audio device, but you can also select the on-board audio device(s) if present.
-Additional devices can be added/removed by clicking the symbols to the left.
-
| _(Network MAC)_: | -- - | -
| _(Network Source)_: | -- - | -
| _(Network Model)_: | -- - | -
| _(Boot Order)_: | -- style="width: 50px;" name="nic[][boot]" title="_(Boot order)_" value="" > - | -
--- Network MAC
- -
- By default, a random MAC address will be assigned here that conforms to the standards for virtual network interface controllers. You can manually adjust this if desired. -- Network Source
- -
- The default libvirt managed network bridge (virbr0) will be used, otherwise you may specify an alternative name for a private network to the host. -- Network Model
- -
- Default and recommended is 'virtio-net', which gives improved stability. To improve performance 'virtio' can be selected, but this may lead to stability issues. -Use boot order to set device as bootable and boot sequence.
- -Additional devices can be added/removed by clicking the symbols to the left.
-
| - | _(Select)_ _(Optional)_ _(Boot Order)_ |
| _(USB Devices)_: | -
-
- $arrDev) {
- ?>
-
- - "._('None available').""; - } - ?> - |
-
-- -If you wish to assign any USB devices to your guest, you can select them from this list.
-Use boot order to set device as bootable and boot sequence.
-Select optional if you want device to be ignored when VM starts if not present.
-
| - | _(Select)_ _(Boot Order)_ |
| _(Other PCI Devices)_: | -
-
- $arrDev) {
- $bootdisable = $extra = $pciboot = '';
- if ($arrDev["typeid"] != "0108" && substr($arrDev["typeid"],0,2) != "02") $bootdisable = ' disabled="disabled"';
- if (count($pcidevice=array_filter($arrConfig['pci'], function($arr) use ($arrDev) { return ($arr['id'] == $arrDev['id']); }))) {
- $extra .= ' checked="checked"';
- foreach ($pcidevice as $pcikey => $pcidev) $pciboot = $pcidev["boot"];
- } elseif (!in_array($arrDev['driver'], ['pci-stub', 'vfio-pci'])) {
- //$extra .= ' disabled="disabled"';
- continue;
- }
- $intAvailableOtherPCIDevices++;
- ?>
-
- - "._('None available').""; - } - ?> - |
-
-- -If you wish to assign any other PCI devices to your guest, you can select them from this list.
-Use boot order to set device as bootable and boot sequence. Only NVMe and Network devices (PCI types 0108 and 02xx) supported for boot order.
-
| - |
-
-
-
-
-
- - - - - - |
-
-- - -Click Create to generate the vDisks and return to the Virtual Machines page where your new VM will be created.
-
| _(Advanced tuning options)_ | |
| _(QEMU Command Line)_: | - -- |
-- -If you need to add QEMU arguments to the XML
- Examples can be found on the Libvirt page => https://libvirt.org/kbase/qemu-passthrough-security.html - -
| _(Clocks)_ | |||
| _(Clocks Offset)_: | -- - - | -||
| - | - : | -- _(Present)_: - | -- _(Tickpolicy)_: - - |
-- "",'grab'=>"",'repeat'=>"",'grabToggle'=>""]; - foreach ($arrConfig['evdev'] as $i => $arrEvdev) { - $strLabel = ($i > 0) ? appendOrdinalSuffix($i + 1) : ''; - ?> -Allows setting of timers and offset into the XML You should not need to modify these values.
-Windows tuning details can be found here https://forums.unraid.net/topic/134041-guide-optimizing-windows-vms-in-unraid/
-Details can be found on the Libvirt XML page => https://libvirt.org/formatdomain.html#time-keeping
-Defaults are:
-linux Hpet:no Hypervclock: no Pit yes rtc yes tickpolicy catchup.
-Windows Hpet:no Hypervclock: yes Pit yes rtc yes tickpolicy catchup.
-Windows and Hyperv Hpet:no Hypervclock: yes Pit no rtc no.
- -
| _(Evdev Device)_: | -- - | - -
| _(Grab)_: | -- - | -
| _(Repeat)_: | -- - | -
| _(Grab Toggle)_: | -- - | -
--- Event Devices
-
- Evdev is an input interface built into the Linux kernel. QEMU’s evdev passthrough support allows a user to redirect evdev events to a guest. These events can include mouse movements and key presses. By hitting both Ctrl keys at the same time, QEMU can toggle the input recipient. QEMU’s evdev passthrough also features almost no latency, making it perfect for gaming. The main downside to evdev passthrough is the lack of button rebinding – and in some cases, macro keys won’t even work at all. - Optional items are normally only used for keyboards. -- Device
- -
- Host device to passthrough to guest. -- Grab
- -
- All grabs all input devices instead of just one -- Repeat
- -
- Repeat with value 'on'/'off' to enable/disable auto-repeat events -- GrabToggle
- -
- GrabToggle with values ctrl-ctrl, alt-alt, shift-shift, meta-meta, scrolllock or ctrl-scrolllock to change the grab key combinationAdditional devices can be added/removed by clicking the symbols to the left.
-
| - | - - - - - - - - - - | -
-- -Click Create to generate the vDisks and return to the Virtual Machines page where your new VM will be created.
-
| - |
-
-
-
-
-
-
- - - - - - - - - - |
-
| _(Name)_: | -- |
-- -Give the VM a name (e.g. LibreELEC Family Room, LibreELEC Theatre, LibreELEC)
-
| _(Description)_: | -- |
--Give the VM a brief description (optional field).
-
| _(LibreELEC Version)_: | -- - | -
-- -Select which LibreELEC version to download or use for this VM
-
| _(Download Folder)_: | -- - | -
-- -Choose a folder where the LibreELEC image will downloaded to
-
| - | - - | -
| _(Config Folder)_: | -- - - | -
-- -Choose a folder or type in a new name off of an existing folder to specify where LibreELEC will save configuration files. If you create multiple LibreELEC VMs, these Config Folders must be unique for each instance.
-
| _(CPU Mode)_: | -- - | -
--There are two CPU modes available to choose:
-- Host Passthrough
-
- With this mode, the CPU visible to the guest should be exactly the same as the host CPU even in the aspects that libvirt does not understand. For the best possible performance, use this setting. -- Emulated
-
- If you are having difficulties with Host Passthrough mode, you can try the emulated mode which doesn't expose the guest to host-based CPU features. This may impact the performance of your VM. -
| _(Logical CPUs)_: | -
-
- 1 ? 'checked' : 'checked disabled') : '';
- if (!$cpu2) {
- echo "";
- } else {
- echo "";
- $extra = in_array($cpu2, $arrConfig['domain']['vcpu']) ? ($arrConfig['domain']['vcpus'] > 1 ? 'checked' : 'checked disabled') : '';
- echo "";
- }
- }
- ?>
-
- |
-
-- -The number of logical CPUs in your system is determined by multiplying the number of CPU cores on your processor(s) by the number of threads.
-Select which logical CPUs you wish to allow your VM to use. (minimum 1).
-
| _(Initial)_ _(Memory)_: | -- - | - -_(Max)_ _(Memory)_: | -- - | -- |
--Select how much memory to allocate to the VM at boot.
-
--For VMs where no PCI devices are being passed through (GPUs, sound, etc.), you can set different values to initial and max memory to allow for memory ballooning. If you are passing through a PCI device, only the initial memory value is used and the max memory value is ignored. For more information on KVM memory ballooning, see here.
-
| _(Machine)_: | -- - | -
--The machine type option primarily affects the success some users may have with various hardware and GPU pass through. For more information on the various QEMU machine types, see these links:
- http://wiki.qemu.org/Documentation/Platforms/PC
- http://wiki.qemu.org/Features/Q35
-As a rule of thumb, try to get your configuration working with i440fx first and if that fails, try adjusting to Q35 to see if that changes anything.
-
| _(BIOS)_: | -- - - >_(Enable USB boot)_: - - - | -
--- SeaBIOS
-
- is the default virtual BIOS used to create virtual machines and is compatible with all guest operating systems (Windows, Linux, etc.). -- OVMF
-
- (Open Virtual Machine Firmware) adds support for booting VMs using UEFI, but virtual machine guests must also support UEFI. Assigning graphics devices to a OVMF-based virtual machine requires that the graphics device also support UEFI. -- Once a VM is created this setting cannot be adjusted. -
-- USB Boot
-
- Adds support for booting from USB devices using UEFI. No device boot orders can be specified at the same time as this option.
-
| _(USB Controller)_: | -- - | -
--- USB Controller
-
- Select the USB Controller to emulate. Qemu XHCI is the same code base as Nec XHCI but without several hacks applied over the years. Recommended to try qemu XHCI before resorting to nec XHCI. -
| _(Graphics Card)_: | -- - | -
| _(VM Console Protocol)_: | -- - | -
| _(VM Console AutoPort)_: | -- - - >_(VM Console Port)_: - - > - - >_(VM Console WS Port)_: - - > - | -
| _(Graphics ROM BIOS)_: | -- - | -
-- - - - - $arrAudio) { - $strLabel = ($i > 0) ? appendOrdinalSuffix($i + 1) : ''; - - ?> -- Graphics Card
-
- If you wish to assign a graphics card to the VM, select it from this list, otherwise leave it set to virtual. -- virtual video protocol VDA/SPICE
- - Graphics Card
- If you wish to assign a protocol type, specify one here. -
- If you wish to assign a graphics card to the VM, select it from this list, otherwise leave it set to virtual. - - -- virtual video protocol VDC/SPICE
- -
- If you wish to assign a protocol type, specify one here. -- virtual auto port
- - -
- Set it you want to specify a manual port for VNC or Spice. VNC needs two ports where Spice only requires one. Leave as auto yes for the system to set. -- Graphics ROM BIOS
- - 1) {?> -
- If you wish to use a custom ROM BIOS for a Graphics card, specify one here. -Additional devices can be added/removed by clicking the symbols to the left.
- -
| _(Sound Card)_: | -- - | -
-- - - - - $domain_bridge, - 'mac' => "", - 'model' => 'virtio-net' - ] ; - } - foreach ($arrConfig['nic'] as $i => $arrNic) { - $strLabel = ($i > 0) ? appendOrdinalSuffix($i + 1) : ''; - - ?> -Select a sound device to assign to your VM. Most modern GPUs have a built-in audio device, but you can also select the on-board audio device(s) if present.
- 1) {?> -Additional devices can be added/removed by clicking the symbols to the left.
- -
| _(Network MAC)_: | -- - | -
| _(Network Source)_: | -- - | -
| _(Network Model)_: | -- - | -
| _(Boot Order)_: | -- style="width: 50px;" name="nic[][boot]" title="_(Boot order)_" value="" > - | -
--- Network MAC
- -
- By default, a random MAC address will be assigned here that conforms to the standards for virtual network interface controllers. You can manually adjust this if desired. -- Network Source
- -
- The default libvirt managed network bridge (virbr0) will be used, otherwise you may specify an alternative name for a private network to the host. -- Network Model
- -
- Default and recommended is 'virtio-net', which gives improved stability. To improve performance 'virtio' can be selected, but this may lead to stability issues. -Use boot order to set device as bootable and boot sequence.
- -Additional devices can be added/removed by clicking the symbols to the left.
-
| - | _(Select)_ _(Optional)_ _(Boot Order)_ |
| _(USB Devices)_: | -
-
- $arrDev) {
- ?>
-
- - "._('None available').""; - } - ?> - |
-
-- -If you wish to assign any USB devices to your guest, you can select them from this list.
-Use boot order to set device as bootable and boot sequence.
-Select optional if you want device to be ignored when VM starts if not present.
-
| - | _(Select)_ _(Boot Order)_ |
| _(Other PCI Devices)_: | -
-
- $arrDev) {
- $bootdisable = $extra = $pciboot = '';
- if ($arrDev["typeid"] != "0108") $bootdisable = ' disabled="disabled"' ;
- if (count($pcidevice=array_filter($arrConfig['pci'], function($arr) use ($arrDev) { return ($arr['id'] == $arrDev['id']); }))) {
- $extra .= ' checked="checked"';
- foreach ($pcidevice as $pcikey => $pcidev) $pciboot = $pcidev["boot"]; ;
-
- } elseif (!in_array($arrDev['driver'], ['pci-stub', 'vfio-pci'])) {
- //$extra .= ' disabled="disabled"';
- continue;
- }
- $intAvailableOtherPCIDevices++;
- ?>
-
- - "._('None available').""; - } - ?> - |
-
-- -If you wish to assign any other PCI devices to your guest, you can select them from this list.
-Use boot order to set device as bootable and boot sequence. Only NVMe devices (PCI types 0108) supported for boot order.
-
| - |
-
-
-
-
-
- - - - - - |
-
-- -Click Create to return to the Virtual Machines page where your new VM will be created.
-
| - |
-
-
-
-
-
-
- - - - - - - - - |
-
| _(Name)_: | -- |
-- -Give the VM a name (e.g. OpenELEC Family Room, OpenELEC Theatre, OpenELEC)
-
| _(Description)_: | -- |
--Give the VM a brief description (optional field).
-
| _(OpenELEC Version)_: | -- - | -
-- -Select which OpenELEC version to download or use for this VM
-
| _(Download Folder)_: | -- - | -
-- -Choose a folder where the OpenELEC image will downloaded to
-
| - | - - | -
| _(Config Folder)_: | -- - - | -
-- -Choose a folder or type in a new name off of an existing folder to specify where OpenELEC will save configuration files. If you create multiple OpenELEC VMs, these Config Folders must be unique for each instance.
-
| _(CPU Mode)_: | -- - | -
--There are two CPU modes available to choose:
-- Host Passthrough
-
- With this mode, the CPU visible to the guest should be exactly the same as the host CPU even in the aspects that libvirt does not understand. For the best possible performance, use this setting. -- Emulated
-
- If you are having difficulties with Host Passthrough mode, you can try the emulated mode which doesn't expose the guest to host-based CPU features. This may impact the performance of your VM. -
| _(Logical CPUs)_: | -
-
- 1 ? 'checked' : 'checked disabled') : '';
- if (!$cpu2) {
- echo "";
- } else {
- echo "";
- $extra = in_array($cpu2, $arrConfig['domain']['vcpu']) ? ($arrConfig['domain']['vcpus'] > 1 ? 'checked' : 'checked disabled') : '';
- echo "";
- }
- }
- ?>
-
- |
-
-- -The number of logical CPUs in your system is determined by multiplying the number of CPU cores on your processor(s) by the number of threads.
-Select which logical CPUs you wish to allow your VM to use. (minimum 1).
-
| _(Initial)_ _(Memory)_: | -- - | - -_(Max)_ _(Memory)_: | -- - | -- |
--Select how much memory to allocate to the VM at boot.
-
--For VMs where no PCI devices are being passed through (GPUs, sound, etc.), you can set different values to initial and max memory to allow for memory ballooning. If you are passing through a PCI device, only the initial memory value is used and the max memory value is ignored. For more information on KVM memory ballooning, see here.
-
| _(Machine)_: | -- - | -
--The machine type option primarily affects the success some users may have with various hardware and GPU pass through. For more information on the various QEMU machine types, see these links:
- http://wiki.qemu.org/Documentation/Platforms/PC
- http://wiki.qemu.org/Features/Q35
-As a rule of thumb, try to get your configuration working with i440fx first and if that fails, try adjusting to Q35 to see if that changes anything.
-
| _(BIOS)_: | -- - - >_(Enable USB boot)_: - - - | -
--- SeaBIOS
-
- is the default virtual BIOS used to create virtual machines and is compatible with all guest operating systems (Windows, Linux, etc.). -- OVMF
-
- (Open Virtual Machine Firmware) adds support for booting VMs using UEFI, but virtual machine guests must also support UEFI. Assigning graphics devices to a OVMF-based virtual machine requires that the graphics device also support UEFI. -- Once a VM is created this setting cannot be adjusted. -
-- USB Boot
-
- Adds support for booting from USB devices using UEFI. No device boot orders can be specified at the same time as this option.
-
| _(USB Controller)_: | -- - | -
--- USB Controller
-
- Select the USB Controller to emulate. Qemu XHCI is the same code base as Nec XHCI but without several hacks applied over the years. Recommended to try qemu XHCI before resorting to nec XHCI. -
| _(Graphics Card)_: | -- - | -
| _(VM Console Protocol)_: | -- - | -
| _(VM Console AutoPort)_: | -- - - >_(VM Console Port)_: - - > - - >_(VM Console WS Port)_: - - > - | -
| _(Graphics ROM BIOS)_: | -- - | -
-- - - - - $arrAudio) { - $strLabel = ($i > 0) ? appendOrdinalSuffix($i + 1) : ''; - - ?> -- Graphics Card
- - Graphics Card
- If you wish to assign a graphics card to the VM, select it from this list. -
- If you wish to assign a graphics card to the VM, select it from this list, otherwise leave it set to virtual. - - -- virtual video protocol VDC/SPICE
- -
- If you wish to assign a protocol type, specify one here. -- virtual auto port
- -
- Set it you want to specify a manual port for VNC or Spice. VNC needs two ports where Spice only requires one. Leave as auto yes for the system to set. -- Graphics ROM BIOS
- - 1) {?> -
- If you wish to use a custom ROM BIOS for a Graphics card, specify one here. -Additional devices can be added/removed by clicking the symbols to the left.
- -
| _(Sound Card)_: | -- - | -
-- - - - - $domain_bridge, - 'mac' => "", - 'model' => 'virtio-net' - ] ; - } - foreach ($arrConfig['nic'] as $i => $arrNic) { - $strLabel = ($i > 0) ? appendOrdinalSuffix($i + 1) : ''; - - ?> -Select a sound device to assign to your VM. Most modern GPUs have a built-in audio device, but you can also select the on-board audio device(s) if present.
- 1) {?> -Additional devices can be added/removed by clicking the symbols to the left.
- -
| _(Network MAC)_: | -- - | -
| _(Network Source)_: | -- - | -
| _(Network Model)_: | -- - | -
| _(Boot Order)_: | -- style="width: 50px;" name="nic[][boot]" title="_(Boot order)_" value="" > - | -
--- Network MAC
- -
- By default, a random MAC address will be assigned here that conforms to the standards for virtual network interface controllers. You can manually adjust this if desired. -- Network Source
- -
- The default libvirt managed network bridge (virbr0) will be used, otherwise you may specify an alternative name for a private network to the host. -- Network Model
- -
- Default and recommended is 'virtio-net', which gives improved stability. To improve performance 'virtio' can be selected, but this may lead to stability issues. -Use boot order to set device as bootable and boot sequence.
- -Additional devices can be added/removed by clicking the symbols to the left.
-
| - | _(Select)_ _(Optional)_ _(Boot Order)_ |
| _(USB Devices)_: | -
-
- $arrDev) {
- ?>
-
- - "._('None available').""; - } - ?> - |
-
-- -If you wish to assign any USB devices to your guest, you can select them from this list.
-Use boot order to set device as bootable and boot sequence.
-Select optional if you want device to be ignored when VM starts if not present.
-
| - | _(Select)_ _(Boot Order)_ |
| _(Other PCI Devices)_: | -
-
- $arrDev) {
- $bootdisable = $extra = $pciboot = '';
- if ($arrDev["typeid"] != "0108") $bootdisable = ' disabled="disabled"' ;
- if (count($pcidevice=array_filter($arrConfig['pci'], function($arr) use ($arrDev) { return ($arr['id'] == $arrDev['id']); }))) {
- $extra .= ' checked="checked"';
- foreach ($pcidevice as $pcikey => $pcidev) $pciboot = $pcidev["boot"]; ;
-
- } elseif (!in_array($arrDev['driver'], ['pci-stub', 'vfio-pci'])) {
- //$extra .= ' disabled="disabled"';
- continue;
- }
- $intAvailableOtherPCIDevices++;
- ?>
-
- - "._('None available').""; - } - ?> - |
-
-- -If you wish to assign any other PCI devices to your guest, you can select them from this list.
-Use boot order to set device as bootable and boot sequence. Only NVMe devices (PCI types 0108) supported for boot order.
-
| - |
-
-
-
-
-
- - - - - - |
-
-- -Click Create to return to the Virtual Machines page where your new VM will be created.
-
| - |
-
-
-
-
-
-
- - - - - - - - - |
-