@@suspiciousstew1169 Ah yes, msi's bios updates, which for some reason wipes the NVRAM of the uefi, even though that part has shit to do with the actual update. Fucking grade A engineering right there. Anyways, if you need a solution, get a live usb and chroot into the drive, then run efibootmgr. Can't remember the full command right now, but it boils down to you selecting what disk your efi part is, what partition it is, and the path to the efi executable, relative to efi part root, and the last argument is the name of the nvram entry, you can call it whatever.
Great video! Just wanted to mention that single GPU passthrough (as in only having one GPU in the entire system) is also viable and works pretty well, even though it's recommended to set up qemu hooks to detach and attach the GPU while system is running to avoid hassle.
@@offset.5727 Yep, since when you detach you use a command where you need to specify the PCIE device id, something like: _virsh nodedev-detach pci_0000_0a_00_0_
Dumb question: where do you plug your monitor's video cable, if, say you have an iGPU and a dGPU? How would the iGPU work if you plugged it into the video card? (I only have one dedicated GPU, so I can't go and check)
Mad props from a long-time viewer for trying to help out in intermediate level Linux/VM stuff! ;o) -- I agree, virt-manager GPU passthru can be a hassle to set up (even with an instruction video like this), but can be used for so many cool stuff, just as you described. Sadly, some games nowadays have VM detection and blocking in their anti-cheat systems (due to i.e. farmbotting etc.), so just having a GPU pass-through might not work with every game -- that is, unless you've got low-level hypervisor support on your motherboard (i.e. Hyper-V), have it enabled for the CPU architecture as well from your UEFI/BIOS menu, and use that to pass-through your architecture (=CPU & motherboard topology) in virt-manager, which also makes things obviously way faster, but might come with some risks, such as Virtual Machine Escape (see Wikipedia article under that title, also the "Hyperjacking" article for VM risks). So, a word of caution on what you should run with those. You didn't mention Hyper-V (probably because it can be enough of a subject for a video of its own?), but it's also definitely worth looking into. If bare metal-level performance is what you're after, then it's Hyper-V + GPU-passthrough FTW. On the PCI(e) graphics pass-through frontier, there's been some developments in other adaptations like Looking Glass that you might want to look into (they have their own website & wiki), although I must say idk about the current status of the project and what caveats it might have. As others pointed out, there's many tweaks to a VM in virt-manager that might make it way faster (enabling xmp), even stuff like RNG (/dev/random, /dev/urandom) hardware passthru is recommended to be set up correctly for faster performance (albeit the more you let things pass through the hardware, the more hypothetical security risks there _might_ be). Then again, if you're running a few pieces of legit software on the Windows side, shouldn't be too concerning. Anyway. I recommend looking up Looking Glass and into Hyper-V and other bells 'n' whistles 'n' other Gyro Gearloose-doohickey-options in virt-manager to make your VM run faster. Thank you, have a great day!
I literally spent all of last week trying to figuring this out. Now, you post the video that solved my problems with the driver loading too fast for my GPU.
Hey, just wanted to say I really like what this guide set out to do - because it covers a lot in a very comprehensive way, but having done this myself before, there can be a lot of gotchas and caveats with doing this. I just want to point some of those out because I think a lot of people who may be attempting to try this off this video alone are going to hit walls. - To actually use the GPU for gaming (not just compute tasks), you'll need to hook a seperate monitor into the gpu. I can't remember if I *needed* to disable the virtio display as well but I'm pretty sure I did. This goes for almost any hardware passthrough - it will steal the device from the host system, so you'll either need a second keyboard/mouse/usb controller/sound device OR a KVM switch. Basically it's like running two computers off one computer. Alternatively you can use a low latency remote application, but there are compromises there too. - There's something you may need to add to your xml config so that you can avoid error 43 in device manager (also get around "most" anti VM drm on games) - The video card needs it be in its own IOMMU group unless you attempt a complicated workaround (if you only have a motherboard that supports 1 gpu and no iGPU, you may not be able to pull this method off). I recommend anyone doing this has a AMD Threadripper or Intel-X workstation motherboard - it's not just about the number of physical slots. Some lower end boards will work but it may require a totally different method. Personally I can say VirtManager/IOMMU is probably the best way to get to the metal performance VMs, especially on arch. But I had quite a bit of difficulty using it as a daily driver. I ultimately decided to build an ESXI server for virtualization, even though arch is really really cool. Performance wise it's the best and I even like virtmanager's software acceleration better than VMwares. But it can get convoluted really quick and I don't think I had the linux chops to troubleshoot all the little details and hiccups I was experiencing.
@@jotsa The passthrough will technically work as-is because your VM will have the GPU installed - and that definitely has use cases even without the direct connection to it. My understanding is that you're still using the Virtio QXL Drivers for the display that's built into virtmanager/QEMU (it's the one in device manager that shows up as Red Hat QXL controller). Therefor it's still doing a majority of the work in applications that display on it. I could be wrong though. This was a while ago and methods change, or I just misremember. But I did have to go and buy a KVM switch to get it all working in the end. Test some games out on it and you'll know for sure.
@@jotsa Hmm, I guess it'd be worth me revisiting in the future then. I could never get that working properly. I had to basically stick with 1 gpu per system. But it was basically bare metal.
That's not 100% true. There is a way to have one GPU, one monitor and single keyboard+mouse and have GPU passthrough. I've set up my PC like that a long time ago and it works. One caveat is that when using this setup, you can't simultaneously use your Linux and Windows, it's either one or another cause here, when you start your VM, you kill your X (or any other UI), then VM starts up and steals your GPU and Windows boots. One thing with this is that when something crashes (even your keyboard or mouse will not setup properly), you won't be able to control VM or in worse case, you'll need to reset your whole PC, because something broke, your GUI didn't start and you ended up with black screen. I've tried using GPU passthrough with two GPUs inside PC, but then (because I chose wrong MoBo) I was able to pass only secondary GPU and having 5700XT on a, IIRC, 1x PCIe sounded very, very bad. So that's when I've found single GPU passthrough.
You can do many of the things in this video and in others pretty much as is, with most consumer boards. I have at least 3 different x370/x570 boards that had zero issue with actually passing thru, but some gotchas that kept it from working till I configured either Linux or scripts or the dreaded ACS patch. As long as windows is installed it acts like a regular windows install, no crazy bs. And for what its worth, its been super stable for what I do, multiple pcie devices passthru and when it works it works excellently. Just need a board for later that has proper iommu groups.
This is a great guide since you also provide the reasons for doing certain things, which some guides leave out for some reason or leave unclear. Thanks!!
If this process was easier, more streamlined, and friendly for new linux users we would get a lot more people in the linux desktop world. I couldn't do this on a laptop on somebody and he went back to Windows. Oh well. This is one of the best videos i've ever seen, Mr. kenny outlaw
"If this process was easier, more streamlined, and friendly for new linux users we would get a lot more people in the linux desktop world." Unfortunately, this is true for waay to many things about Linux :/
i tried this but i am apparently too dumb. i just have a second disk for my winders install for the few games that require easy anticheat with no support on linux.
I plan on upgrading my PC later on this year once the RX7000 cards release, thanks for making the vid since theres a definite lack of full video guides on this topic
Now if you take the extra steps to make it think it's bare metal and enable Hyper-V in Windows it will enable Virtualization and confuse any anti-cheats into thinking you're not on a VM. I've used this method before to play things like Escape From Tarkov but games like Valorant with their root kit anti-cheat may be a bit more annoying to deal with.
Actually that same method works for Valorant last I knew but you need to add a couple flags to the vm xml as well. I don’t know if that still works but it did for a while. Haven’t looked into it recently. Most all anticheats run on the kernel level just that Vanguard goes to far in running 24/7.
You can get games like valorant to work but that requires you to either really know what you’re doing or be constantly kept up with whatever esoteric black magic workaround the vm gaming community has found for the most recent version of the game
@@gayusschwulius8490 Unless it is one of those fancy rootkits that uses some instruction that is slower on a vm. There's a way to spoof that too, but you need to compile the kernel with some modifications
Been doing this for about a year now with a Displayport KVM switch, works great! and I recommend just using two Logitech Unifying dongles with mouse and keyboard that allow easy device switching. I also passthrough a PCIe wifi card and usb card to get reliable direct access.
I tried adding a PCIe sata card to mine for hard drives, but whenever i try and boot with it my host crashes. Any words of wisdom? GPU passthrough working fine on it from what I can tell.
recently started test driving linux with the idea of keeping a windows install on another ssd but using it with a vm inside Linux. I was going to use virtualbox until I saw your video about how to use qemu/kvm, so I decided to do that instead. got it all working and then realized I need gpu passthrough. only a couple days later you release this video. thanks for reading my mind
For those using Proxmox, there are some great guides out there as well. This video is pretty close to what you need anyway. I got my GTX1060 passed through to a Windows 10 VM and works great.
I've noticed, your RAM is still running at stock speed, might want to enable the XMP profile or overclock the RAM yourself, otherwise you are probably leaving performance on the table. Ryzen/Threadripper really benefits from higher RAM clocks. Thanks for the guide though, been wanting to do this for a while.
As much as I appreciate you doing this video, this is *NOT* "single GPU passthrough". Yes you just passing through one GPU of your system, but you have two in there. The goal of single GPU passthrough is, that you are passing your one and only GPU through to the VM and get back into your linux system after playing or whatever you might need Windows for. You title does not suggest "single", but you are saying it a lot. The comment also asked for "single". Although most of the steps are kinda the same, passing the GPU that you are currently using in Linux through to Windows and getting back to Linux safely is much more complicated and fiddlely. It would be great, if you'd cover that, too, though 😉
Nvidia usually, usually, is going to be easy in and out, where as amd might present problems depend on which generation you have. I believe the newer cards are less problematic but might still have the reset bug of which you can alleviate in windows by setting the device to be enabled and disabled via a scheduled task. I don't have any issue with my r9 380 but my wx7100 gave me so much shit for the longest time, but I did the task schedule script and it work like magic. But there's always a gotcha somewhere that makes this more a bitch than it should be.
@@battokizu Could you explain a bit more? I'm trying to do the same thing but with a w4100, so I'm guessing the troubleshooting would be very similar to what you're doing.
@@askiiart It's been a bit since I've actually set up the system, aside from setting up virt-manager in manjaro, I don't remember what actually got the passthru working. I have that system still available so I'll update my comment if I see anything that I did that might help you out. But I do have to ask what specific issue are you having? Or what step are you on that is still causing issue.
@@askiiart no problem, we're all busy with stuff. Sorry to hear that, you should be able to get a cheap Asus x570 mobo and have no issues, if your intel or on some older platform that doesn't have support, which might be the case on Intel's side of things and amd pre ryzen. But anyhow used motherboards and cpus aren't the worst thing you can invest in if you really want to experiment with iommu.
Damn dude, u da GOAT! Did some quick lookups and got this up with an amd card. Also got the usb 3.2 card up right off. Incredible. Casual user who only watched some vids about pass through before doing it. Got games going. Got professional software going. Amazing.
Well explained! Just to note, if you have only one gpu u wanna passthrough, this is still possible as "single gpu passthrough". Might be useful in specific cases. With proxmox for example u get a web interface for the host, have the single gpu free for vms. As long as you have ssh or cockpit or anything available, it works with any distro.
Hey bud I know this is 6 months old comment but yeah you can totally do single gpu passthrough but it adds step in the process like building a hook so the graphics card gets picked up when vm is launching and it does require also the bios file for the graphics card. You can find single GPU pcie passthrough guide on youtube
Just a couple of things, this is not a single pass-through, in single gpus pass-through you detach your one and only gpu from the host and pass it to the guest, and another point is, sure windows reconized your gpu, but if you try any games in the state you ended up in this video it will not be accelerated by the card you passed through, but by RedHats virtual display adapter, if you want to use the 1080ti in all its glory you need to remove any other video devices from the hardware options on virtmanager and connect a monitor to your 1080ti to get its video out or setup a looking glass capture (but that requires a dummy plug on the 1080ti i think)
@@VladTepesVEVO No. The preferred method is to have another GPU. It removes a lot of the headache. If you only have one gpu it requires a lot more work and will probably have more issues as well.
@@warhawk_yt Yea that's what I meant with SLI, having at least more than 1 physical GPU installed on your rig. Maybe even different brands, an AMD GPU on the host OS and an Nvidia GPU for VFIO purposes.
For someone who finds this video, amd_iommu=on is not a valid value. You can safely leave this out entirely for newer kernels/cpus; the default value is generally what you want.
This is EXACTLY what I needed! To decide to go and keep on using dual boot. Wasted the better part of my day yesterday trying to get GPU and USB devices to work properly on virtualbox; then installed virt-manager with Qemu/Kvm and faced similar problems. Today I say no, NO MORE! I'm done! xD Anyway, the only thing I can't do better on linux is play driving game with a sim wheel; so why bother. (Yeah it does work, the ffb is just dreadfuly bad compared to windows)
Thanks again! After follow the last tutorial and getting rid of virtual box, I did look into GPU passthrough on my laptop, but got scared a bit and postponed it for later. this helps a lot, but for decent gaming, I think spice isn't fast enough, and it looks like the solution is something called "looking glass". (since I don't want to haul another monitor with my laptop.) Also I still haven't found any methods that suggest an elegant way of switching the display between the host and guest OS. I wish we could just press alt+ctrl+f1 and f2 to use different ttys to switch seamlessly!
[11:00] You can simply blacklist "nvidia" module, so it won't be loaded, if your second VGA is not nvidia-based, obviously. KVM/QEMU/libvirt don't need "nvidia" kernel module to function, you install nvidia drivers inside windows guest os instead.
hey man sorry to bother you so late, how do i blacklist the nvidia drivers on bootup? currently im using them and im on arch but im wanting to make it so my linux is using my iGPU esclusively now so i can use looking glass and nvidia on windows. t hanks
GPU passthrough is something that interests me a lot. Unfortunately, I set up the passthrough, but the multiplayer games that I wanted to play would simply not let me do it cause their anti-cheat doesn't allow VMs.
I used to have a windows VM just for this one game, but the anti-cheat started to block VM's so I just started to patch out the anti-cheat. It works even better on wine than on a VM so I guess I'll keep doing it this way.
@@kxuydhj excuse me, does this work on pubg? cos their anti-cheat is hardbanning linux :( I would really dive into gpu passthrough if this was possible.
What steps do you need to do, if you want to passthrough sometimes, but also use the gpu with the host system sometimes? Could you make everything in "/etc/modprobe.d/vfia.conf" a comment (#), run "mkinitcpio -p linux" after and reboot?
The success of pass-through setup highly dependent on hardware, like on CPU, chipset, BIOS, VGA, etc. Also, for quite some time nvidia refused to patch their drivers so they could be installed and function correctly within VM guest OS. Too many things to track, many issues were patched over the years, and this pass-through setup really works well on modern hardware.
If your mobo's iommu groups aren't designed properly, it's hard to passthrough what you want without affecting something else. This typically leads to a hard lock requiring a reboot. It's especially bad if your VMs auto start.
THANK you for this, this helped a lot. could you please make a video about how to hide the fact that youre using a vm? so that you're able to play online games like cs and valorant without getting banned. that would be awesome, great content regardless!
th-cam.com/video/L1JCCdo1bG4/w-d-xo.html I introduce you to Mutahar. This guy knows his VMs and makes guides on how to bypass Anti-Cheats on VMs. Really worth checking this video out.
sadly it's a difficult thing to do, vm detection on anticheats are always improving. one way to hide that fact is adding kvm state hidden to your XML config and also enable HyperV completely in Windows. it worked for me with r6, for ~2 months after a battleye patch it doesn't work now :(. good luck with that and if you manage to do that sharing your solution would be appreciated! also check out muta's (someordinarygamers) channel, he used to talk about gaming vms, bypassing vm blocks.
If I ever manage to get another GPU I'll have to try this set-up. Would love to see my VR rig working in a VM, Windows is genuinely awful to use all the time.
For those confused about what outlaw is doing with grub hes just editing kernel parameters. If you need it for systemd-boot you can use the file path /etc/boot/loader then go to the main config file and add the same test hes typing in the options section.
Thank you for covering this, @MO. Yes, this is a very hard thing to find the steps on the web. I plan to do this very soon, because I just had another windows update went and borked my system. It really fucked up my Office 2010 apps (like Word) and now it won't load. And, it took hours to figure out what went wrong and get it so that Office would load correctly; and, even still, some of my add-in, purchased software doesn't work yet. So, I've got to virtualize windows and eliminate these problems.
Fun Fact: My older friend, who got me into linux fried his system trying to make an NVIDIA passthrough Edit: Fried his system as in fried his linux install
Very good tutorial, I just set this up a few months ago for a Mac VM I needed for an IOS app I am developing and this would have saved me a lot of headache. There are still a few extra steps if you are doing Mac VM, but these are a good enough just to get your windows machine up and running
@@unreleasedjuicewrld9792 you need to rip it from a machine running macOS. Just go to your local computer shop and do it there if you dont have one. There are tutorials online.
"Sudo reboot"?! What're you doing? Lol "shutdown -r now" man, never use sudo unless absolutely necessary 😜 Glad you made this one, virtualization is gonna be the next big thing with so many cores and ram being standard these days.
Great video. Maybe good to tell at the start that the sytem must have 2 graphics card... :) Now I have 2 identical vendor/model GPUs, Both show the same IDs... How can I then isolate one from the other? Can I use the first nunbers on the line? In your situation it would be "01:00.0" for the 1080 Ti and 01:00.1 for its audio device. How?
Anyone attempting this, do make sure you have a fuck-ton of free time to solve the random bugs you will encounter, there are an absurd amount of gotchas you can hit, and then there is PCI-E communication standards hardware manufacturers failed to implement, and, if you run into that you probably won't be able to get anything running reliably without replacing hardware. This entire thing will likely not be a single weekend project.
it is very funny that while he talks about how hard it is to install drivers on windows, windows just installs the driver in the background without him even noticing. But still great video love you content.
The problem with that, is that this is no-where near dynamic. For example, I use a CAD software that is windows only, but want to render my videos on native Linux. If it was dynamic, for example passing the card only when VM is run, then I could see much usefulness out of this. Else, dual boot is the way to go, but dual boot has the very bad tendency to make you lazy with switching, and you end up giving Microsoft more time than you want. 😕
Before I go ahead and get a second gpu to do this, can you answer a quick question. When playing games on the windows vm with gpu pass-through, do you have to connect your monitors to the gpu in question, or can you play in the vm window?
@@aidamon6170 yes, I did. You have to connect one of your monitors to the gpu in question, and than switch the input source to that GPU to be able to play games
if you get error 43 when installing nvidia drivers go into your vm options, go to the "Overview" tab and click on XML, scroll down to and somewhere in there add the line
Awesome! You missed one thing tho. The Audio Controller must be a subdevice of the GPU. If you don't the two devices will show up to the os as being 2 different PCI devices on two different buses. Because of that my AMD GPU driver freaked out. Unfortunately you'll need to edit the XML for that but that's not hard with Virt-Manager.
When I go to start the VM, I get the error "please ensure all devices within the iommu_group are bound to their vfio bus driver". Does anyone know what causes this problem?
Nice video Kenny. Do you know how to set the vfio PCI ID if you've got two identical video cards? Can you identify the cards by PCI Bus ID instead? 01:00.0 and 01:00.1 in your example.
Please correct me if I'm wrong. I have only 1 monitor meaning I will have to connect that monitor to integrated graphics and then use discrete graphics for the virtual machine otherwise I will become unable to do anything on the host while virtual machine is running.
I have followed every step, and I still see the nouveau drivers for my nvidia card loaded and my hda_intel sound modules loaded for the sound card part of it. I followed your steps exactly..
I remember I took the plunge around 4 years ago, took about a month to get a GPU passthrough all set up only to run into the AMD SMT CPU performance bug, give up, reinstall Windows and after a week afterwards I read that the bug was fixed shortly after I switched back. Is another monitor for the VM or Looking Glass no longer required? Is audio still dodgey?
During the first reboot right after editing the /etc/default/grub my machine won't boot or even show an error! Just a blank screen doest even recognize Linux, anyone else had this problem?
Hi Mental Outlaw, I love your channel. I would very much like to see a video on CPU pinning for use in a VM please. Also, what's the best way to contact you? I could do with advice on a desktop build I'm planning. I'm willing to pay for your time. A lot of my questions are follow-up questions to things I've learnt from your videos, but it would be easier to put my questions to you in one place rather than break them up into individual video comments. Many thanks. :)
if you need a second GPU, do you need a second display to connect that GPU? I have the impression that you need an extra monitor if you want to do this thing
i didn't see you change the gpu output, you changed the output correct,? and what we see on your screen is the output from your passthrough graphics connected via a different hdmi?
So how it is working in detail ? You have connected Your display to some motherboard gpu (INTEL etc.etc.) and Windows System using dedicated PCIE Nvidia ? If yes, then You are streaming picture rendered by nvidia and display via motherboard gpu . What about quality of that stream ? Did You observed some moments with low quality picture ? video compression etc.etc. ?
As much as I'd like to do a gpu pass-through the electricity prices where i live are horrendous, I would need to buy a new power supply (considering what the second gpu would need power-wise) and it's just not worth it, since waiting for the virtual machine to boot takes as long as rebooting into my windows partition instead where I could instead also use my better graphics card that I already have built-in rn (RX 6800 XT) Still a good tutorial for those who are not limited by what I mentioned or were considering it anyway and just needed a better tutorial to actually get started on it
If using windows I would prefer to not run it on bare metal. Although for me it would be interesting enough to have dedicated graphics inside of a Linux vm.
after rebooting when having done the grub config stuff im stuck in what i think is a boot loop it just keeps initializing the same things then failing on a million things and starting over. im using a laptop running linux mint cinnamon 21 btw this has happened once and when it did i reinstalled the entire os but now i wanted to see if i missed a step and i cant seem to find anything that i missed so here i am afraid to reboot cuz im almost certain the same thing will happen again... what do i do? fyi the "quiet" option was enabled and i disabled it along with some option called "splash". is this the splash screen at bootup or is it important and should i not mess with it? for now i have simply removed the commands by commenting them for later and rebuilt grub in the way shown through the video
Hi Kenny tried this but cannot seem to stop the Quadro from loading nouveaux VGA compatible controller: NVIDIA Corporation GF106GL [Quadro 2000] (rev a1) Host is using a seperate amd gpu card. there is no onboard graphics Subsystem: Hewlett-Packard Company Device 084a Kernel modules: nouveau tried blacklisting but hasnt worked
Remember kids, when using windows always use protection, use a VM.
don't forget to use windows 10 debloater to remove the telemetry and other bloatware
@@suspiciousstew1169
Ah yes, msi's bios updates, which for some reason wipes the NVRAM of the uefi, even though that part has shit to do with the actual update. Fucking grade A engineering right there.
Anyways, if you need a solution, get a live usb and chroot into the drive, then run efibootmgr. Can't remember the full command right now, but it boils down to you selecting what disk your efi part is, what partition it is, and the path to the efi executable, relative to efi part root, and the last argument is the name of the nvram entry, you can call it whatever.
thamks
@Not Convinced yes, windows has the best keylogger undetectable by any antivirus (why people even use antiviruses ?)
... and if he complains and want to enter from the front door, you have the right to say no.
Great video! Just wanted to mention that single GPU passthrough (as in only having one GPU in the entire system) is also viable and works pretty well, even though it's recommended to set up qemu hooks to detach and attach the GPU while system is running to avoid hassle.
How does that work? Does the Linux machine become headless while the VM is in control?
@@AROAH yes
can you use this method with 2 gpus? like hooking one and leaving the other for the host or is normal vfio easier?
@@offset.5727 Yep, since when you detach you use a command where you need to specify the PCIE device id, something like: _virsh nodedev-detach pci_0000_0a_00_0_
Dumb question: where do you plug your monitor's video cable, if, say you have an iGPU and a dGPU? How would the iGPU work if you plugged it into the video card?
(I only have one dedicated GPU, so I can't go and check)
Mad props from a long-time viewer for trying to help out in intermediate level Linux/VM stuff! ;o) -- I agree, virt-manager GPU passthru can be a hassle to set up (even with an instruction video like this), but can be used for so many cool stuff, just as you described. Sadly, some games nowadays have VM detection and blocking in their anti-cheat systems (due to i.e. farmbotting etc.), so just having a GPU pass-through might not work with every game -- that is, unless you've got low-level hypervisor support on your motherboard (i.e. Hyper-V), have it enabled for the CPU architecture as well from your UEFI/BIOS menu, and use that to pass-through your architecture (=CPU & motherboard topology) in virt-manager, which also makes things obviously way faster, but might come with some risks, such as Virtual Machine Escape (see Wikipedia article under that title, also the "Hyperjacking" article for VM risks). So, a word of caution on what you should run with those. You didn't mention Hyper-V (probably because it can be enough of a subject for a video of its own?), but it's also definitely worth looking into. If bare metal-level performance is what you're after, then it's Hyper-V + GPU-passthrough FTW. On the PCI(e) graphics pass-through frontier, there's been some developments in other adaptations like Looking Glass that you might want to look into (they have their own website & wiki), although I must say idk about the current status of the project and what caveats it might have. As others pointed out, there's many tweaks to a VM in virt-manager that might make it way faster (enabling xmp), even stuff like RNG (/dev/random, /dev/urandom) hardware passthru is recommended to be set up correctly for faster performance (albeit the more you let things pass through the hardware, the more hypothetical security risks there _might_ be). Then again, if you're running a few pieces of legit software on the Windows side, shouldn't be too concerning. Anyway. I recommend looking up Looking Glass and into Hyper-V and other bells 'n' whistles 'n' other Gyro Gearloose-doohickey-options in virt-manager to make your VM run faster. Thank you, have a great day!
I literally spent all of last week trying to figuring this out. Now, you post the video that solved my problems with the driver loading too fast for my GPU.
Hey, just wanted to say I really like what this guide set out to do - because it covers a lot in a very comprehensive way, but having done this myself before, there can be a lot of gotchas and caveats with doing this. I just want to point some of those out because I think a lot of people who may be attempting to try this off this video alone are going to hit walls.
- To actually use the GPU for gaming (not just compute tasks), you'll need to hook a seperate monitor into the gpu. I can't remember if I *needed* to disable the virtio display as well but I'm pretty sure I did. This goes for almost any hardware passthrough - it will steal the device from the host system, so you'll either need a second keyboard/mouse/usb controller/sound device OR a KVM switch. Basically it's like running two computers off one computer. Alternatively you can use a low latency remote application, but there are compromises there too.
- There's something you may need to add to your xml config so that you can avoid error 43 in device manager (also get around "most" anti VM drm on games)
- The video card needs it be in its own IOMMU group unless you attempt a complicated workaround (if you only have a motherboard that supports 1 gpu and no iGPU, you may not be able to pull this method off). I recommend anyone doing this has a AMD Threadripper or Intel-X workstation motherboard - it's not just about the number of physical slots. Some lower end boards will work but it may require a totally different method.
Personally I can say VirtManager/IOMMU is probably the best way to get to the metal performance VMs, especially on arch. But I had quite a bit of difficulty using it as a daily driver. I ultimately decided to build an ESXI server for virtualization, even though arch is really really cool. Performance wise it's the best and I even like virtmanager's software acceleration better than VMwares. But it can get convoluted really quick and I don't think I had the linux chops to troubleshoot all the little details and hiccups I was experiencing.
@@jotsa The passthrough will technically work as-is because your VM will have the GPU installed - and that definitely has use cases even without the direct connection to it. My understanding is that you're still using the Virtio QXL Drivers for the display that's built into virtmanager/QEMU (it's the one in device manager that shows up as Red Hat QXL controller). Therefor it's still doing a majority of the work in applications that display on it.
I could be wrong though. This was a while ago and methods change, or I just misremember. But I did have to go and buy a KVM switch to get it all working in the end. Test some games out on it and you'll know for sure.
@@jotsa Hmm, I guess it'd be worth me revisiting in the future then. I could never get that working properly. I had to basically stick with 1 gpu per system. But it was basically bare metal.
That's not 100% true. There is a way to have one GPU, one monitor and single keyboard+mouse and have GPU passthrough. I've set up my PC like that a long time ago and it works.
One caveat is that when using this setup, you can't simultaneously use your Linux and Windows, it's either one or another cause here, when you start your VM, you kill your X (or any other UI), then VM starts up and steals your GPU and Windows boots. One thing with this is that when something crashes (even your keyboard or mouse will not setup properly), you won't be able to control VM or in worse case, you'll need to reset your whole PC, because something broke, your GUI didn't start and you ended up with black screen.
I've tried using GPU passthrough with two GPUs inside PC, but then (because I chose wrong MoBo) I was able to pass only secondary GPU and having 5700XT on a, IIRC, 1x PCIe sounded very, very bad. So that's when I've found single GPU passthrough.
You can do many of the things in this video and in others pretty much as is, with most consumer boards. I have at least 3 different x370/x570 boards that had zero issue with actually passing thru, but some gotchas that kept it from working till I configured either Linux or scripts or the dreaded ACS patch.
As long as windows is installed it acts like a regular windows install, no crazy bs.
And for what its worth, its been super stable for what I do, multiple pcie devices passthru and when it works it works excellently. Just need a board for later that has proper iommu groups.
@@sewertendo oh and you don't need to use the virtual display thing, you can use looking glass if you want to go "headless" in windows.
This is a great guide since you also provide the reasons for doing certain things, which some guides leave out for some reason or leave unclear.
Thanks!!
If this process was easier, more streamlined, and friendly for new linux users we would get a lot more people in the linux desktop world. I couldn't do this on a laptop on somebody and he went back to Windows. Oh well. This is one of the best videos i've ever seen, Mr. kenny outlaw
"If this process was easier, more streamlined, and friendly for new linux users we would get a lot more people in the linux desktop world." Unfortunately, this is true for waay to many things about Linux :/
i tried this but i am apparently too dumb. i just have a second disk for my winders install for the few games that require easy anticheat with no support on linux.
I plan on upgrading my PC later on this year once the RX7000 cards release, thanks for making the vid since theres a definite lack of full video guides on this topic
Now if you take the extra steps to make it think it's bare metal and enable Hyper-V in Windows it will enable Virtualization and confuse any anti-cheats into thinking you're not on a VM. I've used this method before to play things like Escape From Tarkov but games like Valorant with their root kit anti-cheat may be a bit more annoying to deal with.
Actually that same method works for Valorant last I knew but you need to add a couple flags to the vm xml as well. I don’t know if that still works but it did for a while. Haven’t looked into it recently. Most all anticheats run on the kernel level just that Vanguard goes to far in running 24/7.
You can get games like valorant to work but that requires you to either really know what you’re doing or be constantly kept up with whatever esoteric black magic workaround the vm gaming community has found for the most recent version of the game
@@D00000T it's not that hard, usually spoofing hwids is all it takes. There's little they can do about it.
@@gayusschwulius8490 Unless it is one of those fancy rootkits that uses some instruction that is slower on a vm. There's a way to spoof that too, but you need to compile the kernel with some modifications
I believe Valorant and Rainbow Six Siege already patched this out
Thanks for this simple guide. Now I can actually run all the proprietary software my college requires me to use without compromising my system!
Been doing this for about a year now with a Displayport KVM switch, works great! and I recommend just using two Logitech Unifying dongles with mouse and keyboard that allow easy device switching. I also passthrough a PCIe wifi card and usb card to get reliable direct access.
I tried adding a PCIe sata card to mine for hard drives, but whenever i try and boot with it my host crashes. Any words of wisdom? GPU passthrough working fine on it from what I can tell.
recently started test driving linux with the idea of keeping a windows install on another ssd but using it with a vm inside Linux. I was going to use virtualbox until I saw your video about how to use qemu/kvm, so I decided to do that instead. got it all working and then realized I need gpu passthrough. only a couple days later you release this video. thanks for reading my mind
For those using Proxmox, there are some great guides out there as well. This video is pretty close to what you need anyway. I got my GTX1060 passed through to a Windows 10 VM and works great.
I've noticed, your RAM is still running at stock speed, might want to enable the XMP profile or overclock the RAM yourself, otherwise you are probably leaving performance on the table. Ryzen/Threadripper really benefits from higher RAM clocks. Thanks for the guide though, been wanting to do this for a while.
Man, the "bring this video on phone" advice stole my heart!!
As much as I appreciate you doing this video, this is *NOT* "single GPU passthrough".
Yes you just passing through one GPU of your system, but you have two in there. The goal of single GPU passthrough is, that you are passing your one and only GPU through to the VM and get back into your linux system after playing or whatever you might need Windows for.
You title does not suggest "single", but you are saying it a lot. The comment also asked for "single".
Although most of the steps are kinda the same, passing the GPU that you are currently using in Linux through to Windows and getting back to Linux safely is much more complicated and fiddlely.
It would be great, if you'd cover that, too, though 😉
Nvidia usually, usually, is going to be easy in and out, where as amd might present problems depend on which generation you have. I believe the newer cards are less problematic but might still have the reset bug of which you can alleviate in windows by setting the device to be enabled and disabled via a scheduled task. I don't have any issue with my r9 380 but my wx7100 gave me so much shit for the longest time, but I did the task schedule script and it work like magic. But there's always a gotcha somewhere that makes this more a bitch than it should be.
@@battokizu Could you explain a bit more? I'm trying to do the same thing but with a w4100, so I'm guessing the troubleshooting would be very similar to what you're doing.
@@askiiart It's been a bit since I've actually set up the system, aside from setting up virt-manager in manjaro, I don't remember what actually got the passthru working. I have that system still available so I'll update my comment if I see anything that I did that might help you out. But I do have to ask what specific issue are you having? Or what step are you on that is still causing issue.
@@battokizu Didn't see your reply, sorry. Turns out my motherboard doesn't support iommu. Don't think there's anything I can do about that.
@@askiiart no problem, we're all busy with stuff. Sorry to hear that, you should be able to get a cheap Asus x570 mobo and have no issues, if your intel or on some older platform that doesn't have support, which might be the case on Intel's side of things and amd pre ryzen. But anyhow used motherboards and cpus aren't the worst thing you can invest in if you really want to experiment with iommu.
Damn dude, u da GOAT! Did some quick lookups and got this up with an amd card. Also got the usb 3.2 card up right off. Incredible. Casual user who only watched some vids about pass through before doing it. Got games going. Got professional software going. Amazing.
Well explained! Just to note, if you have only one gpu u wanna passthrough, this is still possible as "single gpu passthrough". Might be useful in specific cases. With proxmox for example u get a web interface for the host, have the single gpu free for vms. As long as you have ssh or cockpit or anything available, it works with any distro.
Hey bud I know this is 6 months old comment but yeah you can totally do single gpu passthrough but it adds step in the process like building a hook so the graphics card gets picked up when vm is launching and it does require also the bios file for the graphics card.
You can find single GPU pcie passthrough guide on youtube
@@ritzmatsad part is for me the hook scripts don't work
No worry, most tutorials are incomplete, I had to get my friend help to get me out of a false negative when I did it 3y ago.
THANK YOU!!!! GPU passthrough has stumped me for ages on KVM/QEMU
Just a couple of things, this is not a single pass-through, in single gpus pass-through you detach your one and only gpu from the host and pass it to the guest, and another point is, sure windows reconized your gpu, but if you try any games in the state you ended up in this video it will not be accelerated by the card you passed through, but by RedHats virtual display adapter, if you want to use the 1080ti in all its glory you need to remove any other video devices from the hardware options on virtmanager and connect a monitor to your 1080ti to get its video out or setup a looking glass capture (but that requires a dummy plug on the 1080ti i think)
So what you're saying is, VFIO works best if you have an SLI setup. One dedicated GPU for the host OS, and the other GPU can be used for the VMs.
fr fr
@@VladTepesVEVO when did he say that?
@@VladTepesVEVO No. The preferred method is to have another GPU. It removes a lot of the headache. If you only have one gpu it requires a lot more work and will probably have more issues as well.
@@warhawk_yt Yea that's what I meant with SLI, having at least more than 1 physical GPU installed on your rig. Maybe even different brands, an AMD GPU on the host OS and an Nvidia GPU for VFIO purposes.
Would love to see a single gpu passthrough guide soon from you Mr. kenny outlaw, great video.
For someone who finds this video, amd_iommu=on is not a valid value. You can safely leave this out entirely for newer kernels/cpus; the default value is generally what you want.
This is EXACTLY what I needed! To decide to go and keep on using dual boot.
Wasted the better part of my day yesterday trying to get GPU and USB devices to work properly on virtualbox; then installed virt-manager with Qemu/Kvm and faced similar problems.
Today I say no, NO MORE! I'm done! xD
Anyway, the only thing I can't do better on linux is play driving game with a sim wheel; so why bother. (Yeah it does work, the ffb is just dreadfuly bad compared to windows)
Thanks again! After follow the last tutorial and getting rid of virtual box, I did look into GPU passthrough on my laptop, but got scared a bit and postponed it for later. this helps a lot, but for decent gaming, I think spice isn't fast enough, and it looks like the solution is something called "looking glass". (since I don't want to haul another monitor with my laptop.)
Also I still haven't found any methods that suggest an elegant way of switching the display between the host and guest OS.
I wish we could just press alt+ctrl+f1 and f2 to use different ttys to switch seamlessly!
I remember tying to do this a couple years ago and gave up after 3 days. Good to see it mostly actually works now.
Once again, Kenny with a video that's exactly relevant to a current question I have.
Thank you sir, excellent guide! I really don't understand why in 2022 this option is still not available in Virt-Manager...
i love you big D energy to simply not even bother with de-noising your voice audio track XD
[11:00] You can simply blacklist "nvidia" module, so it won't be loaded, if your second VGA is not nvidia-based, obviously.
KVM/QEMU/libvirt don't need "nvidia" kernel module to function, you install nvidia drivers inside windows guest os instead.
hey man sorry to bother you so late, how do i blacklist the nvidia drivers on bootup? currently im using them and im on arch but im wanting to make it so my linux is using my iGPU esclusively now so i can use looking glass and nvidia on windows. t hanks
GPU passthrough is something that interests me a lot. Unfortunately, I set up the passthrough, but the multiplayer games that I wanted to play would simply not let me do it cause their anti-cheat doesn't allow VMs.
I used to have a windows VM just for this one game, but the anti-cheat started to block VM's so I just started to patch out the anti-cheat. It works even better on wine than on a VM so I guess I'll keep doing it this way.
There is a way to bypass those by adding a single flag but I forgot what it was.
@@myself50094 kvm flag , cpu flag . when running kvm at least.
@@kxuydhj excuse me, does this work on pubg? cos their anti-cheat is hardbanning linux :( I would really dive into gpu passthrough if this was possible.
Caramba, meu irmão! Bem no momento que eu tô pesquisando sobre o assunto!
ala, um br
@@rocstar3000, é nóiz, parceiro!
What steps do you need to do, if you want to passthrough sometimes, but also use the gpu with the host system sometimes?
Could you make everything in "/etc/modprobe.d/vfia.conf" a comment (#), run "mkinitcpio -p linux" after and reboot?
instant like just from the title alone bud. thanks for the guide!
Oh man. I tried to do passthrough some time ago... My debian install crashed, and I got a kernel panic.
I've been there several times
Feels bad, man
The success of pass-through setup highly dependent on hardware, like on CPU, chipset, BIOS, VGA, etc.
Also, for quite some time nvidia refused to patch their drivers so they could be installed and function correctly within VM guest OS.
Too many things to track, many issues were patched over the years, and this pass-through setup really works well on modern hardware.
If your mobo's iommu groups aren't designed properly, it's hard to passthrough what you want without affecting something else. This typically leads to a hard lock requiring a reboot. It's especially bad if your VMs auto start.
THANK you for this, this helped a lot. could you please make a video about how to hide the fact that youre using a vm? so that you're able to play online games like cs and valorant without getting banned. that would be awesome, great content regardless!
th-cam.com/video/L1JCCdo1bG4/w-d-xo.html I introduce you to Mutahar. This guy knows his VMs and makes guides on how to bypass Anti-Cheats on VMs. Really worth checking this video out.
cs is on linux
sadly it's a difficult thing to do, vm detection on anticheats are always improving. one way to hide that fact is adding kvm state hidden to your XML config and also enable HyperV completely in Windows. it worked for me with r6, for ~2 months after a battleye patch it doesn't work now :(. good luck with that and if you manage to do that sharing your solution would be appreciated! also check out muta's (someordinarygamers) channel, he used to talk about gaming vms, bypassing vm blocks.
It's not needed that much anymore but it can try to find the settings for full obfuscation.
@@slubus I am subbed to him actually, i was just unaware that this video was about that! thank you!
If I ever manage to get another GPU I'll have to try this set-up. Would love to see my VR rig working in a VM, Windows is genuinely awful to use all the time.
i was able to do this on ubuntu (kubuntu) with some tweaking of commands on the cmd line and i got it working! awesome tutorial!
For those confused about what outlaw is doing with grub hes just editing kernel parameters. If you need it for systemd-boot you can use the file path /etc/boot/loader then go to the main config file and add the same test hes typing in the options section.
Thank you for covering this, @MO. Yes, this is a very hard thing to find the steps on the web. I plan to do this very soon, because I just had another windows update went and borked my system. It really fucked up my Office 2010 apps (like Word) and now it won't load. And, it took hours to figure out what went wrong and get it so that Office would load correctly; and, even still, some of my add-in, purchased software doesn't work yet. So, I've got to virtualize windows and eliminate these problems.
_THANK YOU_ for the softdep tip. Very nice find!
*Don't forget to add iommu=pt to your boot options, not having this option will greatly reduce performance!*
Scam
Fun Fact: My older friend, who got me into linux fried his system trying to make an NVIDIA passthrough
Edit: Fried his system as in fried his linux install
Can you use that to fry some chicken?
@@RunicRhino22 thinking how my RTX2060 can heat up I think that it might be possible xD
Did this friend ever figure out why that happened?
@@honx8570 Step one: Cover your GPU in oil (Insert le troll face)
How is that even possible?
On my old box I was using GPU passthrough with Linux as both the host and guest, then using Proton on the guest for games. Worked great!
Very good tutorial, I just set this up a few months ago for a Mac VM I needed for an IOS app I am developing and this would have saved me a lot of headache. There are still a few extra steps if you are doing Mac VM, but these are a good enough just to get your windows machine up and running
How do you get a mac ISO?
@@unreleasedjuicewrld9792 you need to rip it from a machine running macOS. Just go to your local computer shop and do it there if you dont have one. There are tutorials online.
"Sudo reboot"?! What're you doing? Lol
"shutdown -r now" man, never use sudo unless absolutely necessary 😜
Glad you made this one, virtualization is gonna be the next big thing with so many cores and ram being standard these days.
Excellent tutorial which helped considerably in me wrapping my head round GPU passthrough. Thankyou!
The thumbnails keep getting better
Thanks! Been waiting for this for some time. Also SomeOrdinaryGamers made a similar video months ago.
For people on phones: Please use zoom to fill, and set the quality to 1080p, or at least 720p.
Great video. Maybe good to tell at the start that the sytem must have 2 graphics card... :)
Now I have 2 identical vendor/model GPUs, Both show the same IDs... How can I then isolate one from the other? Can I use the first nunbers on the line? In your situation it would be "01:00.0" for the 1080 Ti and 01:00.1 for its audio device.
How?
Anyone attempting this, do make sure you have a fuck-ton of free time to solve the random bugs you will encounter, there are an absurd amount of gotchas you can hit, and then there is PCI-E communication standards hardware manufacturers failed to implement, and, if you run into that you probably won't be able to get anything running reliably without replacing hardware. This entire thing will likely not be a single weekend project.
They took down your BitTorrent streaming video. Bastards! Thank you for all you do. Love your channel!
oh geez, this is more complex than I expected ngl.
it is very funny that while he talks about how hard it is to install drivers on windows, windows just installs the driver in the background without him even noticing. But still great video love you content.
The problem with that, is that this is no-where near dynamic. For example, I use a CAD software that is windows only, but want to render my videos on native Linux. If it was dynamic, for example passing the card only when VM is run, then I could see much usefulness out of this. Else, dual boot is the way to go, but dual boot has the very bad tendency to make you lazy with switching, and you end up giving Microsoft more time than you want. 😕
This, compared to getting single gpu pass trough without any 2nd gpu to work is so much easier
Good timing, I'm sitting here trying to get a Voodoo 3 to pass through.
11:18 what is the ubuntu/debian based equivalent of this command?
I'm on pop_os if that helps
7:16 If this command doesn't work, try grub2-mkconfig as well as changing the directory to /boot/grub2
Before I go ahead and get a second gpu to do this, can you answer a quick question. When playing games on the windows vm with gpu pass-through, do you have to connect your monitors to the gpu in question, or can you play in the vm window?
It confused me too. You used the gpu then need to output,right? did you find the answer?
@@aidamon6170 yes, I did. You have to connect one of your monitors to the gpu in question, and than switch the input source to that GPU to be able to play games
if you get error 43 when installing nvidia drivers go into your vm options, go to the "Overview" tab and click on XML, scroll down to and somewhere in there add the line
Awesome! You missed one thing tho. The Audio Controller must be a subdevice of the GPU. If you don't the two devices will show up to the os as being 2 different PCI devices on two different buses. Because of that my AMD GPU driver freaked out. Unfortunately you'll need to edit the XML for that but that's not hard with Virt-Manager.
This means I can finally stop commenting about the progress on the GPU Passthrough video. I love using Windows in a container for all my gaming needs
Finally this is exactly what i have been looking for
When I go to start the VM, I get the error "please ensure all devices within the iommu_group are bound to their vfio bus driver". Does anyone know what causes this problem?
Nice video Kenny. Do you know how to set the vfio PCI ID if you've got two identical video cards? Can you identify the cards by PCI Bus ID instead? 01:00.0 and 01:00.1 in your example.
Any ideas on a fix for vfio.conf? As I dont believe softdep worked for me. It still is chained to nvidia
Is there perhaps a way to use the guest gpu on host after the VM is shut down automatically?
I have a GT 610 with HDMI that I could use on my Ubuntu 20.04 system. Would that be too low for having my Windows VM steal my RTX 2080?
Mining on the VM while using your Linux main works pretty well with the passthrough
Another day another based and GNU-pilled Mental Outlaw tutorial.
Please correct me if I'm wrong. I have only 1 monitor meaning I will have to connect that monitor to integrated graphics and then use discrete graphics for the virtual machine otherwise I will become unable to do anything on the host while virtual machine is running.
I have followed every step, and I still see the nouveau drivers for my nvidia card loaded and my hda_intel sound modules loaded for the sound card part of it. I followed your steps exactly..
I'm stuck at 11:23, since when I run the command I get "mkinitcpio: command not found". Is there any solutions to this?
you might need mkinitramfs, instead, on your distribution.
Can you make/show me a video explaining the experience of setting up Linux and which OS to buy/get
I remember I took the plunge around 4 years ago, took about a month to get a GPU passthrough all set up only to run into the AMD SMT CPU performance bug, give up, reinstall Windows and after a week afterwards I read that the bug was fixed shortly after I switched back. Is another monitor for the VM or Looking Glass no longer required? Is audio still dodgey?
You can check the tool called "nvcleanstall" to install Nvidia drivers without all bloatwares that comes with.
174k views and 6 k likes, wowz, wutt... keep it up with your libre podcast and maybe some updates, but ya your on the farm :)
If I want to passtru my iGPU only to a VM and only interface with a host try SSH would that work?
wanted to try that for a long time now. thanks for the guide!
btw, it seems like if there is no vt/iommu option in bios then this wont go?
Does this work with stuff like older Japanese programs like Visual Novels and Painttool SAI?
Nice video. Please, do a video showing how to make a shared folder between the host and the guest.
ive been waiting for this for so long YES
I missed your tutorials !!!
This is definitely going to help me get started on stuff like this, thanks a lot!
During the first reboot right after editing the /etc/default/grub my machine won't boot or even show an error! Just a blank screen doest even recognize Linux, anyone else had this problem?
Did you ever resolve it?
I hope you know your thumbnails are the best hahaha
Hi Mental Outlaw, I love your channel. I would very much like to see a video on CPU pinning for use in a VM please. Also, what's the best way to contact you? I could do with advice on a desktop build I'm planning. I'm willing to pay for your time. A lot of my questions are follow-up questions to things I've learnt from your videos, but it would be easier to put my questions to you in one place rather than break them up into individual video comments.
Many thanks. :)
I love VMs! I'd love to see more videos like this.
if you need a second GPU, do you need a second display to connect that GPU? I have the impression that you need an extra monitor if you want to do this thing
i didn't see you change the gpu output, you changed the output correct,? and what we see on your screen is the output from your passthrough graphics connected via a different hdmi?
Thank you for this video. I missed yelling racial slurs at middle school kids in COD
So, that's Artix. And what about compiling Gentoo with your Threadripper?
So how it is working in detail ? You have connected Your display to some motherboard gpu (INTEL etc.etc.) and Windows System using dedicated PCIE Nvidia ? If yes, then You are streaming picture rendered by nvidia and display via motherboard gpu . What about quality of that stream ? Did You observed some moments with low quality picture ? video compression etc.etc. ?
The prophecy is true, kenny will utilise AMD and Nvidia cards are within the same system flawlessly.
As much as I'd like to do a gpu pass-through the electricity prices where i live are horrendous, I would need to buy a new power supply (considering what the second gpu would need power-wise) and it's just not worth it, since waiting for the virtual machine to boot takes as long as rebooting into my windows partition instead where I could instead also use my better graphics card that I already have built-in rn (RX 6800 XT)
Still a good tutorial for those who are not limited by what I mentioned or were considering it anyway and just needed a better tutorial to actually get started on it
If using windows I would prefer to not run it on bare metal. Although for me it would be interesting enough to have dedicated graphics inside of a Linux vm.
after rebooting when having done the grub config stuff im stuck in what i think is a boot loop
it just keeps initializing the same things then failing on a million things and starting over.
im using a laptop running linux mint cinnamon 21
btw this has happened once and when it did i reinstalled the entire os but now i wanted to see if i missed a step and i cant seem to find anything that i missed so here i am afraid to reboot cuz im almost certain the same thing will happen again... what do i do? fyi the "quiet" option was enabled and i disabled it along with some option called "splash". is this the splash screen at bootup or is it important and should i not mess with it?
for now i have simply removed the commands by commenting them for later and rebuilt grub in the way shown through the video
Hi Kenny tried this but cannot seem to stop the Quadro from loading nouveaux
VGA compatible controller: NVIDIA Corporation GF106GL [Quadro 2000] (rev a1)
Host is using a seperate amd gpu card. there is no onboard graphics
Subsystem: Hewlett-Packard Company Device 084a
Kernel modules: nouveau
tried blacklisting but hasnt worked
at 11:32 what would be the mkinitcpio equivalent on Ubuntu