Celsian
-
Posts
31 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by Celsian
-
-
@giafidis & @DoeBoye If you aren't using the vBios from your GFX card I recommend using Space Invader Ones script to pull it. The script is here: https://github.com/SpaceinvaderOne/Dump_GPU_vBIOS
Use the User Scripts plugin, add the script and modify the first section, run it once and then assign the vBios in your VM.
-
4 hours ago, fearlessknight said:
Script location: /tmp/user.scripts/tmpScripts/GPUPass/script
Note that closing this window will abort the execution of this script
/tmp/user.scripts/tmpScripts/GPUPass/script: line 3: /sys/class/vtconsole/vtcon1/bind: No such file or directory
/tmp/user.scripts/tmpScripts/GPUPass/script: line 4: echo: write error: No such deviceSame as yours. What do you normally use to remote into your VM? Maybe try a fresh VM install and run the script.
I would agree, try a new VM. Make sure Hyper-V is set back to Yes as well.
Here is what my VM looks like in 6.9.0, perhaps you'll see something that will help:
-
On 5/3/2018 at 6:46 AM, bigjme said:
----------- ANSWER --------
For easy reading, this was the answer needed. In the event that you get mmap errors on passing through the rom, or you install the nvidia drivers and get errors like the above, try running the following in command line and try again
echo 0 > /sys/class/vtconsole/vtcon0/bind
echo 0 > /sys/class/vtconsole/vtcon1/bind
echo efi-framebuffer.0 > /sys/bus/platform/drivers/efi-framebuffer/unbindI added these to a user script that triggers on first array boot up. I have now successfully remove a gpu i no longer need from my system and am able to reboot unraid and have the vm auto start on the primary gpu
Don't mean to Necro, but this solved it for me. Thanks a lot.
If you are looking at your VM Logs by clicking on your VM and clicking Logs, and you're seeing:
2021-03-06T06:32:32.186442Z qemu-system-x86_64: vfio_region_write(0000:09:00.0:region1+0x1be6ba, 0x0,1) failed: Device or resource busy
Try the fix above. It worked for me.
The Hardware I'm running:
ASUS Prime X570-Pro
Ryzen 7 3700x
ASUS Strix GTX 1060 Gaming
Best of luck.
- 1
-
You two are not the only ones. I upgraded to 6.9 and the VM was working fine. I upgraded my hardware from Intel to AMD a few days later, I'm in the same boat you two are now. Rolling back to try 6.8.3 now...
Intel 6700k
ASUS Maximus Hero VIII
upgraded to:
Ryzen 7 3700x
ASUS Prime X570-Pro
GPU is an ASUS GTX 1060.
-------------------------------------------------------------------------
Edit:
I resolved my issue. Having dug deeper I found the following in my VM Log:
2021-03-06T06:32:32.186442Z qemu-system-x86_64: vfio_region_write(0000:09:00.0:region1+0x1be6ba, 0x0,1) failed: Device or resource busy
Some searching yielded another thread:
Adding a user script to User Script Plugin that runs when the array starts seems to have solved my issue, I was able to successfully boot into Windows 10 VM with the GTX 1060 passed through. I have installed the drivers successfully.
The script:
#!/bin/bash
echo 0 > /sys/class/vtconsole/vtcon0/bind
echo 0 > /sys/class/vtconsole/vtcon1/bind
echo efi-framebuffer.0 > /sys/bus/platform/drivers/efi-framebuffer/unbindEdit 2:
For clarification, my VM would not load on 6.8.3 or 6.9.0 with GTX 1060 as my primary and only gpu in the system. This script fixed the problem for me in both 6.8.3 and 6.9.0.
- 2
GPU Passthrough doesnt work after Updating to unRAID 6.9
in VM Engine (KVM)
Posted
Jeez, I'm sorry friends. Not sure where to go from here.
@DoeBoye It sounds like our problems are a little different. I was never able to load the VM unless the Nvidia Driver wasn't installed, otherwise it would freeze on the loading screen, then boot loop.