MikeW

With the existing web GUI or with some updates? As long as it feels like an "app" then my family could use it.

I have no problem using the unRAID web GUI to manage my VMs, but I was thinking about creating VMs for other family members and how they would control them. I think it would be a great feature if unRAID had a mobile app which would allow users (wife and kids) to perform very basic VM tasks such as start, force stop and reset. Each VM would have permissions for who could control it remotely from the app. I know this won't be high on the priority list of feature requests, but I think this would be a great addition to allow non-techies to have basic control of their VMs and would align with Lime Technology's goal of pushing their solutions beyond the tech savvy crowd.

:) Looks like that did the trick. Can you give a brief explanation regarding that line with "ioh3420"? I'm also curious why it's "bus=pci.0" instead of "bus=pcie.0". Thanks, -Mike

After Googling a bit more I believe I don't have everything I need in the <qemu:commandline> section, but I'm not sure what needs to be added. <domain type='kvm' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'> <name>Windows 8</name> <uuid>1f5e5059-e6a1-7d99-e9b4-766bfeff4633</uuid> <description>Windows 8 Gaming</description> <metadata> <vmtemplate name="Custom" icon="windows.png" os="windows"/> </metadata> <memory unit='KiB'>4194304</memory> <currentMemory unit='KiB'>4194304</currentMemory> <memoryBacking> <nosharepages/> <locked/> </memoryBacking> <vcpu placement='static'>4</vcpu> <cputune> <vcpupin vcpu='0' cpuset='0'/> <vcpupin vcpu='1' cpuset='1'/> <vcpupin vcpu='2' cpuset='2'/> <vcpupin vcpu='3' cpuset='3'/> </cputune> <os> <type arch='x86_64' machine='pc-i440fx-2.3'>hvm</type> <loader type='pflash'>/usr/share/qemu/ovmf-x64/OVMF-pure-efi.fd</loader> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough'> <topology sockets='1' cores='4' threads='1'/> </cpu> <clock offset='localtime'> <timer name='rtc' tickpolicy='catchup'/> <timer name='pit' tickpolicy='delay'/> <timer name='hpet' present='no'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/bin/qemu-system-x86_64</emulator> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/cache/VM/Windows 8/vdisk1.img'/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/ISO/win8.iso'/> <target dev='hda' bus='ide'/> <readonly/> <boot order='2'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/ISO/virtio-win-0.1.96.iso'/> <target dev='hdb' bus='ide'/> <readonly/> <address type='drive' controller='0' bus='0' target='0' unit='1'/> </disk> <controller type='usb' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/> </controller> <controller type='pci' index='0' model='pci-root'/> <controller type='ide' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:d4:78:d5'/> <source bridge='br0'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </interface> <serial type='pty'> <target port='0'/> </serial> <console type='pty'> <target type='serial' port='0'/> </console> <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/Windows 8.org.qemu.guest_agent.0'/> <target type='virtio' name='org.qemu.guest_agent.0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x01' slot='0x00' function='0x1'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </hostdev> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/> </memballoon> </devices> <qemu:commandline> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=09:00.0,bus=root.1,addr=00.1'/> </qemu:commandline> </domain>

I'm trying to passthrough a PCIe USB3 controller card which is based on the Renasas chip, but I get the following pop-up dialog error when I try to run the my Win8 VM: 2015-07-23T23:43:26.497522Z qemu-system-x86_64: -device vfio-pci,host=09:00.0,bus=root.1,addr=00.1: Bus 'root.1' not found I'm using the ASRock Z97 Extreme6 motherboard and I have discovered that the PCIe x1 slot that the USB controller card is plugged into sits behind an ASMedia 1184 PCIe switch. I'm not sure how to determine the correct setting for "bus=root.1,addr=00.1", but it seems like this is due to the PCIe switch device. This is the output from the readlink command. The USB controller card is 09:00.0. root@unraid:~# readlink /sys/bus/usb/devices/usb3 ../../../devices/pci0000:00/0000:00:1c.3/0000:05:00.0/0000:06:05.0/0000:09:00.0/usb3 Any ideas what values I need to use for "bus" and "addr"? Thanks.