space

Members
  • Posts

    45
  • Joined

  • Last visited

Everything posted by space

  1. I'm having the same problem. 1 of 5 times I boot my win10 VM (passthrough USB and GPU) the server locks up, and my only option is the power button. Booting during automatic updates MAY be the problem I have, when I find my server in a locked state every now and then. I will try to disable automatic updates (if that's possible now?).
  2. I have installed the latest drivers. I have seen many people having issues with focusrite and win10, on bare metal, so it very well can be the drivers combined with my hardware. I have now tried the following: -focusrite connected to a win10 laptop: No problem -edirol ua-25 connected to win10 laptop: No problem -focusrite connected to passed through usb3 on unraid: Stutter/glitch -edirol ua-25 connected to passed through usb3 on unraid: Stutter/glitch -focusrite connected to passed through usb2 on unraid: Stutter/glitch -edirol ua-25 connected to passed through usb2 on unraid: Stutter/glitch - Onboard Realtek ALC1150: No problem
  3. I've read something about disabling hyperthreading may solve some problems regarding latency. Is that done in BIOS? What performance gain/loss will that result in? Someone said 10% gain in using hyperthreading? Then I guess just 6 cpus will show up, instead of 12 in my system, and it makes pinning and assignment somewhat easier to manage.
  4. Could be. What happens if I pass through the focusrite directly from unraid, while it is connected to a USB controller that is also passed through? Will it crash? Must find my main board's manual. Where can it be?...
  5. I pass through the usb controller to the win10 VM. Maybe I pass through a USB3 controller, and the audio interface doesn't like it. I have to figure out what ports are usb2. (I suspect all are USB2/3 compatible). I have tried connecting it to different ports, all of them passed through. Main board is ASUS X99-A, Socket 2011-3 as stated in my first post. If I remember correctly, it has 2 USB controllers, and I passed through the one that the unraid usb stick is not attached to.
  6. I'm currently just running the win10 VM. My soundcard is the Focusrite Scarlett 2i4 USB interface. (I'm doing occasional home recording. Well, not at the moment... ) I will try the built in audiointerface now and report back. Edit: Now listening through headphones connected to the back of my computer: No issues with sound, what so ever. Soo... USB passthrough issue? Focusrite issue? I must find someone that as a different USB interface and try that to see if it fails too. Irritating!
  7. Ok. More testing done. I'm now running your recommended setup: Win 10 VM 4,5,10,11 isolated 4,5,10,11 emulator pin remaining cpus 0,1,2,3,6,7,8,9 and everything hooked in MSI_util Improvements in LatencyMon, no difference in audio... Even windows sound can't be played without glitches. LatencyMon and dpclat shows very few peaks now. Something like 1 pr. minute. But sound is bad as ever. Constant skipping/popping noise.
  8. Are you now meaning cpus, cores, or threads? It's not my fault Intel makes cpus with X number of cores. Wouldn't it be stupid not to use them? I've read that more than 4 cores can be trouble too. My current (stated in my above post) just uses 4 right? and 4 for emulatorpin. aah.. my head is spinning.
  9. Thanks dlandon! I will try this later tonight. (And I'll save my current XML as well. I need some custom coding to get my usb controller passed through.) And I'm also running dockers Plex Media Server and SABnzbd, so I guess I'll keep Ubuntu on one core (two threads) to be sure.
  10. Hmm, the cpu pairs are: 0,6 1,7 2,8 3,9 4,10 5,11 so, win10 is pinned to 4 "main" cores. 2 3 4 5 and emulatorpin to the corresponding pairs: 8, 9, 10, 11. I tried this after reading this advice in another thread here. 0,6,1,7 and 8,9,10,11 is not reserved by isolcpus. My other VM (ubuntu) I'm pinning to 1 with emulatorpin 7. This is then handled by unraid, that also has cores 0 and 6 for it's own use. I now run this setup with append isolcpus=2,3,4,5 I also used the MSI_tool to enable MSI on all lines mentioning graphics or audio. The result is much better than before. Some very few latency spikes. (I will test this better tonight) The above is at least what I THINK I'm accomplish by the settings mentioned.
  11. What about MSI? hook everything, just GFX, GFX + audio?
  12. Yes, I see it can be read two ways, and found out later what I stated was wrong. What about emulatorpin? If I'm doing this: <vcpu placement='static'>4</vcpu> <cputune> <vcpupin vcpu='0' cpuset='2'/> <vcpupin vcpu='1' cpuset='3'/> <vcpupin vcpu='2' cpuset='4'/> <vcpupin vcpu='3' cpuset='5'/> <emulatorpin cpuset='8-11'/> </cputune> ... <cpu mode='host-passthrough'> <topology sockets='1' cores='4' threads='1'/> </cpu> How am I setting up isolcpus? append isolcpus=2,3,4,5,8,9,10,11 or append isolcpus=2,3,4,5
  13. Reading forum posts ... I see something is misunderstood. isolcpus shoud point at the cpus that will be used exclusively by unrar, not the other way around. That means in my setup it should be append isolcpus=0,6 Ref jonp in this thread: https://lime-technology.com/forum/index.php?topic=45379.0 One other thing that isnot quite right is <emulatorpin cpuset='8,9,10,11'/> The emulatorpin setting should list the cpus that will take care of the VM overhead, and not be the pairing logical cpu, if I understand it correctly. I have tried lots of settings now, but I'm not there yet. The closest yet is the setup with only 4 cpus. well, off to reboot again.
  14. Yes. I will try more options tonight. I like to stick with XML-editing when I have added custom stuff. Like you say, the gui removes "random" settings. I'll just add <vcpupin vcpu='4' cpuset='6'/> <vcpupin vcpu='5' cpuset='7'/> <vcpupin vcpu='6' cpuset='8'/> <vcpupin vcpu='7' cpuset='9'/> This means I'm more or less back to my original XML, except <topology sockets='1' cores='4' threads='2'/> instead of <topology sockets='1' cores='8' threads='1'/> and starting unraid with the isolcpus setting. I read somewhere that the topoligysetting didn't matter much as long as the numbers multiplied equaled 8. (but I guess worth trying)
  15. It's just showing 4 graphs at the moment. Some more tweaking to do apparently... So append isolcpus=1-11 and <emulatorpin cpuset='8,9,10,11'/> while topology still <topology sockets='1' cores='4' threads='1'/> then?
  16. Looks like the latency issue is fixed. I have to use the machine a few more days to be shure, but it really sounds promising. No pops and skips so far, and it used to be quite bad. I am now running this config: [select] append isolcpus=1-5 win10: Cores 2, 3, 4 and 5 / <topology sockets='1' cores='4' threads='2'/> xubuntu: Cores 1 / <topology sockets='1' cores='1' threads='1'/> The task manager in win10 shows: sockets: 1 Virtual processors: 4 Is it somewhere I can check the hyperthread status, to see if it runs 8 threads? Interresting:
  17. D'Oh! Of course you're right... I will edit, and get back with a status report later tonight! Sometimes it takes someone from the outside to state the obvious. Thanks!
  18. Well, I already got win10: <cpu mode='host-passthrough'> <topology sockets='1' cores='8' threads='1'/> </cpu> xubuntu: <cpu mode='host-passthrough'> <topology sockets='1' cores='2' threads='1'/> </cpu> So I guess step 1 and 2 would be: 1. add „append isolcpus=3-12“ to the boot parameters 2. leave the core setup as today. (win10: 2-9 and xubuntu: 10-11) 3. leave topology as today. Correct? Or is it some hidden point in using fewer cores? This thread mentions: "I just made the change to enable MSI interrupts in Windows for this GPU thinking this may solve my issue" and that seemed to work. I will dig into that later... https://lime-technology.com/forum/index.php?topic=42828.0
  19. 1. win10: 8GB ram xubuntu: 2GB ram 2. win10: cores 2,3,4,5,6,7,8,9 xubuntu: cores 10, 11 3. Not sure what you mean? 4. I have no issues using the built in audio interface of the main board. (I think....) Gaming also seems to be no problem. It's just windows sounds, music, videos and such. VM XML: <domain type='kvm' id='2' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'> <name>Windows 10 virtual desktop</name> <uuid>99407073-5e6b-c02b-be14-9c02ff5523e7</uuid> <description>windows 10 lokal</description> <metadata> <vmtemplate name="Custom" icon="windows.png" os="windows"/> </metadata> <memory unit='KiB'>8388608</memory> <currentMemory unit='KiB'>8388608</currentMemory> <memoryBacking> <nosharepages/> <locked/> </memoryBacking> <vcpu placement='static'>8</vcpu> <cputune> <vcpupin vcpu='0' cpuset='2'/> <vcpupin vcpu='1' cpuset='3'/> <vcpupin vcpu='2' cpuset='4'/> <vcpupin vcpu='3' cpuset='5'/> <vcpupin vcpu='4' cpuset='6'/> <vcpupin vcpu='5' cpuset='7'/> <vcpupin vcpu='6' cpuset='8'/> <vcpupin vcpu='7' cpuset='9'/> </cputune> <resource> <partition>/machine</partition> </resource> <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='8' 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/Windows 10 virtual desktop/vdisk1.img'/> <backingStore/> <target dev='hda' bus='virtio'/> <boot order='1'/> <alias name='virtio-disk0'/> <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/vdisks2/Windows 10 virtual desktop/vdisk2.img'/> <backingStore/> <target dev='hdc' bus='virtio'/> <alias name='virtio-disk2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </disk> <controller type='usb' index='0'> <alias name='usb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/> </controller> <controller type='pci' index='0' model='pci-root'> <alias name='pci.0'/> </controller> <controller type='virtio-serial' index='0'> <alias name='virtio-serial0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:4a:6b:f1'/> <source bridge='br0'/> <target dev='vnet1'/> <model type='virtio'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </interface> <serial type='pty'> <source path='/dev/pts/1'/> <target port='0'/> <alias name='serial0'/> </serial> <console type='pty' tty='/dev/pts/1'> <source path='/dev/pts/1'/> <target type='serial' port='0'/> <alias name='serial0'/> </console> <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/Windows 10 virtual desktop.org.qemu.guest_agent.0'/> <target type='virtio' name='org.qemu.guest_agent.0' state='connected'/> <alias name='channel0'/> <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='0x00' slot='0x14' function='0x0'/> </source> <alias name='hostdev0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/> </hostdev> <memballoon model='virtio'> <alias name='balloon0'/> <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=03: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>
  20. I have several problems with my unraid server OR kvm. I will try to describe and mention some possible solutions. All problems may be connected, but I will list them seperately. Hardware: Intel Core i7-5820K, Socket-LGA2011-3 ASUS X99-A, Socket 2011-3 ASUS DC2 OC NVIDIA GeForce GTX 970 4GB Crucial Ballistix Sport 16GB 2400MHz DDR4 DIMM 288-pin Unraid 6.1.9. Running win10 and xubuntu in kvm. Win10 with usb and GPU passthrough. xubuntu as a straight vm. 1. The server stops responding after a few days, or 2 weeks, or anything between. When this happens it also seems to spam my network, so all other machines and mobiles are getting poor speed. I have not been able to see anything in the logs. I suspect the win10 vm to be the problem. 2. win10 vm restart (from within win10) can bring the whole server down. This happened to me twice yesterday, as I was trying to install ond uninstall some audio drivers. I was not able to contact the unraid.local from my laptops browser. (This might be the reason the server dies from time to time. Like windows update booting the system and the server dies all together) 3. win10 audio latency trouble. pops and skips.This is entering a world of pain it seems. The web is flooded with these problems, and it seems to happen for all types of reasons. (On a general. Not related to unraid) This is where I have put in most of my effort, and maybe found a solution. I have a focusrite 2i4 usb soundcard. Problem: Pops and skips while playback from spotify, youtube videos etc. While playback for a longer period it suddenly gets worse (10 second soundclip takes 20-30 seconds to playback. Like playing back with a jog wheel), to the point of videos not playing, and spotify halting. Yesterday I discovered the program "latencymon", and lots of people blaming network drivers as the cause of this. Latencymon showed spikes of latency during playback. Today I connected to win10 using teamviewer, and run latencymon again. Now it whent through the roof with reported latency. AHA! So under mayor network load the problem gets much worse? That gives me reason to belive the network drivers are the issue here as well. As my system runs on unraid, with virtual network, I guess it's not that simple to swap out the network driver? If I buy a usb network adapter, will I get this working in my win10 vm? Using the integrated network card for unraid server, and no network passthrough to the vm. Just the usb device, with native drivers, set up in my vm. I understand this will affect speed between host and vm (if it's possible to get working), but I can live with that if it makes my other trouble go away. Am I the only one having these issues? Other ideas are welcome!