May 4, 201511 yr I removed the virtio and vm plugins, updated to beta15, enabled VM's in VM Manager in settings, then started my windows 8.1 VM. It basically worked fine, but my IR remote no longer works. I suspect it's not being passed thru correctly, but that's just a guess. I know things have changed with the new version and the new VM Manager, but I've been busy with other stuff to follow all the details. Hopefully there's something simple I can do to 'update' my VM to a fully working state again. Any pointers or suggestions are most welcome.
May 4, 201511 yr I removed the virtio and vm plugins, updated to beta15, enabled VM's in VM Manager in settings, then started my windows 8.1 VM. It basically worked fine, but my IR remote no longer works. I suspect it's not being passed thru correctly, but that's just a guess. I know things have changed with the new version and the new VM Manager, but I've been busy with other stuff to follow all the details. Hopefully there's something simple I can do to 'update' my VM to a fully working state again. Any pointers or suggestions are most welcome. More info needed on your IR remote. Usb connected? That's the only issue you are having?
May 4, 201511 yr I had a problem passing through my usb dac to a Windows 7 vm and changed to i440fx chipset. Then it was recognised.
May 4, 201511 yr Author Here is the XML; which worked fine on beta 14b... <domain type='kvm' id='2' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'> <name>Windows8_Passthru</name> <uuid>2e151e44-f801-4773-a6df-bfb01b0812fb</uuid> <description>Windows8 with Passthru</description> <memory unit='KiB'>4194304</memory> <currentMemory unit='KiB'>4194304</currentMemory> <memoryBacking> <nosharepages/> <locked/> </memoryBacking> <vcpu placement='static'>2</vcpu> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-q35-2.1'>hvm</type> <boot dev='hd'/> <bootmenu enable='no'/> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough'/> <clock offset='localtime'/> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>destroy</on_crash> <devices> <emulator>/usr/bin/qemu-system-x86_64</emulator> <disk type='file' device='disk'> <driver name='qemu' type='qcow2' cache='none' io='native'/> <source file='/mnt/cache/VM/Windows8.qcow2'/> <backingStore/> <target dev='vdc' bus='virtio'/> <alias name='virtio-disk2'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x03' function='0x0'/> </disk> <controller type='usb' index='0' model='ich9-ehci1'> <alias name='usb0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x01' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <alias name='usb0'/> <master startport='0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x01' function='0x0' multifunction='on'/> </controller> <controller type='usb' index='0' model='ich9-uhci2'> <alias name='usb0'/> <master startport='2'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x01' function='0x1'/> </controller> <controller type='usb' index='0' model='ich9-uhci3'> <alias name='usb0'/> <master startport='4'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x01' function='0x2'/> </controller> <controller type='sata' index='0'> <alias name='sata0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> <controller type='pci' index='0' model='pcie-root'> <alias name='pcie.0'/> </controller> <controller type='pci' index='1' model='dmi-to-pci-bridge'> <alias name='pci.1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x1e' function='0x0'/> </controller> <controller type='pci' index='2' model='pci-bridge'> <alias name='pci.2'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x01' function='0x0'/> </controller> <interface type='bridge'> <mac address='00:16:3e:c8:c8:c8'/> <source bridge='br0'/> <target dev='vnet0'/> <model type='virtio'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x02' function='0x0'/> </interface> <input type='tablet' bus='usb'> <alias name='input0'/> </input> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x050d'/> <product id='0x0201'/> <address bus='1' device='5'/> </source> <alias name='hostdev0'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x045e'/> <product id='0x0745'/> <address bus='1' device='9'/> </source> <alias name='hostdev1'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x0a12'/> <product id='0x0001'/> <address bus='1' device='8'/> </source> <alias name='hostdev2'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x147a'/> <product id='0xe03e'/> <address bus='1' device='7'/> </source> <alias name='hostdev3'/> </hostdev> <memballoon model='virtio'> <alias name='balloon0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x04' function='0x0'/> </memballoon> </devices> <seclabel type='none' model='none'/> <qemu:commandline> <qemu:arg value='-device'/> <qemu:arg value='ioh3420,bus=pcie.0,addr=1c.0,multifunction=on,port=1,chassis=1,id=root.1'/> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=01:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on'/> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=01:00.1,bus=pcie.0'/> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=07:00.0,bus=pcie.0'/> </qemu:commandline> </domain> Here is the USB devices list from Tools... Bus 006 Device 002: ID 8087:8001 Intel Corp. Bus 006 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 002: ID 045e:00db Microsoft Corp. Natural Ergonomic Keyboard 4000 V1.0 Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 002: ID 8087:8009 Intel Corp. Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 174c:3074 ASMedia Technology Inc. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 006: ID 051d:0002 American Power Conversion Uninterruptible Power Supply Bus 001 Device 025: ID 045e:0745 Microsoft Corp. Nano Transceiver v1.0 for Bluetooth Bus 001 Device 024: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) Bus 001 Device 026: ID 147a:e03e Formosa Industrial Computing, Inc. Infrared Receiver [iR605A/Q] Bus 001 Device 022: ID 050d:0201 Belkin Components Peripheral Switch Bus 001 Device 004: ID 174c:2074 ASMedia Technology Inc. Bus 001 Device 003: ID 13fe:3d00 Kingston Technology Company Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub The IR Remote is the Formosa device near the bottom. It appears to be the last device in my XML. I know there were big changes in this new beta, and I probably have to change some things, but I'm working LOTS of hours right now, and just can't keep up with unRAID like I used to I appreciate any help, as always.
May 4, 201511 yr Here is the XML; which worked fine on beta 14b... <domain type='kvm' id='2' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'> <name>Windows8_Passthru</name> <uuid>2e151e44-f801-4773-a6df-bfb01b0812fb</uuid> <description>Windows8 with Passthru</description> <memory unit='KiB'>4194304</memory> <currentMemory unit='KiB'>4194304</currentMemory> <memoryBacking> <nosharepages/> <locked/> </memoryBacking> <vcpu placement='static'>2</vcpu> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-q35-2.1'>hvm</type> <boot dev='hd'/> <bootmenu enable='no'/> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough'/> <clock offset='localtime'/> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>destroy</on_crash> <devices> <emulator>/usr/bin/qemu-system-x86_64</emulator> <disk type='file' device='disk'> <driver name='qemu' type='qcow2' cache='none' io='native'/> <source file='/mnt/cache/VM/Windows8.qcow2'/> <backingStore/> <target dev='vdc' bus='virtio'/> <alias name='virtio-disk2'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x03' function='0x0'/> </disk> <controller type='usb' index='0' model='ich9-ehci1'> <alias name='usb0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x01' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <alias name='usb0'/> <master startport='0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x01' function='0x0' multifunction='on'/> </controller> <controller type='usb' index='0' model='ich9-uhci2'> <alias name='usb0'/> <master startport='2'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x01' function='0x1'/> </controller> <controller type='usb' index='0' model='ich9-uhci3'> <alias name='usb0'/> <master startport='4'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x01' function='0x2'/> </controller> <controller type='sata' index='0'> <alias name='sata0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> <controller type='pci' index='0' model='pcie-root'> <alias name='pcie.0'/> </controller> <controller type='pci' index='1' model='dmi-to-pci-bridge'> <alias name='pci.1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x1e' function='0x0'/> </controller> <controller type='pci' index='2' model='pci-bridge'> <alias name='pci.2'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x01' function='0x0'/> </controller> <interface type='bridge'> <mac address='00:16:3e:c8:c8:c8'/> <source bridge='br0'/> <target dev='vnet0'/> <model type='virtio'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x02' function='0x0'/> </interface> <input type='tablet' bus='usb'> <alias name='input0'/> </input> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x050d'/> <product id='0x0201'/> <address bus='1' device='5'/> </source> <alias name='hostdev0'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x045e'/> <product id='0x0745'/> <address bus='1' device='9'/> </source> <alias name='hostdev1'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x0a12'/> <product id='0x0001'/> <address bus='1' device='8'/> </source> <alias name='hostdev2'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x147a'/> <product id='0xe03e'/> <address bus='1' device='7'/> </source> <alias name='hostdev3'/> </hostdev> <memballoon model='virtio'> <alias name='balloon0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x04' function='0x0'/> </memballoon> </devices> <seclabel type='none' model='none'/> <qemu:commandline> <qemu:arg value='-device'/> <qemu:arg value='ioh3420,bus=pcie.0,addr=1c.0,multifunction=on,port=1,chassis=1,id=root.1'/> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=01:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on'/> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=01:00.1,bus=pcie.0'/> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=07:00.0,bus=pcie.0'/> </qemu:commandline> </domain> Here is the USB devices list from Tools... Bus 006 Device 002: ID 8087:8001 Intel Corp. Bus 006 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 002: ID 045e:00db Microsoft Corp. Natural Ergonomic Keyboard 4000 V1.0 Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 002: ID 8087:8009 Intel Corp. Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 174c:3074 ASMedia Technology Inc. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 006: ID 051d:0002 American Power Conversion Uninterruptible Power Supply Bus 001 Device 025: ID 045e:0745 Microsoft Corp. Nano Transceiver v1.0 for Bluetooth Bus 001 Device 024: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) Bus 001 Device 026: ID 147a:e03e Formosa Industrial Computing, Inc. Infrared Receiver [iR605A/Q] Bus 001 Device 022: ID 050d:0201 Belkin Components Peripheral Switch Bus 001 Device 004: ID 174c:2074 ASMedia Technology Inc. Bus 001 Device 003: ID 13fe:3d00 Kingston Technology Company Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub The IR Remote is the Formosa device near the bottom. It appears to be the last device in my XML. I know there were big changes in this new beta, and I probably have to change some things, but I'm working LOTS of hours right now, and just can't keep up with unRAID like I used to I appreciate any help, as always. Change to i440fx. Q35 is really not needed anymore except for Linux based guests.
May 4, 201511 yr Author Thanks jonp. I've figured out how best to edit the VM, using the new plugin architecture. I see a couple of things I'm not sure about... I notice that I cannot select anything other then seaBIOS when editing my current VM. I think I saw I had to create a new VM to select UEFI BIOS. I wanted to ask about this before trying to change/fix/update too many things. Advice? I notice that when I changed my initial RAM down from 4GB to 2GB, it also changed the maximum down to 2GB simultaneously. I was able to change the max back to 4GB, but it seemed 'buggy' to change both values 'automatically' when changing the minimum. I also noticed that when I clicked in the box to select/point to my virtio drivers, then started typing /mnt/ it didn't auto-populate the box with possible path choices, like it does in other parts of the GUI. Maybe this can be 'fixed'. Finally, I thought I saw something about selecting a different bridge (other than br0), but can't find that post, nor remember why. Is this something I should do if/when I create a new VM to select UEFI BIOS? I'm updating the VM to change just the machine type right now and will test the IR in a minute, but wanted to ask about these other things while I was thinking about them. Thanks again for all your help.
May 5, 201511 yr Thanks jonp. I've figured out how best to edit the VM, using the new plugin architecture. I see a couple of things I'm not sure about... We'll get you squared away! I notice that I cannot select anything other then seaBIOS when editing my current VM. I think I saw I had to create a new VM to select UEFI BIOS. I wanted to ask about this before trying to change/fix/update too many things. Advice? It is not possible to convert an already-created SeaBIOS VM to OVMF (which uses UEFI). I notice that when I changed my initial RAM down from 4GB to 2GB, it also changed the maximum down to 2GB simultaneously. I was able to change the max back to 4GB, but it seemed 'buggy' to change both values 'automatically' when changing the minimum. This is a bug that is already resolved for the next release. If you lower max mem to less than min mem, it will auto lower min mem, but the fact that min mem automatically adjusts the max mem is the bug we fixed for the next build. I also noticed that when I clicked in the box to select/point to my virtio drivers, then started typing /mnt/ it didn't auto-populate the box with possible path choices, like it does in other parts of the GUI. Maybe this can be 'fixed'. I think your "auto-populate' may be a function of your browser, not the GUI itself, but would be happy to be proven wrong on this. Where in the webgui does auto-populate occur for you? Finally, I thought I saw something about selecting a different bridge (other than br0), but can't find that post, nor remember why. Is this something I should do if/when I create a new VM to select UEFI BIOS? This can be found under "advanced view". Note that by default, we have configured libvirt to create a bridge of "virbr0" that you can use, but you don't get the ability to give the VM a static IP, and this bridge uses a NAT method where libvirt acts as a DHCP server for the bridge as opposed to using your router. The general guideline right now is that if you wish to use your VM as a client and not a server, it is fine to use virbr0, but if you need to connect to the VM for services such as RDP, then you'll need to use the unRAID managed bridge under network settings. I'm updating the VM to change just the machine type right now and will test the IR in a minute, but wanted to ask about these other things while I was thinking about them. Thanks again for all your help. Let me know how the machine type change goes and if your device starts working better!
May 5, 201511 yr Author Okay, changing machine type seems to have worked, but I had to reboot the server to get the VM to start properly. Either way, IR is working now. I'm glad you already have that bug fixed; good work I can't find another example of the path auto-populating right now but I know it used to work, I think while setting up dockers, but when I just tested it, nothing auto-filled now, so I guess it's not working anymore. Maybe it can come back someday. I'll try to create a new VM pointing to the current image and see how that goes, although I'm not having any (other) issues at the moment. thanks again!
Archived
This topic is now archived and is closed to further replies.