Jump to content

effingheck

Members
  • Content Count

    18
  • Joined

  • Last visited

Community Reputation

0 Neutral

About effingheck

  • Rank
    Member

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Thanks 1812 - must have missed that incremental update! I'll update and check again then report back to the release thread. Cheers.
  2. Hi all, So I think there is an issue with Windows 10 VM's and unRAID 6.3.1. My vm was working completely fine, booting up and restarting etc without issue. Upgrade to v6.3.1 and now I find the whole unRAID system hangs and i have to do a hard reset of my server when booting up the VM. I can recreate this on demand and it generally works like this: Boot up VM - all ok Shutdown VM Boot up VM - Crashes unRAID Hard Reset - Start Array - Dockers etc. Boot up VM - all ok Shutdown VM - Boot up VM - Crashes unRAID etc. etc. To further add to this, a colleague also upgraded to v6.3.1 and mentioned his VM's are also crashing unRAID and requires a hard reset. There certainly seems to be a correlation between this new update and system crashes as I can see other threads reporting similar issues. I've attached diagnostics - I'm happy to go through any troubleshooting steps! Many Thanks tower-diagnostics-20170221-0846.zip
  3. Hi all, So i'm almost at the point where everything is working on my windows 10 VM. My last stumbling block has been the oculus rift. I'm using one of the recommended pci-e cards here: https://www.amazon.co.uk/gp/product/B00FPIMJEW/ref=oh_aui_detailpage_o07_s00?ie=UTF8&psc=1 The card is passed through to the VM directly. The sensors/rift show as connected to usb 3.0 - no errors on the initial setup. I can then use the rift for about five minutes before everything on the card drops including my keyboard/mouse (no tracking on controllers, kb+mouse stop responding). I also get windows errors showing "a usb device not recognised" so it seems that the whole card is just giving up completely for some reason. Pretty sure this is a passthrough issue rather than a faulty card as it was working on baremetal previously. Any ideas what could be causing this or any tips on troubleshooting? Can't seem to find any clues in the logs but maybe someone else with a bit more experience can spot something! I've attached diagnostics. Cheers
  4. I think I found it in the unraid wiki somewhere? Can't seem to locate it now. Not exactly sure what it does but it doesn't seem to have effected the operation of my VM, I assume it would make a difference on bare metal in boot up times but how much I'm not sure.. Glad you got it resolved (it bugged me for ages too!)
  5. This exact issue was happening to me. Fixed it by doing the following: Type Control Panel in the search box. Click Control Panel. Click Power Options. Click Choose what the power buttons do. Click Change settings that are currently unavailable. Scroll down to Shutdown settings and uncheck Turn on fast startup. Click Save changes. Give that a go and try again.
  6. Ok so an update on where I am currently: Suggestion from Squid - Installed cAdvisor but have no idea how to use it. Checked support thread but nothing was there I could see. Any link to instructions? Suggestions from Darkun - MSI/HDMI issue probably isn't relevant as I'm passing through a seperate sound card and using DVI output on the GPU Suggestions by 1812 - Changing core allocation to 8-15 and adjusting topology to reflect using physical cores and no HT made performance worse and maxed out CPU usage on simple tasks so reverted back. I've also pinned every docker to cores not being used by my VM so my CPU core allocation is as follows: cpu 0 / 16 - Emulator Pin / Unraid cpu 1 / 17 - Unraid cpu 2 / 18 - All dockers cpu 3 / 19 - All dockers cpu 4 / 20 - All dockers cpu 5 / 21 - All dockers cpu 6 / 22 - All dockers cpu 7 / 23 - All dockers cpu 8 / 24 - All dockers cpu 9 / 25 - All dockers cpu 10 / 26 - All dockers cpu 11 / 27 - All dockers cpu 12 / 28 - Win10VM cpu 13 / 29 - Win10VM cpu 14 / 30 - Win10VM cpu 15 / 31 - Win10VM And also of course added isolcpus=12-15,28-31 to syslinux file. Now the main two problem behaviours I'm still seeing: Youtube lipsync goes way out around 2-3 minutes into any video Games run at a stable 60+FPS BUT as soon as any transcoding occurs, I experience immediate performance issues and FPS impact (can drop to 40/stall/lag etc). Now this absolutely shouldn't be happening since I've isolated cores 12-15 and 28-31. Also dockers shouldn't be interfering with the emulator pin as they're all set to --cpuset-cpus=2-11,18-27. Also completely rebuilt VM from scratch to eliminate OS issue. Also tried both versions of virtio drivers (1.2.6/1.3.0) and installed QEMU agent. So unfortunately not made any progress really...if someone could guide me in the right direction to see why dockers/unraid processes are interfering with the VM vcpu's that would be great! cadvisor I guess could help but again, not sure how to use it! Thanks!
  7. I managed to solve a very similar issue just now (see thread: https://lime-technology.com/forum/index.php?topic=55715.0) Try: In Windows... Type Control Panel in the search box. Click Control Panel. Click Power Options. Click Choose what the power buttons do. Click Change settings that are currently unavailable. Scroll down to Shutdown settings and uncheck Turn on fast startup. Click Save changes.
  8. Finally managed to at least solve this issue! Instructions below for anyone else having the issue that might stumble on this thread: Type Control Panel in the search box. Click Control Panel. Click Power Options. Click Choose what the power buttons do. Click Change settings that are currently unavailable. Scroll down to Shutdown settings and uncheck Turn on fast startup. Click Save changes.
  9. Tried installing that msi but didn't make a difference. managed to find the PID that is apparently responsible though (noticed it lists them in Tools -> processes.. root 6043 1 0 11:27 ? 00:00:00 /usr/sbin/libvirtd -d -l -f /etc/libvirt/libvirtd.conf -p /var/run/libvirt/libvirtd.pid Not sure if that helps narrow down the issue though!
  10. Thanks 1812, I'll try it without the HT pairs and see if that makes any difference.
  11. See below my VM XML in full: <domain type='kvm' id='2'> <name>Windows 10</name> <uuid>4b6733a6-c5f8-50b1-416e-2844a5019f17</uuid> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/> </metadata> <memory unit='KiB'>16777216</memory> <currentMemory unit='KiB'>16777216</currentMemory> <memoryBacking> <nosharepages/> <locked/> </memoryBacking> <vcpu placement='static'>8</vcpu> <cputune> <vcpupin vcpu='0' cpuset='12'/> <vcpupin vcpu='1' cpuset='13'/> <vcpupin vcpu='2' cpuset='14'/> <vcpupin vcpu='3' cpuset='15'/> <vcpupin vcpu='4' cpuset='28'/> <vcpupin vcpu='5' cpuset='29'/> <vcpupin vcpu='6' cpuset='30'/> <vcpupin vcpu='7' cpuset='31'/> <emulatorpin cpuset='0,16'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-i440fx-2.5'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/4b6733a6-c5f8-50b1-416e-2844a5019f17_VARS-pure-efi.fd</nvram> </os> <features> <acpi/> <apic/> <hyperv> <relaxed state='on'/> <vapic state='on'/> <spinlocks state='on' retries='8191'/> <vendor id='none'/> </hyperv> </features> <cpu mode='host-passthrough'> <topology sockets='1' cores='4' threads='2'/> </cpu> <clock offset='localtime'> <timer name='hypervclock' present='yes'/> <timer name='hpet' present='no'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/local/sbin/qemu</emulator> <disk type='block' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source dev='/dev/disk/by-id/ata-Samsung_SSD_850_EVO_250GB_S21PNXAG664859P'/> <backingStore/> <target dev='hdc' bus='sata'/> <boot order='1'/> <alias name='sata0-0-2'/> <address type='drive' controller='0' bus='0' target='0' unit='2'/> </disk> <controller type='usb' index='0' model='nec-xhci'> <alias name='usb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/> </controller> <controller type='pci' index='0' model='pci-root'> <alias name='pci.0'/> </controller> <controller type='sata' index='0'> <alias name='sata0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </controller> <controller type='virtio-serial' index='0'> <alias name='virtio-serial0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:17:3a:15'/> <source bridge='br0'/> <target dev='vnet0'/> <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/0'/> <target port='0'/> <alias name='serial0'/> </serial> <console type='pty' tty='/dev/pts/0'> <source path='/dev/pts/0'/> <target type='serial' port='0'/> <alias name='serial0'/> </console> <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/domain-Windows 10/org.qemu.guest_agent.0'/> <target type='virtio' name='org.qemu.guest_agent.0' state='disconnected'/> <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='0x04' slot='0x00' function='0x0'/> </source> <alias name='hostdev0'/> <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='0x02' slot='0x00' function='0x0'/> </source> <alias name='hostdev1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x81' slot='0x00' function='0x0'/> </source> <alias name='hostdev2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/> </hostdev> <memballoon model='virtio'> <alias name='balloon0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x09' function='0x0'/> </memballoon> </devices> </domain> And also see below CPU usage with PC on and three transcodes running in tandem. I feel like it should be using way less processing power considering these are 2x Xeon e5-2670's... Thanks in advance!
  12. Thanks Darkun, Sure see below my CPU summary while my VM is off...
  13. Hi all, So I've been trying really hard to get my main gaming VM running in tandem with my plex docker/transcoder but I'm getting stuck. Some info on the configuration: SysLinux Config added this line: isolcpus=12-15,28-31 VM XML added this: <vcpupin vcpu='0' cpuset='12'/> <vcpupin vcpu='1' cpuset='13'/> <vcpupin vcpu='2' cpuset='14'/> <vcpupin vcpu='3' cpuset='15'/> <vcpupin vcpu='4' cpuset='28'/> <vcpupin vcpu='5' cpuset='29'/> <vcpupin vcpu='6' cpuset='30'/> <vcpupin vcpu='7' cpuset='31'/> <emulatorpin cpuset='0,16'/> Plex Docker is left at defaults so it uses all other cores available. Now when there are plex transcodes occuring, I immediately see FPS drops/lag on the VM. As soon as I stop the transcodes, solid 70FPS and VM is working beautifully.** **EDIT: Actually - not working perfectly. Noticing lipsync issues when watching youtube videos so something isn't right... Thought this might be down to Plex using the cores the emulator pin is using so set Plex docker extra parameter: --cpuset-cpus=1-11,17-27 This made no difference. As soon as there's any transcoding activity, my VM is affected. Any ideas what I'm doing wrong? I'll also attach the diagnostics output. tower-diagnostics-20170121-1521.zip
  14. Thanks for the advise. Tried both suggestions: 1. Changed machine type from i440 v2.5 down to 2.4/2.3/2.2 - no change 2. BIOS already set to gen2 pci-e but changed to gen3 in case that helped - no change Also checked BIOS firmware was up to date. Issue still persists...
  15. Anyone have any ideas with this one? It's definitely this line I need to figure out: 2017-01-17T19:35:01.037192Z qemu-system-x86_64: terminating on signal 15 from pid 5730 How do I find out what pid 5730 is?