erasmusfenris

Seriously appreciate the work and looking forward to testing this out in the new build. I had to drop hyper-threading in order to be able to run both gaming win10 vm's and avoid audio issues.

No i'm running an I7 5930k and having these issues. Keep in mind I am trying to run two win 10 gaming vm's both at the same time. It works now without HT enabled but the 4 core limit does not work when both are running at the same time. This is certainly a cpu pinning issue not confined to Xeon procs, lets put that to bed.

So I just disabled hyper-v and pinned cores 1-3 to vm win10 #1 and 4-6 to the other. Fixed audio issues... Certainly looks like CPU pinning and possibly frequency setting on the cores is the issue. I'm on unraid 6.2 beta 19. I would love to see LT fix this issue. I really like what they have done in 6.2 ( I can use my gaming mouse and NVME shows up!) but this has got to be keeping some people from effectively using Unraid to game on.

I've had similar issues with sound static and latency. I can't really pinpoint the issue and I have separate core assignments for the two Win 10 vm's. I have mostly resolved it by running both of the vm's audio through oboard audio and the other on a sound card. Also if I run them using display port I get audio issues even when I am directly connected via 3.5mm. I have disabled other audio devices inside windows in case display port passing audio is interfering somehow. I imagine that there is some resource related to audio that is trying to use the cpu and introducing latency. The usb audio WAS working at some point but then stopped, without me making any updates to unraid, settings, or anything else. I upgraded to 6.2 beta unraid but it did not change anything, though I like the build.

You did not exactly passthrough your PCI-device. You just mapped your block-device through a virtio disk-device to your vm. qemu/kvm does not need to know, that it is a disk you are passing throught, that just adds overhead that nvme is trying to remove. That way, you get pretty much native perfomance, because you remove any overhead, that qemu/kvm may add. Your VM would directly access the PCI device. But as I wrote you via pm, you would probably need to use OVMF (EFI) instead of SeaBIOS, because I don't know if SeaBIOS can boot from PCI/nvme. How would you go about making that modification to do the direct pass-through and still be able to boot from it?

This is great stuff and something I am planning on doing tonight to experiment with. Thanks to the both of you for outlining all this. If you have a sec can you outline how you used the mount point from nvme during the creation of the vm to host the os on? Also if you have any info on how to modify the GO command that would be appreciated. I didn't see reference to that and am super noobing it here. Edit: Figured out that the mnt point will show up in the unRAID gui console and allow you to select it as the "primary vdisk location." I'm sure this was obvious to many just not me until I started experimenting. Also the go command can be modified via the console (CLI). Go to the directory (remove any " from below commands) cd /boot/config type "vi go" From there hit the "~" key Move to the field you want to edit and hit "i" Type in the following on two separate lines "mkdir /mnt/nvme" "mount /dev/disk/by-uuid/2d5e7ce0-41e6-47b5-80d2-70df40a8c1da /mnt/nvme" Hit "Esc" key Then "wq!" Now you have the go file set to auto create and mount the drive on boot each time. Took me a bit to figure out and this is mostly to inform other noob fish.

Sure, here is the article http://kb.vmware.com/kb/2012007 It did fix it for me on both vm's with windows 10. One I did the MSI fix for and the other I did not, both were resolved by changing the default bit rate.

Having some issues getting a mouse to passthrough to my windows 10 vm. I have edited the XML to attempt to do the passthrough, perhaps you can review the file and let me know what the xml is missing. The mouse is a Gigabyte mouse and DOES show up as usb devices but it doesn't have a device name. Device shows up as - Bus 001 Device 012: ID e0ff:0002 The part of the XML that I added is the following <hostdev mode='subsystem' type='usb' managed='yes'> <source> <vendor id='0xe0ff'/> <product id='0x0002'/> <address bus='1' device='12'/> </source> </hostdev> This is the XML as it stands now. <domain type='kvm' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'> <name>Josh</name> <uuid>cda05c30-5a29-a411-5cac-160f41da1e5e</uuid> <description>Gaming PC</description> <metadata> <vmtemplate name="Custom" icon="windows.png" os="windows"/> </metadata> <memory unit='KiB'>6815744</memory> <currentMemory unit='KiB'>6815744</currentMemory> <memoryBacking> <nosharepages/> <locked/> </memoryBacking> <vcpu placement='static'>6</vcpu> <cputune> <vcpupin vcpu='0' cpuset='6'/> <vcpupin vcpu='1' cpuset='7'/> <vcpupin vcpu='2' cpuset='8'/> <vcpupin vcpu='3' cpuset='9'/> <vcpupin vcpu='4' cpuset='10'/> <vcpupin vcpu='5' cpuset='11'/> </cputune> <os> <type arch='x86_64' machine='pc-i440fx-2.3'>hvm</type> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough'> <topology sockets='1' cores='6' 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/user/vdisks/Josh/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='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/ArrayVDisk/Josh/vdisk2.img'/> <target dev='hdd' bus='virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/ISOs/win10pro.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/ISOs/virtio-win-0.1.112.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:65:d3:64'/> <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/Josh.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='usb' managed='yes'> <source> <vendor id='0x413c'/> <product id='0x2107'/> </source> </hostdev> <hostdev mode='subsystem' type='usb' managed='yes'> <source> <vendor id='0xe0ff'/> <product id='0x0002'/> <address bus='1' device='12'/> </source> </hostdev> <hostdev mode='subsystem' type='usb' managed='yes'> <source> <vendor id='0x0461'/> <product id='0x4d22'/> </source> </hostdev> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </memballoon> </devices> <qemu:commandline> <qemu:arg value='-device'/> <qemu:arg value='ioh3420,bus=pci.0,addr=1c.0,multifunction=on,port=2,chassis=1,id=root.1'/> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=06:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on'/> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=00:1b.0,bus=root.1,addr=01.0'/> </qemu:commandline> </domain>

Just wanted to stop by and say that I was having audio static on my windows 10 VM's. After trying a bunch of fixes I eventually ran across an article from vmware that suggested turning up the bitrate on the audio device in question. TL:DR - Audio static can be resolved by increasing the bit rate. How to - 1. Right click audio in windows (bottom right) 2. Select "playback devices" 3. Select whatever your audio device is and right click to properties 4. Advanced tab increase the bitrate to atleast 16bit, 48000 Hz Windows 10 X99-UD3P I7-5820E DDR4-3000 Unraid 6 Note - First time posting so if this is in the wrong area or largely irrelevant let me know.