So, I’ve been poking at this system for a good couple days now and I’m really really lost.
I have passthrough working with my 1060 3GB on the same VM. That isn’t the issue. I understand passthrough at a base level. Stub the card, provide the ROM because it’s Slot 1, and party.
Mind, this config works fine with a GTX 1060 3GB from MSI. Works great, actually. I just wanted more power for VR stuff and had this Vega 64 as an eGPU for my Macbook Pro and wanted to try it out as the card in my VR system before bothering to set it up with Bootcamp and dealing with issues related to eGPU latency and VR, as the 1060 was laggy with my Rift.
If I’m being honest, I’m almost tempted to switch from unRAID to WinServer2016, but I rely heavily on Docker, and all my disks are btrfs and I don’t have space to migrate all that data if I wanted to.
I’m running kernel version 4.19.33, QEMU 3.1, and the latest packages provided by unRAID
Best I can get is error 31 in Windows, which is to say, not very far. Trying to install the Radeon driver locks the system. Same error under ESXi, actually.
The ROM file doesn’t seem to make much of a difference.
Recent AMD cards have a reset bug. Vega is definitely affected. It is a hardware issue, so it would require a major firmware rework at a minimum on AMD’s part to fix, and they have not fixed even with the Radeon VII.
If you reboot/reset/turn off+ turn on the VM, you need to reboot the host before it will work. The issue is that the card does not reset properly without a full bare-metal system restart, which is fine normally, but is problematic in a VM.
And I can’t find the post now, but I’ve definitely read that 4.19 helped with the reset bug, not that i even care. I just wanted to get the VM booting once and not dying the moment the driver tried to install
I was facing similar issues with a vega 56 on B450 Board.
The one setting hat seems to work is:
-Disable legacy boot options (for reasons I fail to understand)
-Save the ROM of my GPU in GPU-Z on baremetall install
-rename the rom to Vega56.rom in my case (this was necessary and did not work when named “Vega 10.rom”
-passthrough rom
-Stub GPU and HDMI Sound (for me they need to be in different IOMMU groups since HDMI sound can’t be passed through successfully)
-Not pass through HDMI sound
-Run Q35-3.1 (i440fx didn’t work)
Well…at this point I really thing the hole discussion is a hugh mess since Kernel changes, Bios changes and a lot of confusion in the process generated a situation where common configurations are a rare that every case seems to be different.
But I do hope that I might notch you or someone in the right direction.
@mo-mobile I am having these issues too with similar hardware
How did u disable Legacy boot Mode? I tired to do this in B450 BIOS settings where it said “Legacy+UEFI” and changed to just “UEFI” but then Unraud never boots and I just return to B450 BIOS settings.
I am unfamiliar how to save the ROM in GPU-Z? I have extracted the ROM from my GPU and also have msi-rxvega56-8192-180316 from techpowerups.
I have tried bounding the GPU IOMMU groups and not passing through audio with no luck, so maybe your earlier steps are a requirement.
I figured out how to boot into UEFI with Legacy off my changing settings in Unraid. Also saved my ROM a different way then using GPU-Z, but I believe it worked.
Still haven’t gotten in to work yet, but maybe getting closer.
Hello, I can report success with the MSI Vega64. What I did was to go to the Clover configurator, and on the Lernel section enable lilu.kext, WhateverGreen, AppleAcl, AGPMinjector nd USBPorts.
Moreover, in the helper script, I set REMOVETOPOLOGY=“yes”.
Bingo, my Vega 64 is up and running. The only problem I need to solv now is the scaling on one of my monitor is not very good, As I was able to pass through an USB controller, I found out an old bluetooth USB dongle is actually recognized, so I am using my Magic Mouse at the moment.