Jump to content

ronni3

Members
  • Content Count

    99
  • Joined

  • Last visited

Community Reputation

1 Neutral

About ronni3

  • Rank
    Advanced Member

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

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

  1. No. Not necessarily. I have a mix of devices and also I share my library with family and they have a tendency to use whatever flavor box/tv that supports Plex, hence the need for the P2000 card for transcoding. Also I find the P2000 helps tremendously with transcoding the UHD/4K media I have and that continues to grow in selection. If all I was dealing with was 720p/1080p media then yes I could possibly just tell my family to upgrade to a slightly better device, but for them to be able to support 4K they would need to be on my network and 4K conversions need a dedicated GPU to assist with that workload versus offloading to a few cores on the CPU.
  2. So I purchased a Threadripper 3970x and I am almost ready to start building this monster machine. It is replacing two machines. One is my dedicated Unraid workhorse that houses a 7980xe with an Nvidia Quadro P2000. The Quadro is used for transcoding. It has 9 drives with 25 Tb of usable space and 32 Gb of RAM. I use my Unraid server for my media, virtualization labs (building Microsoft domains for testing) and I heavily utilize Eve-NG and GNS3. For the most part the space is used to hold my media. The other machine is my daily, everyday machine that is used for gaming and all other things. It is a first-gen 1920x Threadripper, has 32 Gb RAM, two Samsung NVME drives as the main drives and a Nvidia 2080 TI GPU. My plan is to consolidate the nine drives and two graphic cards into the new build with 64 Gb RAM and two new larger NVME drives. My issue is not knowing which direction to go and whether or not to re-install my Unraid build within ESXi or to make Unraid my base OS. Since I already have VM's running within Unraid I am leaning in that direction, but I know how VMware works and the ease of deploying on that hypervisor. My only concern is that passthrough of my GPU's will not work quite as well within ESXi versus Unraid. I want to make sure I don't have a huge impact on my gaming situation, however lite I game, I still want to be able to do that. What has your experience been with GPU Passthrough in ESXi and how has that impacted gaming? I'd also need to passthrough the P2000 into Unraid for transcoding which means I'd need one additional GPU for ESXi.
  3. @jcloud Hey I appreciate you looking out for any other ways to help me out. I tried that and it didn't work for me. I sold some 'coins' and went 'full-retard' (Tropic Thunder quote) and splurged on a Intel i9-7980x using another MSI board and I can confirm I am in working order now, but I now have a Threadripper and board I no longer need. I'm sure everyone will think purchasing this processor is overkill but I work in IT and want to build a number of VM's for testing Domain-related and network policy changes so the additional horsepower works for me. Know anyone that wants a Threadripper?
  4. After reading several threads I was well aware that this needed to be off but I thank you for bringing it up. The issue could very well be with this particular board. Most others seem to have the Asus or Asrock boards. Maybe this one has its set of problems???
  5. It's a very beautiful quote. lol Oh well, back to the drawing board. One or two more questions before I lose you... I know I could virtualize Unraid by using Vmware ESXi. Would virtualizing Windows 10 in VMware work better and would I still be able to pass through my graphics card if I went that route? Would things work better or worse if I did that?
  6. Okay so after taking a quick look... seems I've always chose the first option (default) which is the text boot. I just tried kicking off GUI mode and I've definitely never used that option before.
  7. I understand the question now. I usually always boot in GUI mode. Not sure I've ever tried any of the other methods. I will give the others a shot right now and see if that makes any difference. Wasn't really aware it mattered if you booted any other way, but definitely worth trying out.
  8. Actually let me clarify one additional thing. The only time the VM will boot is if I have VNC enabled as the first video card. I can have the GTX1060 attached or not as a second card. Otherwise the VM freezes and will never boot.
  9. I assume by GUI-boot, you mean the standard way Windows boots. If so, then yes, I am booting in GUI-boot. Unsure exactly what text-boot is. So far I've tried moving the video card (Asus model Dual-GTX1060-O6G) from the PCIe 1 slot to PCIe 4 & 5 with no difference. I have two Intel SAS cards that I've alternated between different slots as I've moved the video card. Still no difference. I then attempted to use Space Invader One's recommended Rom File fix and so far I've had no luck using two different Rom dumps. Then I tried the Rom Dump alongside the suggestion above from Rhynri and that actually shows that it is failing in the log. Here's what I get when I add the above QEMU and Domain change. This happens with that XML change with and without adding the Rom file. 2018-03-03 01:51:17.366+0000: starting up libvirt version: 4.0.0, qemu version: 2.11.1, hostname: CheshireCat LC_ALL=C PATH=/bin:/sbin:/usr/bin:/usr/sbin HOME=/ QEMU_AUDIO_DRV=none /usr/local/sbin/qemu -name 'guest=Windows 10,debug-threads=on' -S -object 'secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-14-Windows 10/master-key.aes' -machine pc-i440fx-2.11,accel=kvm,usb=off,dump-guest-core=off,mem-merge=off -cpu host -drive file=/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd,if=pflash,format=raw,unit=0,readonly=on -drive file=/etc/libvirt/qemu/nvram/ea3a2052-7f49-4c54-ff5a-9ad2c5ac2a91_VARS-pure-efi.fd,if=pflash,format=raw,unit=1 -m 4096 -realtime mlock=off -smp 2,sockets=1,cores=2,threads=1 -uuid ea3a2052-7f49-4c54-ff5a-9ad2c5ac2a91 -display none -no-user-config -nodefaults -chardev 'socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-14-Windows 10/monitor.sock,server,nowait' -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime,driftfix=slew -global kvm-pit.lost_tick_policy=delay -no-hpet -no-shutdown -boot strict=on -device nec-usb-xhci,iver,nowait' -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 -device vfio-pci,host=41:00.0,id=hostdev0,bus=pci.0,addr=0x5,romfile=/mnt/user/domains/Asus.GTX1060.6144.160706.modified.dump -device vfio-pci,host=41:00.1,id=hostdev1,bus=pci.0,addr=0x6 -device usb-host,hostbus=5,hostaddr=2,id=hostdev2,bus=usb.0,port=1 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x8 -cpu host,hv_time,kvm=off,hv_vendor_id=null -msg timestamp=on 2018-03-03 01:51:17.366+0000: Domain id=14 is tainted: high-privileges 2018-03-03 01:51:17.366+0000: Domain id=14 is tainted: custom-argv 2018-03-03 01:51:17.366+0000: Domain id=14 is tainted: host-cpu 2018-03-03T01:51:17.409748Z qemu-system-x86_64: -chardev pty,id=charserial0: char device redirected to /dev/pts/0 (label charserial0) I've even tried changing the CPU Mode from passthrough to QEMU and testing everything above again with no luck. Only way it boots if I leave XML untouched but then I am still where I left off with the card in Device Manager reading Code 43. It recognizes the card but it is unable to link to any drivers and no output to a monitor via any of the display ports. Any other suggestions?
  10. Would this processor have similar issues like Threadripper with passthrough?
  11. All equipment works. This is a bundle sale. Take all for $950. MSI X399 Gaming Pro Carbon AC motherboard https://us.msi.com/Motherboard/X399-GAMING-PRO-CARBON-AC AMD Ryzen Threadripper 1920x processor with 12 cores/28 threads. Noctua NH-U9 TR4-SP3 premium-grade 92mm CPU cooler for AMD TR4/SP3 included I am located in the United States so this sale will be limited to the lower 48 US only. Free shipping via UPS Ground. I will accept payment via Venmo, ChasePay, Paypal (Bank account only).
  12. I added both just as you mentioned and I am still receiving the Code 43 error after I reboot the VM. Any other suggestions? I am on Unraid 6.4.1 currently. Latest BIOS on my board.
  13. Does this work on Threadripper? If so, how do you apply this? I am running a X399 GAMING PRO CARBON AC board with the 1920x processor. I am able to passthrough my GTX1060 but I get the Code 43 error and I am unable to apply any drivers or see output to any attached monitor. Please help I'd really love to get access to my VM.
  14. Hi @iJumbo - Wondering if you managed to get everything working? I am running Threadripper on a X399 board and I can see my GTX 1060 but if I attempt to install drivers the VM restarts and GPU is still not linked to drivers correctly. Is your system still working fine?
  15. Recently upgraded and immediately noticed several errors in logs that eventually lead to the log directory filling up with Unraid eventually freezing up altogether. Before that happens all seems to be running extremely well. Here's my build: AMD Ryzen Threadripper 1920x 32GB RAM MSI X399 GAMING PRO CARBON AC 2x Intel SAS Raid Controller Cards NVIDIA GTX 1060 Errors that are causing the system to freeze up eventually: ErrorWarningSystemArrayLogin Jan 19 19:22:29 CheshireCat kernel: pcieport 0000:00:01.3: [ 8] RELAY_NUM Rollover Jan 19 19:22:29 CheshireCat kernel: pcieport 0000:00:01.3: [12] Replay Timer Timeout Jan 19 19:22:29 CheshireCat kernel: mpt3sas 0000:0a:00.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=0a00(Transmitter ID) Jan 19 19:22:29 CheshireCat kernel: mpt3sas 0000:0a:00.0: device [1000:0072] error status/mask=00001100/00002000 Jan 19 19:22:29 CheshireCat kernel: mpt3sas 0000:0a:00.0: [ 8] RELAY_NUM Rollover Jan 19 19:22:29 CheshireCat kernel: mpt3sas 0000:0a:00.0: [12] Replay Timer Timeout Jan 19 19:22:29 CheshireCat kernel: pcieport 0000:00:01.3: AER: Multiple Corrected error received: id=0000 Jan 19 19:22:29 CheshireCat kernel: mpt3sas 0000:0a:00.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=0a00(Transmitter ID) Jan 19 19:22:29 CheshireCat kernel: mpt3sas 0000:0a:00.0: device [1000:0072] error status/mask=00001000/00002000 Jan 19 19:22:29 CheshireCat kernel: mpt3sas 0000:0a:00.0: [12] Replay Timer Timeout Jan 19 19:22:29 CheshireCat kernel: pcieport 0000:00:01.3: AER: Multiple Corrected error received: id=0000 Jan 19 19:22:29 CheshireCat kernel: pcieport 0000:00:01.3: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=000b(Transmitter ID) Jan 19 19:22:29 CheshireCat kernel: pcieport 0000:00:01.3: device [1022:1453] error status/mask=00001000/00006000 Jan 19 19:22:29 CheshireCat kernel: pcieport 0000:00:01.3: [12] Replay Timer Timeout Jan 19 19:22:29 CheshireCat kernel: pcieport 0000:00:01.3: AER: Corrected error received: id=0000 Jan 19 19:22:29 CheshireCat kernel: pcieport 0000:00:01.3: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=000b(Receiver ID) Jan 19 19:22:29 CheshireCat kernel: pcieport 0000:00:01.3: device [1022:1453] error status/mask=00000080/00006000 Jan 19 19:22:29 CheshireCat kernel: pcieport 0000:00:01.3: [ 7] Bad DLLP Jan 19 19:22:39 CheshireCat kernel: pcieport 0000:00:01.3: AER: Multiple Corrected error received: id=0000 Jan 19 19:22:39 CheshireCat kernel: pcieport 0000:00:01.3: can't find device of ID0000 Anyone know what these are? Things worked fine while I ran under v.6.3.5. cheshirecat-diagnostics-20180119-1916.zip