Jump to content

mikeyosm

Members
  • Posts

    646
  • Joined

  • Last visited

Posts posted by mikeyosm

  1. On 07/11/2017 at 8:35 PM, david279 said:

    I setup a separate vm template based on the Mac Vm xml but for passed thru hardware. I setup virt manager like in grindrunners videos and used it to add the GPU and a couple usb devices to the new vm . Its easy as pick and choose. Adding devices thru virt manager does not reset the xml. I also removed the VNC and QXL video adapters in virt manager. After i had the xml setup I booted my VNCed high sierra... edited the plist file with clover configurator to add the NvidiaWeb System Parameter then installed the Nvidia web drivers. Shutdown the VM. Now boot into the new vm with all the hardware add and it should just boot up. I also had to add the rom dump line to my xml as ryzen has no iGPU.

     

    Awesome work. One thing I am noticing though, HSierra seems much more sluggish than Sierra when using VNC. What is it like for you?

  2. So I got my crosshair vi hero board and ran sensors-detect, here is my output.

    Any ideas how I can force add sensors to UNRAID so I can see my CPU temps?

     

    # sensors-detect revision 6284 (2015-05-31 14:00:33 +0200)
    # Board: ASUSTeK COMPUTER INC. CROSSHAIR VI HERO
    # Kernel: 4.13.13-unRAID x86_64
    # Processor: AMD Ryzen 7 1700 Eight-Core Processor (23/1/1)

    This program will help you determine which kernel modules you need
    to load to use lm_sensors most effectively. It is generally safe
    and recommended to accept the default answers to all questions,
    unless you know what you're doing.

    Some south bridges, CPUs or memory controllers contain embedded sensors.
    Do you want to scan for them? This is totally safe. (YES/no): YES
    Silicon Integrated Systems SIS5595...                       No
    VIA VT82C686 Integrated Sensors...                          No
    VIA VT8231 Integrated Sensors...                            No
    AMD K8 thermal sensors...                                   No
    AMD Family 10h thermal sensors...                           No
    AMD Family 11h thermal sensors...                           No
    AMD Family 12h and 14h thermal sensors...                   No
    AMD Family 15h thermal sensors...                           No
    AMD Family 16h thermal sensors...                           No
    AMD Family 15h power sensors...                             No
    AMD Family 16h power sensors...                             No
    Intel digital thermal sensor...                             No
    Intel AMB FB-DIMM thermal sensor...                         No
    Intel 5500/5520/X58 thermal sensor...                       No
    VIA C7 thermal sensor...                                    No
    VIA Nano thermal sensor...                                  No

    Some Super I/O chips contain embedded sensors. We have to write to
    standard I/O ports to probe them. This is usually safe.
    Do you want to scan for Super I/O sensors? (YES/no):
    Probing for Super-I/O at 0x2e/0x2f
    Trying family `National Semiconductor/ITE'...               No
    Trying family `SMSC'...                                     No
    Trying family `VIA/Winbond/Nuvoton/Fintek'...               No
    Trying family `ITE'...                                      Yes
    Found unknown chip with ID 0x8665
        (logical device 4 has address 0x290, could be sensors)
    Probing for Super-I/O at 0x4e/0x4f
    Trying family `National Semiconductor/ITE'...               No
    Trying family `SMSC'...                                     No
    Trying family `VIA/Winbond/Nuvoton/Fintek'...               No
    Trying family `ITE'...                                      No

    Some systems (mainly servers) implement IPMI, a set of common interfaces
    through which system health data may be retrieved, amongst other things.
    We first try to get the information from SMBIOS. If we don't find it
    there, we have to read from arbitrary I/O ports to probe for such
    interfaces. This is normally safe. Do you want to scan for IPMI
    interfaces? (YES/no):
    Probing for `IPMI BMC KCS' at 0xca0...                      No
    Probing for `IPMI BMC SMIC' at 0xca8...                     No

    Some hardware monitoring chips are accessible through the ISA I/O ports.
    We have to write to arbitrary I/O ports to probe them. This is usually
    safe though. Yes, you do have ISA I/O ports even if you do not have any
    ISA slots! Do you want to scan the ISA I/O ports? (YES/no):
    Probing for `National Semiconductor LM78' at 0x290...       No
    Probing for `National Semiconductor LM79' at 0x290...       No
    Probing for `Winbond W83781D' at 0x290...                   No
    Probing for `Winbond W83782D' at 0x290...                   No

    Lastly, we can probe the I2C/SMBus adapters for connected hardware
    monitoring devices. This is the most risky part, and while it works
    reasonably well on most systems, it has been reported to cause trouble
    on some systems.
    Do you want to probe the I2C/SMBus adapters now? (YES/no):
    Found unknown SMBus adapter 1022:790b at 0000:00:14.0.
    Sorry, no supported PCI bus adapters found.
    Module i2c-dev loaded successfully.

    Next adapter: SMBus PIIX4 adapter port 0 at 0b00 (i2c-0)
    Do you want to scan it? (YES/no/selectively):
    Client found at address 0x50
    Probing for `Analog Devices ADM1033'...                     No
    Probing for `Analog Devices ADM1034'...                     No
    Probing for `SPD EEPROM'...                                 No
    Probing for `EDID EEPROM'...                                No
    Client found at address 0x51
    Probing for `Analog Devices ADM1033'...                     No
    Probing for `Analog Devices ADM1034'...                     No
    Probing for `SPD EEPROM'...                                 No
    Client found at address 0x52
    Probing for `Analog Devices ADM1033'...                     No
    Probing for `Analog Devices ADM1034'...                     No
    Probing for `SPD EEPROM'...                                 No
    Client found at address 0x53
    Probing for `Analog Devices ADM1033'...                     No
    Probing for `Analog Devices ADM1034'...                     No
    Probing for `SPD EEPROM'...                                 No

    Next adapter: SMBus PIIX4 adapter port 2 at 0b00 (i2c-1)
    Do you want to scan it? (YES/no/selectively):

    Next adapter: SMBus PIIX4 adapter port 3 at 0b00 (i2c-2)
    Do you want to scan it? (YES/no/selectively):

    Next adapter: SMBus PIIX4 adapter port 4 at 0b00 (i2c-3)
    Do you want to scan it? (YES/no/selectively):

    Sorry, no sensors were detected.
    Either your system has no sensors, or they are not supported, or
    they are connected to an I2C or SMBus adapter that is not
    supported. If you find out what chips are on your board, check
    http://www.lm-sensors.org/wiki/Devices for driver status.

     

  3. Can someone running UNRAID 6.4 RC10 and Threadripper please try disabling ASPM in their BIOS (ASROCK boards have this, not sure about others) and also adding pcie_aspm=off  to the flash/boot section in the UNRAID GUI and test GPU passthrough again? I have read reports that this may resolve the D3/sleep issue and allow us to reboot VMs without having to reboot the host. If it works, could be an acceptable workaround until the wider problem is resolved.

  4. 1 minute ago, Tuftuf said:

     

    Thanks for your post! What you have explained is very similar to myself apart from I've not given up on the passthrough in the top port and I've not purchased a usb pcie card yet.

     

    I started off passing through just the 670, then I added a 6950 but replaced that with a Firepro I had spare. I'm running two GPU's in my system which is the main reason ive not tried the PCIe usb card yet. Passing through the Keyboard and Mouse has always worked great. USB audio has drop outs, but I can play most games with only a few audio hickups.. some are much worse than others.

     

    After the NPT fix I also had the 43 error, made a couple of posts about it in the pre release thread. I don't really have any proof but I felt that I had more issues after my VM was shutdown after the NPT fix than before. To be clear I mean shutting down the VM and starting it up again.

     

    I installed the NPT fix (before Limetech added it to rc10) using a dvb plugin build scripts and supplying the patch before it actually built the thing. Then the fun started.

    I rebooted and tested my Windows VM.. It worked.. GREAT.

    I rebooted and my GPU would not start up with error 43. NOT SO GREAT!

    I created a new VM and my GPU would not start up Error 43. NOT SO GREAT! (Note this error 43 is presented to me within Device Manager, not at boot like I've seen others post)

    I repeated this many times... nothing seemed to fix it. New VM, New Drivers, Old drivers. 

     

    Then I rebooted my whole server... and Error 43 disappeared.

     

    This led me to think that there are some issues after a VM is shutdown with the hand off with the GPU. I have no fact or really any proof to back this up. But I've not had another error code 43 since then first few days of testing.

     

     

    From experience, the hand-off/ device reset issues have only ever plagued me with Gigabyte boards since they are the very few that allow you to choose a PCI-e slot as Primary display.

    Having said that, the reset issues affected my Samsung nvme when passed through to a VM and not the gfx card.

  5. 3 minutes ago, amelius said:

    Idk where you heard that, sure, that's what their site *claims* but in reality, it's totally not an issue, you just need to set hypervisor.cpuid.v0  = FALSE and it's all fine. Also, ESXi handles that D3 issue no problem, since you can set the way it handles turning PCI devices on and off. (Tip, if you want to not reboot between using the same GPU, make sure you don't do a forced shutdown on a VM that has a GPU passed through, only a proper shutdown will make it available again for that same (or another) vm without a reboot of the host. If you want a guide that outlines passing through in ESXi, https://www.reddit.com/r/Amd/comments/72ula0/tr1950x_gtx_1060_passthrough_with_esxi/ has a rough outline that works perfectly. I tested it with my configuration and had no issues with getting up and running on both Windows 10 and Ubuntu 16.04 with a GTX 1080 Ti passed through on each one (though on Ubuntu I ran into an annoying login loop i've run into before, but that's just an issue with Xorg and Nvidia drivers not playing nice, not an issue with the passthrough though.)

     

    Ah, I see, that's good to know. I did read somewhere that hypervisor.cpuid.v0 = FALSE disables certain performance enhancements within the W10 VM so I  was reluctant to use this parameter. How about temperature monitoring? What does ESXi / vCenter show in terms of temperatures for your devices?

  6. 6 minutes ago, amelius said:

    So after struggling with trying to use Unraid and looking around some forums, I ended up pivoting to ESXi, which actually has no problem with GPU passthrough (though the configuration is a pain), but has a shocking amount of difficulty passing through USB devices (but this is also surmountable). The only downside is the lack of convenient software RAID support. 

     

    I thought nvidia passthrough was a no go with ESXi? Also, ESXi does not show temperatures for motherboard etc?

  7. As an added tip I would also consider using direct passthrough for your SSD/NVME drive to the Windows 10 VM. In the past, whenever I provisioned a W10 VM using vfio scsi driver / raw image, i ran in to random audio 'crackle & pop' issues even when using msiutil. Passing through an nvme meant i could also use samsung nvme driver for optimal performance.

  8. Just now, methanoid said:

     

    You might try the 6.5u1 which is patched for Ryzen and should work.. works for others I believe?  Then LMK how you got on with passthrough please

    I would switch to vmware esxi in a heartbeat if temperature monitoring for most mobo components and nvidia geforce passthrough worked. 

  9. 5 minutes ago, eschultz said:

    Just purchased a AMD Threadripper 1950X cpu and MSI X399 gaming pro carbon motherboard.  Parts will arrive mid next week and will hopefully get some unRAID testing in by that weekend.

     

    Cool. Let us know your 3dmark bench scores particularly the fire strike physics and combined since that is severely impacted by the NPT issue and Ryzen. Where did you purchase from if you don't mind me asking?

  10. 1 minute ago, methanoid said:

    Ryzen owners, how are your VMs running? I saw Level1Techs had some issues with VMs and passthru on Ryzen and I'd like some feedback before I drop a pile of cash on a 16 core Threadripper setup to run multiple VMs with passthrough

    Wait until it's confirmed that npt issue that's plaguing ryzen owners is not present in threadripper. I have no idea if it's being looked at tbh and like you I'm very keen on TR.

    • Upvote 1
  11. 9 minutes ago, HellDiverUK said:

    Latest update on my 1700X.

     

    I can run [email protected], but I've settled at 3.975GHz at 1.3575v which actually benchmarks better in both 3DMark and Cinebench R15.  

     

    Heat is a major issue at 4GHz - even with the H110iGT and the fans going fast, the CPU is still hitting 80C.

     

    I'm quite pleased with the PRIME X370-Pro now, apart from being hit with the common problem that the RGB lighting has totally stopped working.  Seems to be an issue with this model of board.

     

    Are you seeing close to bare metal 3D performance? Everyone that I know with ryzen and kvm are having big performance drops with npt. Physics scores are also very low.

  12. 46 minutes ago, Tuftuf said:

    The only downside for my Ryzen system at the moment is that gaming performance is not perfect within a VM, some games run ok with a slight stall every so often. My other games that use the CPU more, stall more often. I still class them as playable but it is causing me problems.

     

    I do see a good FPS increase with the npt setting but my vms are are worse in other ways (known issue). 

     

    Plus the c-state thing but the workaround is acceptable for now.

    Yeah, it's the main reason why I'm not playing games as much as i used to on my xeon system. If this NPT issue does not get resolved soon and I mean within the month, Intel 7900x will be mine.

  13. Can someone please share their 3dmark firestrike extreme physics score on a 1800x windows 10 VM?

    I only get 6000ish and not sure why. I have 4 cores and 8 threads allocated to my w10 VM and performance in physics is pretty dire.

    My Spec:

    1800x

    980ti

    32GB Gskill at 2400mhz.

    UNRAID 6.4RC6

    Asus Prime latest BIOS

  14. 1 minute ago, rachid596 said:


    Hello, i dont know why your problems come from. But can you tell me your build because I plan to build a ryzen build with easy pass-through. Thanks

    Envoyé de mon FRD-L09 en utilisant Tapatalk
     

    Asus Prime x370

    Ryzen 1800x

    32GB Gskill

    Zotac 980ti Amp!

    UNRAID 6.3.5

    • Upvote 1
  15. Guys - what's your experiences with Windows 10 and either 4 cores or 8 cores, which performs better for you in gaming?

    I passed through my 980ti today and getting really poor physics scores in 3dmark, In firestrike extreme i get 6fps on just the physics test.

    I dedicated 8 ryzen cores in the usual pairs 2,3,4,5,6,7,8,9. GPU scores seem normal so not sure why my CPU is taking a big hit in physics.

    What's everyone else's scores?

  16. 5 hours ago, ufopinball said:

     

    Okay, so I have loaded the ASUS Prime X370-PRO beta-test BIOS 0803 with AMD/Ryzen AGESA 1.0.0.6.  I am still running unRAID 6.3.5, though.

     

    The BIOS upgrade seemed to take longer this time.   As usual, I had to go in and redo all my preferred settings.  The system accepted them and rebooted, then did nothing for like 10 minutes.  I finally powered down, counted to 10, and started it up again and this time it worked.  No idea what was up with the weird hang.  I've rebooted about 3-4 times since then trying different things, and have not encountered it again.  Just be-aware that this may occur, at least the first time after the BIOS upgrade.

     

    Otherwise, my system temperatures are a bit higher, but we're in the middle of a heat wave and that may have something to do with it.  My memory is rated at 2133, so I'm not testing for the 3000-4000 speeds that others are looking for.

     

    I did turn off all the ACS override stuff, but the "new" IOMMU table doesn't look all that impressive:

    
    IOMMU group 0
    	[1022:1452] 00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 1452
    IOMMU group 1
    	[1022:1453] 00:01.3 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 1453
    IOMMU group 2
    	[1022:1452] 00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 1452
    IOMMU group 3
    	[1022:1452] 00:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 1452
    IOMMU group 4
    	[1022:1453] 00:03.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 1453
    IOMMU group 5
    	[1022:1452] 00:04.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 1452
    IOMMU group 6
    	[1022:1452] 00:07.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 1452
    	[1022:1454] 00:07.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 1454
    	[1022:145a] 29:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Device 145a
    	[1022:1456] 29:00.2 Encryption controller: Advanced Micro Devices, Inc. [AMD] Device 1456
    	[1022:145c] 29:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Device 145c
    IOMMU group 7
    	[1022:1452] 00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 1452
    	[1022:1454] 00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 1454
    	[1022:1455] 2a:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Device 1455
    	[1022:7901] 2a:00.2 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51)
    	[1022:1457] 2a:00.3 Audio device: Advanced Micro Devices, Inc. [AMD] Device 1457
    IOMMU group 8
    	[1022:790b] 00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 59)
    	[1022:790e] 00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 51)
    IOMMU group 9
    	[1022:1460] 00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 1460
    	[1022:1461] 00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 1461
    	[1022:1462] 00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 1462
    	[1022:1463] 00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 1463
    	[1022:1464] 00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 1464
    	[1022:1465] 00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 1465
    	[1022:1466] 00:18.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 1466
    	[1022:1467] 00:18.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 1467
    IOMMU group 10
    	[1022:43b9] 03:00.0 USB controller: Advanced Micro Devices, Inc. [AMD] Device 43b9 (rev 02)
    	[1022:43b5] 03:00.1 SATA controller: Advanced Micro Devices, Inc. [AMD] Device 43b5 (rev 02)
    	[1022:43b0] 03:00.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 43b0 (rev 02)
    	[1022:43b4] 1d:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 43b4 (rev 02)
    	[1022:43b4] 1d:04.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 43b4 (rev 02)
    	[1022:43b4] 1d:06.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 43b4 (rev 02)
    	[1022:43b4] 1d:07.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 43b4 (rev 02)
    	[1000:0072] 21:00.0 Serial Attached SCSI controller: LSI Logic / Symbios Logic SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] (rev 03)
    	[1b21:1343] 25:00.0 USB controller: ASMedia Technology Inc. Device 1343
    	[8086:1539] 26:00.0 Ethernet controller: Intel Corporation I211 Gigabit Network Connection (rev 03)
    IOMMU group 11
    	[1002:677b] 28:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Caicos PRO [Radeon HD 7450]
    	[1002:aa98] 28:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Caicos HDMI Audio [Radeon HD 6450 / 7450/8450/8490 OEM / R5 230/235/235X OEM]

    I ended up switching the ACS override back on, since my Windows 10 VM wouldn't start without it.

     

    Unfortunately, that's about all the time I have at the moment.  I'd still like to switch from the USB audio to the onboard audio, and will hopefully find some time to poke at that soon.

     

    Dunno if anyone is monitoring the unRAID 6.4 board, but they're up to RC3 now.  No idea how close they are to a final cut.  That's still on my list, though.  Anyone else give it a try?

     

    - Bill

     

    Same board, same issue with the grouping. I updated to latest 6.4rc3 and no change.

     

  17. 9 minutes ago, unrateable said:

    was full of hopes for propper isolation when I read about the new AMD release, but lost a bit of faith upon seeing your post. I hope I am wrong and more people will report back soem improvements.

     

    very interesting in your grouping is;  this is the first time I see iommu groups breaking up right in between the GPU and its very own audio device.
    I wonder do these split groups, and especially the GPUs properly work as they should - and with minimal performance losses inside the VMs ? 

    afaik when using ACS override patches one can expect occasionally some odd system behaviour. due to the "illegally" shared ressources maybe ?

     

     

    Maybe I'm just lucky but I seem to go days without issues with a bit of light Minecraft gaming, Plex 4k streaming and osx usage. Looking forward to the new agesa to see what impact it has on memory overclocking, I'm on a disappointing 2133mhz atm

×
×
  • Create New...