Jump to content

TType85

Members
  • Content Count

    48
  • Joined

  • Last visited

Community Reputation

5 Neutral

About TType85

  • Rank
    Advanced Member

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

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

  1. TType85

    Win10 don´t use gpu

    Are you up to date on the windows 10 updates? The GPU in task manager was added in the last big update I think.
  2. TType85

    Win10 don´t use gpu

    I don't think RDP uses the graphics card in windows to display, it uses it's own driver. If you use something like teamviewer it will use the GPU but there still is latency.
  3. SeaBIOS vs OVMF: I think SeaBIOS is used for older OS that do not support UEFI and does not play as well with video card passthrough. I440fx vs Q35: i440fx is a older, more supported hardware profile for windows, Q35 is a newer one that works best in Linux (and osx). Your code 43 issue is because Nvidia does not want you to pass your video card to a VM. I think KVM can hidethe HyperV flag so that the video card does not see it and it works. FWIW: I have 2 Windows 10 VM's running as i440fx/OVMF with Nvidia GTX 1060 & 1070 cards passed through along with a usb card and nvme ssd with no issue. I also have a OSX VM that is Q35/OVMF with the GTX 1070 passed to it along with the USB card and it works well also.
  4. TType85

    Toss KVM, and move to a VirtualBox solution

    I wouldn't call it a toy. I am using it as a NAS, plex server, home automation server, music server, RDP gateway, downloader, network controller & vm host it also backs up to another unraid box that is my failover for all but the VM's. Personally I wouldn't use Unraid in a business production environment this way but for home "production" use it's great. Virtualbox is a toy to me, I have never and would not use it in production, I have used ESXi & Hyper-V in production and they shine there.
  5. TType85

    Toss KVM, and move to a VirtualBox solution

    I am not sure what mental anguish you have had but I have had very little problems with KVM/libvirt. I think they used a VirtualBox plugin before going over to libvirt. Most of my issues I have had are either self inflicted or are issues with Unraid overwriting XML settings. How well does VirtualBox do passthrough of hardware like video cards and usb controllers? I currently have 2 daily driver systems running on my Unraid box with video cards, nvme drives and usb ports passed through. The only issues I have had is odd benchmarks with CPUz. Other than that they both run great. You can't tell you are on a VM.
  6. The windows 10 image I used to test is only a few weeks old, fully updated. I actually have very little installed. The scores from when it was a fully fresh install are around the same as they are now. CPUz is the odd one. I was able to get to 400 single core before but mostly it has been between 350 and 375 with no consistency. There were times it dipped as low as 320 but I attributed that to background processes. I did notice that about CB. CPUz stays on one core. We will see how WoW is, It will put 1 core at 95-99% all the time..
  7. I'll take a look at the MSI fix again, I am running sound on a usb adapter so I never get oddities there. I just did a CPUz bench on the w8.1 that is a full 75pts higher than the win 10 machine. I re-ran Cinebench and got 1707/164 in back to back runs.
  8. I am running at 4.1 Ghz on a Noctua cooler on my 1950x and am seeing lower CPU-z scores too. I was close to 400, now 340-350. My temps are good, 32-33c idle and I haven't seen load temps over 63c with all cores cranking away. I have had a few stutters, mainly when I have youtube open while playing World of Warcraft but they last a few seconds and are gone. Check your setup with Cinebench R15. My daily driver is 8c/16t (half the cpu, cinebench doesnt read it right). Single core @4.1ghz under KVM is slightly faster than bare metal at 3.4 boosting to 4.1. The 1661 multi core falls in line with the 3300-3400 i've seen for bare metal. Edit: Just set up a windows 8.1 VM, using the same cores as the windows 10 (w10 machine off) and I get a slightly better cinebench score. I am going to pass the gfx card through and test WoW tonight.
  9. If you are getting the UEFI shell when trying to boot a windows 10 iso you may just not be seeing the prompt to hit a key to boot from CD/DVD. It is a pain to start a VM then launch VNC in time to see it.
  10. TType85

    UA on Windows 10 VM

    passthrough is going to give you native speeds. I am not sure how big of a difference there is using a vdisk. For a while I had battle.net games on a vdisk on a UA ssd and I didn't notice any extra load times or issues. The advantage to using a vdisk is you don't have to dedicate the whole drive to the one VM.
  11. TType85

    UA on Windows 10 VM

    You can create a disk image on the UA device and attach it to the VM or pass the whole disk via /dev/disk/by-id/nvme-xxxxxxxxx (passing the nvme this way may have issues, I haven't had any but others have). You could also blacklist the NVME and use VFIO passthrough (this is how I am doing it).
  12. Maybe try VMware ESXi and set up passthrough and see what it does? Other than that, it seems that a virtualized setup isn't quite where you need it yet. I know a year or so ago it wasn't for me since my main gaming is WoW, which is very single core speed bound. All of the high core count chips were to slow to have the frame rates I wanted. The 1950x does the job pretty well.
  13. Only had a minute to test before heading to dinner, set it to max, 2560x1440 20-09-2018, 16:50:45 HeroesOfTheStorm_x64.exe benchmark completed, 12534 frames rendered in 93.906 s Average framerate : 133.4 FPS Minimum framerate : 114.2 FPS Maximum framerate : 153.2 FPS 1% low framerate : 70.2 FPS 0.1% low framerate : 21.2 FPS Will try 5 min later. CPU usage is maxing on one core mostly, just like World Of Warcraft.
  14. Here is mine Socket 1 ID = 0 Number of cores 1 (max 1) Number of threads 8 (max Name AMD Ryzen Threadripper 1950X Codename Threadripper Specification AMD Ryzen Threadripper 1950X 16-Core Processor Package CPUID F.1.1 Extended CPUID 17.1 Core Stepping ZP-B1 Technology 14 nm TDP Limit 180.0 Watts Core Speed 3393.0 MHz Instructions sets MMX (+), SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, SSE4A, x86-64, AMD-V, AES, AVX, AVX2, FMA3, SHA Microcode Revision 0x1000065 L1 Data cache 8 x 64 KBytes, 2-way set associative, 64-byte line size L1 Instruction cache 8 x 64 KBytes, 2-way set associative, 64-byte line size L2 cache 8 x 512 KBytes, 16-way set associative, 64-byte line size L3 cache 8 x 16 MBytes, 16-way set associative, 64-byte line size Max CPUID level 0000000Dh Max CPUID ext. level 8000001Ah Cache descriptor Level 1, I, 64 KB, 1 thread(s) Cache descriptor Level 1, D, 64 KB, 1 thread(s) Cache descriptor Level 2, U, 512 KB, 1 thread(s) Cache descriptor Level 3, U, 16 MB, 1 thread(s) FID/VID Control yes