Wow, this tutorial worked great! This almost never happens, following a tutorial step by step and getting the exact same results as depicted in the tutorial, thats extremely rare for me. Usually when I tackle tutorials like this I either expect it to completely fail outright for seemingly no comprehensible reason, or I need to figure out and do 37 million extra things that weren't mentioned, or I hit a brick wall with some weird error that only brings up like three results on google that are only similar but not the same, or I would otherwise be one of the unlucky few that has hardware that either flat out doesn't support what I'm trying to do or it requires me go down 12 other rabbit holes to configure a work around. I was absolutely flabbergasted at the end when it just... booted perfectly... and the GPU drivers installed perfectly... and the games installed perfectly... and ran perfectly. I honestly got whiplash from how smoothly this went. It literally feels uncanny. Like the fact that something didn't go wrong... feels wrong. Like I said, in 99% of my linux experience there is always some oddity somewhere waiting patiently to screw me over.
Important note: do *not* leave SAM/ReBAR enabled if you do this. It may not work as it is not perfectly supported by Qemu/KVM. I did not find the written guide mentioning this anywhere, but that was the last bit of troubleshooting I had to dig through to get this to work smoothly. Edit: It now boots perfectly fine with SAM enabled. I'd say only disable it if you run into issues booting the VM.
@@pontifexmaximus6049 I've just enabled SAM in BIOS and it now indeed works perfectly fine. Perhaps a recent patch made it work for my config. I've read many reports online that many others had issues with error code 43 while Re-BAR enabled.
@@pontifexmaximus6049 I've just enabled SAM in BIOS without changing anything, and now it does indeed work perfectly fine. Perhaps some patch made it work for my config. I could not get it to boot the VM before, no matter what I changed and read through many similar reports. Thanks for the hint, glad it's fixed now.
usually I don't comment but you've outdone yourself with this guide man I followed 3 other guides had no luck and this guide was thorough and helped me setup my VM for gaming with ease. You even included segments to bypass some anti cheats to allow me to play on a VM too actual legend you got a sub from me :)
So when you make the changes in the Grub config, doesn't that mean the dgpu no longer works for the host os? Does that have to be switched back in order to go back to gaming without the VM?
One of best tutorials for quite a complex process. Some suggestions I have 1. make setup scripts that automate dumping, editing and placing the firmware. 2. service to restart nvidia/gpu/display service on host if it didn't get properly attached with guest or guest didn't boot up.
protip if any1 has trouble with the release script: in my case (arch, r9 5900x, gtx 3080) even tho i have both vtcon0 and vtcon1, the release script could not rebind vtcon1, so try commenting out vtcon1 bind and unbind lines in the prepare and release scripts and check if it works, worked for me also for faster testing of the scripts, ssh to your pc and just manually run the prepare and release scripts and see if linux regains control of the gpu, this saved me a lot of time troubleshooting
i dont get it, my pc just goes into tty when i try booting the vm :( ive had nothing but problems trying to get this to work... i just wanna play 1 game thats blocked on linux man
Hello , looking to get some help here .... So I'm getting nvflash error ( Falcon in halt or stop state , abort uCode command issuing process) What can I do about this ????
Windoof is a great name for the VM 😂 I guess if I already have a running Win in a separate HDD, after setting the physical hard drive in virt manager, it *should* boot into the OS normally, right?
when i go into tty and do the commands 'sudo systemctl stop sddm', 'sudo systemctl stop nvidia_uvm', and 'sudo systemctl stop nvidia-persistenced' I am still not able to kill the nvidia_drm service with rmmod or modprobe -r, both still tell me that the module is in use.
I did the tutorial 3 times, I reinstalled Manjaro several times and every time I start the VM my PC freezes, the mouse and keyboard disconnect and Manjaro doesn't enter the VM. it just gets stuck
hey, everything went well however while i tried to run the vm it just restarts sddm, not sure what i should do, arch linux edit: i should mention that the scripts didnt get moved after executing the shell, copied them myself but without the .sh extension with chmod +x which did not fix anything, the service was fine
Everything is working great but GPU doesn't load into the Host OS after Guest OS is shut down Win10 logs: 2023-06-02T17:32:12.717390Z qemu-system-x86_64: vfio: Unable to power on device, stuck in D3 2023-06-02T17:32:12.717480Z qemu-system-x86_64: vfio: Unable to power on device, stuck in D3 2023-06-02T17:32:12.725345Z qemu-system-x86_64: vfio: Unable to power on device, stuck in D3 2023-06-02T17:38:33.607258Z qemu-system-x86_64: terminating on signal 15 from pid 731 (/usr/bin/libvirtd) 2023-06-02 17:38:36.015+0000: shutting down, reason=shutdown
@@aa6_ can i use linux with a 4090? I heard somewhere amd is better or required. I want to learn linux but there is alot of windows only apps i need like vs studio and windows only games so i will need to use a vm for that.
Windows virt iso doesn't boot :( followed exactly your instructions and no "Press the key" message appears and when i select any CD ROM in the boot manager, it just refreshes the page UPDATE: I was trying to boot into virtio-win ISO, but it's drivers, not the Windows image
@@xDraga yeah but the github says that the script has been tested on a dual gpu setup which makes no sense and from what ive read you still need an igpu
Get your USB stick and update your BIOS, if you are unlucky it will delete your grub bootloader and your system won't boot. :/ Boot into a live disk and reinstall grub and kernel.
@@serbaldomiro Personally I would not recommend doing something like that at all. What you're asking difficult and it's something completely different to this guide. Of course you can always give it a try, but it will give you a headache, and it might take you roughly 2 weeks or more to learn it, if you're new to this stuff. Again would not recommend. (Also I'm honestly unsure if it's even possible)
The scrip in the IOMMU section doesn't work at all in Proxmox. No outout whatsoever. I tried pasting it into Powershell, CMD Prompt, Debian11 terminal, Proxmox shell and Solar PuTTy (SSH:d to my Proxmox host ofc). I also tried to make it into bash script, but that doesn't output anything either. I ended up using lspci -v in the end because I couldn't figure out how to get that script to work. I'm sure the solution is something very simple, but I'm very much a beginner with Linux trying to get into Proxmox out of necessity.
@@aa6_ Thank you so much! Idk what happened while I was trying various things but somehow I had disabled IOMMU in Proxmox at some point. Now it works. I did however stumple on another way of doing what that script does: for g in /sys/kernel/iommu_groups/*; do echo "IOMMU Group ${g##*/}:"; for d in $g/devices/*; do echo -e "\t$(lspci -nns ${d##*/})"; done; done; As far as I can tell, it does the exact same thing, but works even if IOMMU is disabled which is bad when figuring out how to configure PCIe passthrough. Also something to note for Proxmox users: When installing okteta it's just sudo apt-get install okteta No need to mess with snap. Which fails to install KDE Frameworks 100% of the time, at least on Debian and Proxmox, making installing Okteta impossible.
New imsges of windows 10 add something called watchdog and thats causing problems the forst time i followed the guide i used an old iso w10. And it was detected as such the latest isos of w10 get detected as w11 and get the watchdog
Hi, have you found a workaround for it? I tried disabling it but still messes with display connection. Been thinking on trying an older win10 iso, but im afraid that with driver updates, it will add watchdog to its kernel again.
Nevermind, replaced it with "risingprismtv/single-gpu-passthrough" and worked, as someone suggested in the comments down below. Thank you for you effort.
@@Xongasbr you can return to host only while turning off guest, the second way is to have dedicated gpu for host and dedicated gpu for guest, since when you start the guest host will lose gpu access ...
This probably is an issue with the teardown script, at the "Rebinding consoles" section at the end, just comment it out and you should be returning to your host This is an issue that needs to be fixed in the scripts Putting this here for future references
I usually just run them through Wine and it works fine for the most part. Only once I had a trouble with font rendering and installing some fonts fixed it.
Same some stuff is so poorly supported through proton and wine that you don't really have any other option. I've been trying to read ever17 on a vm and it runs like hot ass.
@Lameless are you using an amd gpu? If so, open the teardown script and delete everything in the rebind console section. Should do the trick for amd. If that didn't fix it or you are using a nvidia gpu, check the Windows log file. At the very bottom of that file, check if it says something along the lines of "could not reset group" or "group is not owned" It basically says what extra group it needs to be able to reset a device. If that still doesn't fix it, feel free to join discord
I think it is some CPU issue, with the version of Win10 iso am using, it doesn't work with Host Cpu Config, so you have to turn it off and then install the spyware OS
This guide completely wasted my time. I get to the end just to keep getting repeated errors when adding the info to the xml file in the end because I’m using an nvidia card on a laptop. PLUS THE OWNER OF THIS CHANNEL SKIPS OVER THIS PART AND DOESNT EVEN SHOW AN EXAMPLE.
Thank you very much. I did it. And AMD CPU just need to add /etc/modprobe.d/kvm.conf options kvm ignore_msrs=1 It's help to install windows 10 LTSC ( I remove my PCIE-wifi-network-card, it's kind of issues temporarily）
I'm getting a black screen no matter what 03/31/2024 16:29:58 : Beginning of Startup! 03/31/2024 16:29:58 : Display Manager is not KDE! 03/31/2024 16:29:58 : Distro is using Systemd 03/31/2024 16:29:58 : Display Manager = gdm 03/31/2024 16:29:58 : Unbinding Console 1 2b:00.0 VGA compatible controller [0300]: NVIDIA Corporation GA104 [GeForce RTX 3070 Ti] [10de:2482] (rev a1) 03/31/2024 16:29:58 : System has an NVIDIA GPU /usr/local/bin/vfio-startup: line 123: echo: write error: No such device modprobe: FATAL: Module drm_kms_helper is builtin. modprobe: FATAL: Module drm is builtin. 03/31/2024 16:29:58 : NVIDIA GPU Drivers Unloaded 03/31/2024 16:29:58 : End of Startup! 03/31/2024 16:30:05 : Beginning of Teardown! 03/31/2024 16:30:05 : Loading NVIDIA GPU Drivers modprobe: ERROR: could not insert 'nvidia': No such device modprobe: ERROR: could not insert 'nvidia_modeset': No such device modprobe: ERROR: could not insert 'nvidia_drm': No such device modprobe: ERROR: could not insert 'nvidia_uvm': No such device 03/31/2024 16:30:05 : NVIDIA GPU Drivers Loaded
yur gpu failed to unbind from the linux host because there are processes that still use the gpu u need to mke sure that all gpu relied processess and services are closed before unbidning by modifying yur script
@@aa6_ it shouldn't be :p hope it will be easier in the future so people that don't like spending time configuring pc can hop to Linux. Very promising tech otherwise.
@@skimmingdeath Best I can do is 15min setup process. Copy-pasting configurations from the internet is error prone and not very user friendly. I feel like in the end if you want to expose any functionality to users it should be as easy as installing app and then few keys away, not 50min guide :P I didn't mean 'easy' as 'easy to do', more like 'simple and quick process'. If your bar for 'easy' is 'just follow this 50min guide' then we might just disagree about the word ^_^
Please help when I save the rom via nvflash (Sudo ./nvflash --save rtx4090.rom) it gives a error (.nvflash: 1: Syntax error: word unexpected (expecting ")")) I run Linux Mint
Wow, this tutorial worked great! This almost never happens, following a tutorial step by step and getting the exact same results as depicted in the tutorial, thats extremely rare for me. Usually when I tackle tutorials like this I either expect it to completely fail outright for seemingly no comprehensible reason, or I need to figure out and do 37 million extra things that weren't mentioned, or I hit a brick wall with some weird error that only brings up like three results on google that are only similar but not the same, or I would otherwise be one of the unlucky few that has hardware that either flat out doesn't support what I'm trying to do or it requires me go down 12 other rabbit holes to configure a work around. I was absolutely flabbergasted at the end when it just... booted perfectly... and the GPU drivers installed perfectly... and the games installed perfectly... and ran perfectly. I honestly got whiplash from how smoothly this went. It literally feels uncanny. Like the fact that something didn't go wrong... feels wrong. Like I said, in 99% of my linux experience there is always some oddity somewhere waiting patiently to screw me over.
Important note: do *not* leave SAM/ReBAR enabled if you do this. It may not work as it is not perfectly supported by Qemu/KVM. I did not find the written guide mentioning this anywhere, but that was the last bit of troubleshooting I had to dig through to get this to work smoothly.
Edit: It now boots perfectly fine with SAM enabled. I'd say only disable it if you run into issues booting the VM.
I actually have it enabled and the NVDIA control panel in the VM even says that it works. Perhaps you may need to update your system and UEFI?
@@pontifexmaximus6049 I've just enabled SAM in BIOS and it now indeed works perfectly fine. Perhaps a recent patch made it work for my config. I've read many reports online that many others had issues with error code 43 while Re-BAR enabled.
@@pontifexmaximus6049 I've just enabled SAM in BIOS without changing anything, and now it does indeed work perfectly fine. Perhaps some patch made it work for my config. I could not get it to boot the VM before, no matter what I changed and read through many similar reports. Thanks for the hint, glad it's fixed now.
@@NeoAemaeth did u used the exact same scripts?
King video and guy, went above and beyond to help me setup VFIO properly on my PC.
All the best for 2023 man:)
Followed 3 other guides and yours was the only successful one. Thanks!
Happy to hear :)
Thank you. I just swapped my old 1060 to 3070 and this video was the key to cut the code on the bios.
Glad it worked! :)
usually I don't comment but you've outdone yourself with this guide man I followed 3 other guides had no luck and this guide was thorough and helped me setup my VM for gaming with ease. You even included segments to bypass some anti cheats to allow me to play on a VM too actual legend you got a sub from me :)
Bro, does it work for Valorant???
@@masterworld4698 you gotta use a method for kernel based games to work
@@randomusername0x0 what method
Awesome thank you :)
It does not work for valorant sadly.
Great video-representation of the Guide! Thanks!
Had to edit the scripts to make it work without Systemd, tho :p
Great stuff!
So when you make the changes in the Grub config, doesn't that mean the dgpu no longer works for the host os? Does that have to be switched back in order to go back to gaming without the VM?
I finally slept.
My insomonia is gone 😀.
Your every level OP
Note: On W11 you need to go to TPM and select TPM 2.0 in the advanced dropdown when creating the VM.
One of best tutorials for quite a complex process. Some suggestions I have
1. make setup scripts that automate dumping, editing and placing the firmware.
2. service to restart nvidia/gpu/display service on host if it didn't get properly attached with guest or guest didn't boot up.
Thanks man, I'll keep that in mind for a future video, if vm setups ever change.
@@aa6_ do u have any tips on which users to add on the groups u mentioned above?
Perfect to the point.
thank you so much!!!!!!! it works!!!!!!!!!!!!!!!!
Happy to hear.
protip if any1 has trouble with the release script: in my case (arch, r9 5900x, gtx 3080) even tho i have both vtcon0 and vtcon1, the release script could not rebind vtcon1, so try commenting out vtcon1 bind and unbind lines in the prepare and release scripts and check if it works, worked for me
also for faster testing of the scripts, ssh to your pc and just manually run the prepare and release scripts and see if linux regains control of the gpu, this saved me a lot of time troubleshooting
i dont get it, my pc just goes into tty when i try booting the vm :(
ive had nothing but problems trying to get this to work... i just wanna play 1 game thats blocked on linux man
What terminal is he using? I like that it autocompletes.
Hi, i apreciate the video!
the zen kernel for ubuntu is liquorix?
yes
I need to do the acs patch but I can't find anywhere how to install zen on debian. any help would be appreciated
Hello , looking to get some help here ....
So I'm getting nvflash error ( Falcon in halt or stop state , abort uCode command issuing process)
What can I do about this ????
hey, i've followed all your steps but when i start the VM it completely sends me back to the tty login screen, and freezes afterwards
Did u find any solution?
Is it fixed yet? If not let me know, I'll see how I can help out.
Same here
Windoof is a great name for the VM 😂 I guess if I already have a running Win in a separate HDD, after setting the physical hard drive in virt manager, it *should* boot into the OS normally, right?
My bad for late reply. Yes it should just boot into the windoof OS.
What should I enter after `yay kernel zen` ? which package to install? you didn't mention
Do you still need help?
Sorry for late reply.
@@aa6_ can u do another video on more in depth look into the scripts u used in the video, thanks.
when i go into tty and do the commands 'sudo systemctl stop sddm', 'sudo systemctl stop nvidia_uvm', and 'sudo systemctl stop nvidia-persistenced' I am still not able to kill the nvidia_drm service with rmmod or modprobe -r, both still tell me that the module is in use.
I did the tutorial 3 times, I reinstalled Manjaro several times and every time I start the VM my PC freezes, the mouse and keyboard disconnect and Manjaro doesn't enter the VM. it just gets stuck
hey, everything went well however while i tried to run the vm it just restarts sddm, not sure what i should do, arch linux
edit: i should mention that the scripts didnt get moved after executing the shell, copied them myself but without the .sh extension with chmod +x which did not fix anything, the service was fine
Everything is working great but GPU doesn't load into the Host OS after Guest OS is shut down
Win10 logs:
2023-06-02T17:32:12.717390Z qemu-system-x86_64: vfio: Unable to power on device, stuck in D3
2023-06-02T17:32:12.717480Z qemu-system-x86_64: vfio: Unable to power on device, stuck in D3
2023-06-02T17:32:12.725345Z qemu-system-x86_64: vfio: Unable to power on device, stuck in D3
2023-06-02T17:38:33.607258Z qemu-system-x86_64: terminating on signal 15 from pid 731 (/usr/bin/libvirtd)
2023-06-02 17:38:36.015+0000: shutting down, reason=shutdown
Sorry for late reply.
The problem is usually fixed with a bios update
Would that work on a laptop with intel iGPU + Nvidia discrete card if I try to pass the internal (intel UHD) one ?
Passing through the igpu is extremely hard, I'd recommend using that external nvidia card instead.
Discord link does not work anymore could u share another one?
what do u use for the theme in manjaro looks sick
Wm Theme: Adwaita
Theme: Adw-dark
@@aa6_ can i use linux with a 4090? I heard somewhere amd is better or required. I want to learn linux but there is alot of windows only apps i need like vs studio and windows only games so i will need to use a vm for that.
@@Anthony0855 You can use the 4090 😀 (nice gpu, kinda jealous)
@@aa6_ ive just got it few days ago havent updated in a good 8 years lol thought it was about time. 👍
How do you deal with the amd reset bug from amd gpus? Nvidia always worked for me but having always issues with AMD.
Google vendor reset patch, it should be from gnif (the creator) and if you click on the github it tells you how to install the patch
Windows virt iso doesn't boot :( followed exactly your instructions and no "Press the key" message appears and when i select any CD ROM in the boot manager, it just refreshes the page
UPDATE: I was trying to boot into virtio-win ISO, but it's drivers, not the Windows image
38:28 I'm confused... Are we really supposed to allocate all the cpu cores to the vm? I thought we should at least save 2 core for the host.
For single gpu passthrough it is fine, but for passthroughts with 2 or more gpus, you need to leave some for linux host
@@aa6_ I see. If so, does that mean a tweak like cpu pinning and governor not that useful in this case?
@@amsuherdi1111 doesn't make a difference, but sometimes it can help with audio issues
Does this guide still hold up in 2024 ?
im confused would this work with just a single nvidia gpu and no igpu?
Its literally in the title of the video
@@xDraga yeah but the github says that the script has been tested on a dual gpu setup which makes no sense and from what ive read you still need an igpu
Is there a way to repurpose this script for setting up a hackintosh VM?
Scripts don't change. The only difference would be how you install hackintosh inside the vm.
All seems well until I need to press any key to boot CD, then it just hangs at a TianoCore logo.
You still have the problem? (Make sure you vm drive is enabled in boot options, inside of virt-manager)
Sorry for late reply.
Hey your link to the gitlab is down can you please update it ? Thank you for the video
try this gitlab.com/risingprismtv/single-gpu-passthrough
Get your USB stick and update your BIOS, if you are unlucky it will delete your grub bootloader and your system won't boot. :/
Boot into a live disk and reinstall grub and kernel.
when running the VM im stuck at archlinux login:
the VM boots perfectly fine, but when I shutdown the VM my host just restarts, im using arch
or it could just be logging me out, I don't know how to tell
I cannot seem to access the gitlab guide. Do you have a working link?
The link in description doesn't work?
@@aa6_ I just checked again using my phone and it is now working. I did not know what happened earlier when I tried to access it using my PC.
@@aa6_ A question before I dive deep into this. Do you know if this works on Ryzen APUs? Just an APU without a discrete GPU.
@@serbaldomiro Personally I would not recommend doing something like that at all. What you're asking difficult and it's something completely different to this guide. Of course you can always give it a try, but it will give you a headache, and it might take you roughly 2 weeks or more to learn it, if you're new to this stuff. Again would not recommend. (Also I'm honestly unsure if it's even possible)
The scrip in the IOMMU section doesn't work at all in Proxmox. No outout whatsoever. I tried pasting it into Powershell, CMD Prompt, Debian11 terminal, Proxmox shell and Solar PuTTy (SSH:d to my Proxmox host ofc). I also tried to make it into bash script, but that doesn't output anything either. I ended up using lspci -v in the end because I couldn't figure out how to get that script to work. I'm sure the solution is something very simple, but I'm very much a beginner with Linux trying to get into Proxmox out of necessity.
can you run this in terminal,
( dmesg | grep -e DMAR -e IOMMU ).
Usually when the Iommu script doesn't work it means that iommu is disabled. You might need to google how to enable it for proxmox.
@@aa6_ Thank you so much! Idk what happened while I was trying various things but somehow I had disabled IOMMU in Proxmox at some point. Now it works. I did however stumple on another way of doing what that script does: for g in /sys/kernel/iommu_groups/*; do echo "IOMMU Group ${g##*/}:"; for d in $g/devices/*; do echo -e "\t$(lspci -nns ${d##*/})"; done; done; As far as I can tell, it does the exact same thing, but works even if IOMMU is disabled which is bad when figuring out how to configure PCIe passthrough. Also something to note for Proxmox users: When installing okteta it's just sudo apt-get install okteta No need to mess with snap. Which fails to install KDE Frameworks 100% of the time, at least on Debian and Proxmox, making installing Okteta impossible.
@@VilleF1N happy to hear it worked 😀
can you help me ihave ps4 linux and windows vm work on qemu but i have problem with gpu like you
You're doing this on a PS4?
@@aa6_yes
@@fdfffgf2475 I don't think it is possible to do it on the ps4 🤔
im using endeavourOS hope it will work
New imsges of windows 10 add something called watchdog and thats causing problems the forst time i followed the guide i used an old iso w10. And it was detected as such the latest isos of w10 get detected as w11 and get the watchdog
whats watchdog?
Hi, have you found a workaround for it? I tried disabling it but still messes with display connection. Been thinking on trying an older win10 iso, but im afraid that with driver updates, it will add watchdog to its kernel again.
@@jaimegonzalez7770 it took me five days to realize that I had to rename windows 11 to win 10 for the scripts to work
yeah not sure if this is why but the guide isn't working for me anymore and I'm fairly certain I did it all right.
that wiki section is gone brother lol
link is down, can you please provide a new one?
Nevermind, replaced it with "risingprismtv/single-gpu-passthrough" and worked, as someone suggested in the comments down below.
Thank you for you effort.
@سعُود glad it worked 👍
it worked fine but it does not return to the host , only Power off system.
My bad for the late reply. Have you checked logs?
@@aa6_ no problem, Works Fine , is possible return to host, without turnoff guest?
@@Xongasbr what?
@@Xongasbr you can return to host only while turning off guest, the second way is to have dedicated gpu for host and dedicated gpu for guest, since when you start the guest host will lose gpu access ...
This probably is an issue with the teardown script, at the "Rebinding consoles" section at the end, just comment it out and you should be returning to your host
This is an issue that needs to be fixed in the scripts
Putting this here for future references
Man I just want to read VNs without lag. I think I'm going to keep reading them at 30-45fps on a vm
I usually just run them through Wine and it works fine for the most part. Only once I had a trouble with font rendering and installing some fonts fixed it.
If you're using like the tutorial, look into CPU pinning
Same some stuff is so poorly supported through proton and wine that you don't really have any other option. I've been trying to read ever17 on a vm and it runs like hot ass.
I am in the folder containing the nvflash
modeprobe -r wont stop the modules on arch
Your command for stopping them don't work either
uninstall nvidia, nvflash, then reinstall
@@orangedullness2268 u didnt do anything with selinux right?
check on yur system by runing sudo getenforce
I wish people would stop posting these guides not a single one of them work with a single GPU, they all require 2 DGPUs.
Bro, still is literally for 1 dgpu.
@@aa6_ A guide that doesn't work is worse than useless. It takes time & views from guides that do actually work.
@@ericneo2 I have no clue what your problem is, but I can guarantee you that this works.
My teardown hook doesn't even work. DAMN
Sorry for late reply.
Are you still having issues with the teardown?
@@aa6_ yeah
@Lameless are you using an amd gpu? If so, open the teardown script and delete everything in the rebind console section. Should do the trick for amd.
If that didn't fix it or you are using a nvidia gpu, check the Windows log file. At the very bottom of that file, check if it says something along the lines of "could not reset group" or
"group is not owned"
It basically says what extra group it needs to be able to reset a device.
If that still doesn't fix it, feel free to join discord
@@aa6_ would I keep echo "$DATE End of Teardown!"?
@@Lameless yes keep that
The discord needs phone verification thats dumb. Please don't promote phone physing websites
We had problems with bot users in the past. There is nothing else we can do about it.
I got BSOD while booting the windows iso to install, lmao
What distro are you using?
@@aa6_ EndevourOS
I think it is some CPU issue, with the version of Win10 iso am using, it doesn't work with Host Cpu Config, so you have to turn it off and then install the spyware OS
@@Gre3k What version of windows iso are you using?
This guide completely wasted my time. I get to the end just to keep getting repeated errors when adding the info to the xml file in the end because I’m using an nvidia card on a laptop. PLUS THE OWNER OF THIS CHANNEL SKIPS OVER THIS PART AND DOESNT EVEN SHOW AN EXAMPLE.
thanks for the heads up.
You know that a Discord is both mentioned in the video and the description? You are welcome to join it and ask for further help in it
Thanks for paying attention to the video unlike someone :D
If you still want to try, go check out discord.
Thank you very much. I did it.
And AMD CPU just need to add
/etc/modprobe.d/kvm.conf
options kvm ignore_msrs=1
It's help to install windows 10 LTSC
( I remove my PCIE-wifi-network-card, it's kind of issues temporarily）
Great to hear :)
If you still have any issues, you can ask in discord.
I'm getting a black screen no matter what
03/31/2024 16:29:58 : Beginning of Startup!
03/31/2024 16:29:58 : Display Manager is not KDE!
03/31/2024 16:29:58 : Distro is using Systemd
03/31/2024 16:29:58 : Display Manager = gdm
03/31/2024 16:29:58 : Unbinding Console 1
2b:00.0 VGA compatible controller [0300]: NVIDIA Corporation GA104 [GeForce RTX 3070 Ti] [10de:2482] (rev a1)
03/31/2024 16:29:58 : System has an NVIDIA GPU
/usr/local/bin/vfio-startup: line 123: echo: write error: No such device
modprobe: FATAL: Module drm_kms_helper is builtin.
modprobe: FATAL: Module drm is builtin.
03/31/2024 16:29:58 : NVIDIA GPU Drivers Unloaded
03/31/2024 16:29:58 : End of Startup!
03/31/2024 16:30:05 : Beginning of Teardown!
03/31/2024 16:30:05 : Loading NVIDIA GPU Drivers
modprobe: ERROR: could not insert 'nvidia': No such device
modprobe: ERROR: could not insert 'nvidia_modeset': No such device
modprobe: ERROR: could not insert 'nvidia_drm': No such device
modprobe: ERROR: could not insert 'nvidia_uvm': No such device
03/31/2024 16:30:05 : NVIDIA GPU Drivers Loaded
yur gpu failed to unbind from the linux host because there are processes that still use the gpu
u need to mke sure that all gpu relied processess and services are closed before unbidning
by modifying yur script
why is this so much work tho
Just is.
@@aa6_ it shouldn't be :p hope it will be easier in the future so people that don't like spending time configuring pc can hop to Linux. Very promising tech otherwise.
@@skimmingdeath Best I can do is 15min setup process. Copy-pasting configurations from the internet is error prone and not very user friendly. I feel like in the end if you want to expose any functionality to users it should be as easy as installing app and then few keys away, not 50min guide :P I didn't mean 'easy' as 'easy to do', more like 'simple and quick process'. If your bar for 'easy' is 'just follow this 50min guide' then we might just disagree about the word ^_^
Please help when I save the rom via nvflash (Sudo ./nvflash --save rtx4090.rom) it gives a error (.nvflash: 1: Syntax error: word unexpected (expecting ")")) I run Linux Mint
You still having issues? Sorry for late reply.
@@aa6_ u didnt do anything with selinux right regarding VFIO single gpu passtrhough?
It looks like the correct link is
risingprismtv/single-gpu-passthrough
not
risingprism/single-gpu-passthrough
Interesting 🤔, but it turns out it's just the same link at the end of the day.
@@aa6_ try to visit it being loged out of gitlab
@ScrewThursdays oh well in my case both links work. Hopefully, one works for you.
"BtW i UsE aRcH "
i use arch btw
Arch btw i use
Arch is pretty good but I mostly use Ubuntu (expected to get random hate for it)
Real
Wow what a coincidence. I too use Arch BTW