Menu="OtherSettings" Title="VM Manager" Icon="dynamix.vm.manager.png" Markdown="false" ---

Your hardware does not have Intel VT-x or AMD-V capability. This is required to create VMs in KVM. Click here to see the unRAID Wiki for more information


You must reboot for changes to take effect

Enable VMs:
One or more paths do not exist (view)

Stopping the VM Manager will first attempt to shutdown all running VMs. After 60 seconds, any remaining VM instances will be terminated.

Libvirt version:
QEMU version:
get_connect_information(); echo $qemu_info['hypervisor_major'].'.'.$qemu_info['hypervisor_minor'].'.'.$qemu_info['hypervisor_release']; ?>
Libvirt storage location:

This is the libvirt volume.

Libvirt vdisk size:
GB

If the system needs to create a new libvirt image file, this is the default size to use specified in GB.

To resize an existing image file, specify the new size here. Next time the Libvirt service is started the file (and file system) will increased to the new size (but never decreased).

Libvirt storage location:
Modify with caution: unable to validate path until Array is Started Path does not exist

You must specify an image file for Libvirt. The system will automatically create this file when the Libvirt service is first started.

Default VM storage path:
Modify with caution: unable to validate path until Array is Started Path does not exist

Specify a user share that contains all your VM subdirectories with vdisks

Default ISO storage path:
Modify with caution: unable to validate path until Array is Started Path does not exist

Specify a user share that contains all your installation media for operating systems

Default Windows VirtIO driver ISO (optional):
placeholder="Click to Select"> Download>

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://fedoraproject.org/wiki/Windows_Virtio_Drivers#Direct_download

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.

Default network bridge:

Select the name of the network bridge you wish to use as default for your VMs, the setting 'virbr0' will let libvirt create a virtual bridge that utilizes NAT (network address translation) and act as a DHCP server to hand out IP addresses to virtual machines directly.

More optional selections are present when virtual bridges are created under network settings.

NOTE: You can also specify a network bridge on a per-VM basis.

Enable PCIe ACS Override:

Warning: Use of this setting could cause possible data corruption with certain hardware configurations. Please visit the Lime Technology forums for more information.

A reboot will be required for changes to this setting to take affect.

 

View the log for libvirt: /var/log/libvirt/libvirtd.log

Libvirt volume info
btrfs filesystem show:
".shell_exec("btrfs filesystem show /etc/libvirt").""?>
btrfs scrub status:
".implode("\n", $scrub_status).""?>
 

Scrub runs the btrfs scrub program to check file system integrity.

If repair is needed you should check the Correct file system errors and run a second Scrub pass; this will permit btrfs scrub to fix the file system.

 
Running

Cancel will cancel the Scrub operation in progress.