Это видео недоступно.
Сожалеем об этом.
Proxmox 8.0 - PCIe Passthrough Tutorial
HTML-код
- Опубликовано: 4 окт 2023
- Grab yourself a Pint Glass, designed and made in house, at craftcomputing...
Virtualization is great, but sometimes you just need access to physical hardware. If only there were a way to allow a virtual machine bare-metal access to PCIe cards in your server. OH WAIT! THERE IS! Whether you need access to a storage controller, graphics card, network card, or any other PCIe device, this is the video for you.
But first... What am I drinking???
Sierra Nevada (Chico, CA) Torpedo Imperial IPA (8.6%)
Written Documentation can be found here: drive.google.c...
Links to items below may be affiliate links for which I may be compensated
Parts from today's build:
AUDHEID 8-Bay NAS Chassis: amzn.to/47iCsxb
ERYING i7-11700B 8-Core (Non-ES): s.click.aliexp....
Leven DDR4 2x16GB 2666 UDIMM: amzn.to/3OmCnjv
Flex ATX 1U 500 Watt: amzn.to/3Qw9EeB
Silicon Power A60 1TB: amzn.to/44XANM1
ASM1064 8-Bay SATA Controller w/ Cables: amzn.to/3KAqULZ
Follow me on Mastodon @Craftcomputing@hostux.social
Support me on Patreon and get access to my exclusive Discord server. Chat with myself and the other hosts on Talking Heads all week long.
/ craftcomputing
Excellent guide.
Do not forget to deselect Device Manager->Secure Boot Configuration->Attempt secure boot in VM UEFI BIOS when installing TrueNAS. Access it by pressing "Esc" key during boot sequence. Othervise you will get access denied on virtual installation disk.
5 months later, this comment just saved me some headache.
@@wirikidor MERCI !!!
I literally just disabled secure boot and it worked (as now it's just UEFI and no disk space is needed) hopefully that doesn't screw me down the road
"Don't virtualize truenas"
*Chuckles in 4 virtualized truenas servers in production*
STOP SAYING TH....
Wait.... nevermind :-D
Just like Stockton Rush always said.
REAL Men ALWAYS test in production.
@@sarahjrandomnumbers Lmao rip
I have been on the fence if I wanted to do truenas on bare metal or virtualize it and this sentence and Jeff's quick explanation on why made me feel a lot better about doing it.
@@shinythings7 you really don't lose much juice virtualizing anything nowadays.
These tutorials are so much more usefull than Network Chucks and you dont seem like a shill trying to sell me something constantly.
Network Chuck is only good for ideas not how-to guides. He’s more of a cyber influencer to me.
This is actually such a good point. I barely/rarely watch Network Chuck anymore. He just feels fake to me now. Almost unwatchable. I haven't seen one of his videos in months.
seems like a good starting point for newbies or kids. I won't knock him for making the stuff sound exciting but I definitely grew out of his style.
I can't fucking stand that guy. "Look at my beard! Look, I'm drinking coffee! Buy my sponsored bullshit!"
Proxmox really should just make these options available in the UI.
Truly. I just dont think these things occur to them when they are processing feature adds and the like. They can be slow to adope like Debian which is what its based on.
Right? They have MOST of the UI, they just need the initialization bit to be UI-driven aswell.
A full-feature product like Proxmox should have all of its functions available through its UI, "popping under the hood" with a terminal is an ugly solution, no matter how poweful it might be.
It's stupid easy in ESXi, too bad Broadcom killed it.
@@Solkre82That's where I'm coming from too. Moving from esxi to Proxmox - if my passthrough setup can be replicated in PVE...
@@manekdubash5022 I'm sure it can, just not as simple. I archived my ESXi 8 ISOs and Keys so I'm not worried about moving for a few years.
Who knows, Broadcom might decide to do good.. HAHAHAHA my sides hurt!
Wish after so many years there was a simple gui option for this. Appreciate the guide!
I've been waiting for this. I already have 2 Erying systems as my Proxmox cluster, after your first video on this, and they've been working perfectly for me, but when you originally said you couldn't get HBA passthrough to work properly, I held off buying a 3rd, as I wanted the 3rd for exactly what you've done in this video, and to have a 3rd node for ceph. Now that I can see you figured it out using a sata card, I'm off to order all the bits for the 3rd node.
Thank You, and after I order everything, I'll pop into your store to buy some glassware to show some appreciation.
As always you're Jeff.. There a situation where you aren't Jeff? like maybe Mike? or Chris?
I kind of like being Jeff.
@@CraftComputing Yeah it would be weird if you woke up as Patrick from STH.
That would be weird. I'd be a whole foot shorter.
@@CraftComputingDepends if you're cosplaying as an admin that day or not
@@CraftComputingme too
I just have to say, I spent hours trying to get my GPU to passthrough correctly, and your one comment on Memory Ballooning just fixed it! Thank you so much! I didn't even see anything about that mentioned in any of the official documentation!
Can we just take a step back and marvel at how now only that this is all possible, but also won't cost a dime in software?
Jeff - Just wanted to give an extreme thank you for the quality and content of your videos. I just finished up my TrueNAS Scale build using your guidance and it worked like a charm. I did use an Audheid as well, but the K7 8-bay model. I went with an LSI 9240-8i HBA (flashed P20 9211-8i IT Mode) and the instructions on Proxmox 8 you provided were flawless and easily had my array of 4TB Toshiba N300's available via the HBA in my TrueNAS Scale VM. Lastly, a shout out to your top-notch beer-swillery as I am an avid IPA consumer as well! (cheers)
Another little addition to this. It seems that you still need to add ""GRUB_CMDLINE_LINUX_DEFAULT="quiet intel_iommu=on" "" to the etc/default/grub boot cfg file if using the legacy grub boot menu. The legacy grub boot menu is still teh default if installing ext4 onto a single drive.
SR-IOV and IOMMU are completely orthogonal features and enabling one will not magically make the other work. SR-IOV simply lets the kernel use a standard way of telling PCI-E devices to split themselves into virtual functions. SR-IOV does not require an IOMMU, and IOMMU does not require SR-IOV.
there is no /etc/kernel/cmdline
Hey Jeff, I had issues passing through a GPU with the exact same hardware until I pulled the EFI ROM off the GPU and loaded it within the VM config PCI line. Adding the flag bootrom=“” to the line in the VM config pointed to the rom should do it. I think this is because the GPU gets ignored during the motherboard EFI bootup so the VROM gets set to legacy mode. When trying to pass it into an EFI VM it won’t boot since the VROM doesn’t boot as EFI
Could you explain a little more on how you got that working? I still can't get GPU passthrough working on my 11900h ES erying mobo.
Also did you mean "romfile=" ?
After looking at his documentation, I think you're onto something here.
This was helpful as I don't run Proxmox and many people have commented on my XCP-NG videos saying how much easier Proxmox handles this VS XCP-NG but in reality they are actually very similar. Both have the need to find the devices and make changes via the command line just to get it working.
Thank you for this. I couldn't get hardware transcoding working properly. I turned off ballooning on the VM and BAM! It works. HUZZAH!
Been waiting for this. All the pcie passthrough write ups are old and outdated, and the only one that worked for me on prox 7.4 was yours.
Tutorials: update-grub
Proxmox 8.0: "What's a grub?"
@@CraftComputingexactly!
Quickly for clarification sake, q35 means uefi and ifx440 or whatever is bios boot?
Half the tutorials say to do one or the other, and this is the first time I have heard it mentioned otherwise, unless I just forgot 😅.
@@lilsammywasapunkrock
Both machine types support bios and uefi.
The primary difference between q35 and i440fx is that q35 uses PCI-e while i440fx uses the old PCI.
If I remember correctly, I was able to use PCI-e passthrough with i440fx but only for one device at a time.
I personally don't see any point in using i440fx in modern systems with modern host operating systems.
^^^ Bingo
FYI, the instructions don't work if you're using GRUB. These instructions appear to be specific to systemd-boot.
You'll need to look in /etc/default/grub rather than /etc/kernel/cmdline to make the kernel command line changes.
You're a damn wizard! :v Thxx Mr Magical Pants!
Thank you for sharing your experience! It was incredibly helpful in getting GPU passthrough to work. However, I needed to make a few adjustments:
In Proxmox 8, /etc/kernel/cmdline does not exist. Instead, I entered the settings in /etc/default/grub as follows:
GRUB_CMDLINE_LINUX_DEFAULT="quiet nouveau.modeset=0 intel_iommu=on iommu=pt video=efifb:off pci=realloc vfio-pci.ids=10de:1d01"
It's important to note the parameters video=efifb:off and pci=realloc, which were not mentioned elsewhere. These are crucial because many motherboards use shadow RAM for PCIe Slot 1, which can hinder GPU passthrough if not configured properly. With this setup, I believe all your GPUs should function correctly. Additionally, I had to blacklist the NVIDIA drivers.
hey, nice addition indeed ! what about the audio card ? this is my pain... can you give me some hints about that ?thx in advance.
Wahoo!! Your directions worked! Thanks. I'm installing Ollama LLM on a VM and want to passthrough the GPU, which worked thanks to you! I'm using an Intel based i7 Dell 3891, GTX 1650, and current Proxmox.
You definitely CAN passtrough your primary GPU to a VM...
Running a setup like this for e few years now. The 'disadvantage' is that a monitor to the proxmox is not available any more, and until the VM boots, the screen says 'loading initramfs'.
Yes, definitely - and Proxmox UI is used through SSH from another device anyway as it usually isn't a thing to run the UI on the Proxmox Servers GPU itself anyway.
It can be handy though to have another means of connecting a GPU to the system if the SSH-interface is messed up - I use a thunderbolt eGPU in such circumstances...
This tutorial series is top notch. Thank you so much, Jeff!
Efi booted host, cards don't have efi firmware on them, so the vbios doesn't get mirrored into memory.
Get a dump of the vbios, and add it as a vbios file in the pci device section of your VM config.
DOH! You're probably right.
I would love an explanation of this comment or further resources. I don't understand efi, vbios, why and how that gets mirrored, or really anything that was said.
@@dozerd42when a physical system boots, it copies the contents of your video card bios (vbios) into main system memory, into the memory region reserved for communicating with the card.
Some cards have a uefi firmware in addition or instead of a traditional vbios.
Without it though, the card won't initialize the display output during boot.
In this case, the cards didn't initialize during boot at all, so providing the video bios to the VM gives it an opportunity to initialize the card on its own.
While you can technically usually boot cards without supplying it, what will often happen is that the in memory copy will become overwritten in some cases - like if that memory region is needed for texture storage at some point.
When that happens it's necessary to reload the vbios from the card, but if you don't supply the vbios separately, sometimes this reload fails, which will hard lock your host.
Are you planning a video on USB and or PCI passthrough to LXC containers? Something about cgroups and permissions never could get it to work.
Hey Jeff, quick tip: you can use the RUclips sections in the timeline to add timings so people can easily skip to where they need help.
Sponserblock extension allows you to skip ads and see where you should start, try it
For your next tutorial I'd love to see you get some VMs running with their storage hosted on the truenas VM!
Unfortunatelly, I'm receiving the error "No /etc/kernel/proxmox-boot-uuids found, skipping ESP sync."
asrock decided to put all my pcie slots in one group and the three m.2 slots in another. needless to say i'm pissed.
Flash vBIOS to force GPU into UEFI mode and disable Legacy mode at boot ?
Do you need to alter any of those CLI strings depending on chipset connected PCIe lanes vs. direct CPU lanes ?
Thank you! Every time i'm stuck on a project in my home lab, you tend to have just the video i need and explain it very well!
Been searching for this for the past week or so. Love your work Jeff. Cheers
Me to, since upgrade failed on my HP Z440 with xeon 2690 and Tesla M40 24G. Cheers
6:55 Did the Path change? I only have install.d, postinst.d and postrm.d in the /etc/kernel directory.
I had to reinstall proxmox for the first time in over a year. This guide was very much needed today. Thanks
Ive followed the isntructions but as soon as I add my HBA as a PCI device being passed through, my VM will just boot loop saying no boot device found. I checked the boot order and made sure it only had the lvm where truenas was installed but it still does this. If I remove the PCI devie, truenas boots fine.
Hi Jeff,
Are there any drawbacks (i.e. Performance) not blacklisting your GPU from the host Proxmox O.S.? Currently I have GPU pass through working but I didn't black list that GPU from the host O.S. and everything seems to be working without issues.
Thanks!
Same here. I did everything except the Proxmox blacklist and got it working in a Win11 VM.
I also checked the "PCI Express" box on the pass-through model in Proxmox for the video card. It did not work without this.
Additionally, my 1070 GTX needed a dummy HDMI plug (or external monitor) to initialize correctly.
If you can convert a video or see apps use cuda without crashing the VM then no, you are completely golden.
Thanks Jeff, you saved me a LOT of frustrating research :-) I just managed to passthrough a couple of network interfaces to a microvm within my NixOS server, and it just took me a couple of hours, I expected to spend all night on it :-D
I prefer using LXC for GFX passthough. Im using it for hardware encoding for Jelly fin. I installed NVIDA drivers on both host and LXC and did pci passthough. Worked straight away.
Meanwhile I spent 2 days pulling my hair out barely able to install the nvidia drivers and still don't have it working.
This has been a life saver. I finally was able to passthrough my 6700 XT for jellyfin hardware encoding.
would be interested in LXC tutorial with GPU passtrough / sharing to it... especially with something like intel NUC with only 1 integrated GPU, or maybe just sharing / passtrough of integrated GPU in general
it's not passthrough for lxc, it'd be just using the host gpu directly in a virtual environment. it's the same kernel
Thank you sir! Just by adding a new physical NIC to Truenas, my write speed increased by x3 on my ZFS pool! I had saturated the just one NIC I had on board with a lot of LXC and VMs
I really like these series on proxmox
a particular reason not to passthrough disks before installing is to make it easier not to mess up the installation drive, so it's good advice indeed
Great video! I wrote a hookscript a while ago to aid in PCIe passthrough. I found it useful to use specifically with a Ryzen system with no iGPU. It dynamically loads and unloads the kernel and vfio drivers so when say a windows gaming VM is not in use, the Proxmox console will re-attach when the VM stops. Could be useful for other devices too! If anyone is interested let me know, I'll try to point you to the Github gist. I don't think RUclips likes my comment with an actual link. :)
What's the name of the repo? We'll just search for it.
@@jowdyboyYes, seconded - sounds useful. Any idea if it works with NVidia?
I use it with Nvidia, I've tried to post several comments, but I'm assuming they keep getting flagged.
Whats the repo name
Great video, I enjoy your server content a lot when it's this kind of set up.
I was able to passthrough an RTX A2000 with my Eyring i9 12900H motherboard . I populated 2 of the 3 nvme ports though.
Hi. I am currently investigating the idea of creating a proxmox server to run various things, including MacOs, since i definitely need/want that one for audio. I can't really find a clear answer so i feel like asking you this : is it feasible to have low-latency audio on a VM ? Not remotely, locally of course, through an USB audio interface. I feel like PCI passthrough on a dedicated USB card can give me something viable, but i'm not completely sure. Maybe i can just passthrough my USB controller on the motherboard ? But in the end, will it provide me something useable for realtime audio treatment, as in "i plug my guitar in the audio interface, and i hear it's sound, processed by the computer, on my loudspeakers in real-time with a low latency, under, say, 15/30ms" ? )
On the "Proxmox isn't the best tool for ZFS file server duties argument".. that's mostly right, however, your friends at 45 drives' Houston UI (running in cockpit) does a solid job at all the missing responsibilities you listed that TrueNAS typically handles. I personally still prefer TrueNAS myself, but you can run the Houston UI webgui and standard Proxmox webgui on the same box.
I prefer separation of concerns and staying as close to default settings and usage as possible in order to be able to update much more easily.
So if I needed or wanted to use ZFS (which I currently don't), I'd have gone for TrueNAS, possibly in a VM. I don't feel as comfortable with Proxmox (I am currently managing VMs and containers by hand or through Cockpit on my Ubuntu set up), though while it works, it's not that robust depending on what you do and it also requires a ton of manual work.
I was surprised that GPU passthrough to Debian or Windows based VMs worked out of the Box on my machine. I never configured anything inside Proxmox. I made sure that the UEFI bios was set up correctly. But that was it. Has been running great for months. (Im using a AMD 5900X on a MSI X570 Gaming Plus with a 1080ti)
Just getting into my own homelab after watching for a while. Got an old ThinkCentre that I'm going to have a tinker with before fully migrating a Windows 11 PC with Plex etc. This video series is great
Great video! Waiting for one about SR-IOV, I tried using virtual functions on my Intel I350-T4 NIC and got nowhere with it
There is no 'cmdline' in /etc/kernel :(
I created the /etc/kernel/cmdline file as well as edited GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub. Not sure which one ended up making iommu work though
To be able to use GPU, I needed to enable PCIE option on file /etc/default/grub line GRUB_CMDLINE_LINUX_DEFAULT="quiet intel_iommu=on modprobe.blacklist=amdgpu" (because im ussing a amd 5600) before add that line, remember to execute grub-mkconfig -o /boot/grub/grub.cfg and restart :)
dude when he pulled up nano instead of some vi or vim elitist bullshit I knew this guy was the GOAT
Not sure if I missed it and it was addressed in the video but my scenario is similar to what's done in the video, 1 VM with TrueNAS passing through the SATA controller to the drives for the sweet sweet ZFS setup and another VM to host all my home server stuff like jellyfin, qbittorrent and elasticsearch.
In this case, what would be the best way to connect the ZFS pool between one VM to another?
It took some good amount of hours to figure things out - but at the end it was worth it! I'm using GPU passthrough to run some language models locally
i had nvidia-smi working fine for my quadro but plex wasn't doing hw transcode. after throwing some semi-stale additional virtualization tweaks at the wall, the real thing was that i used my distro's packaged nvidia driver - which didn't auto include libcuda1 and libnvidia-encode1. eventually figured it out from spelunking the plex debug logs, looks like those two extra packages are enough to get the full hw transcode going, but i'll update here if i notice anything else.
You ever get PCIE pass through working for the x16 slot? Looking forward to part 4 😊
At first, adding a GPU to one of my VM's also did not work as you pointed out.
I made it work by deleting that VM ( Debian 12 ), creating it again from scratch, BUT before the first boot, add PCI device and select your GPU.
Go through the installation process, and once done, lspci showed my GTX 1060 6G in the list.
Hope this helps anyone else looking for this.
This worked like a charm for me!
Turned a spare gaming laptop into a remote access gaming server.
For me the graphics card worked, and I removed the errors on my Nvidia card by not adding the sub features of the card, like usb C, and the audio device as advised in this tutorial. It gives an error saying I added the card twice if I did.
Thank you for the write-up, especially addressing upfront EFI vs legacy boot config for IOMMU (intel_iommu=on).
Great video 👍
Kindest regards, neighbours and friends.
Hey Jeff I'm from Central Oregon been watching you channel for quite a while now, thank you so much for the videos please please more proxmox videos, show any and everything great content :) I'm trying to learn all ins and out of proxmox.
Man, I ran TrueNAS in a VM for years now. I never ran into issues.
I'd like to see more:
* Sharing an nvidia card between multiple VMs using MIG
* On a system running ProxMox, using a VM as a gaming desktop on the machine itself
This is just what I was looking for.
I am a single home user and running a separate machine for NAS from my Main Workstation makes little sense. Having single power PC with Proxmox with one instance of trueNAS and another for windows / linux OS will make things a lot simpler. I can also offload docker instances from my NAS over to proxmox and manage them independently.
Just one question though, how's proxmox on PC in terms of power management. Once I shutdown my workstation PC, will the overall power consumption go down to a comparable level of a commercial grade NAS?
1. make sure that the vm uefi is set to efi mode and not csl mode. The EFI should be loading the drivers for the card at boot time. That could stop the GPU from passing through.
2. If you have two identical GPUs, consider cross flashing the vbios with one from competing AIB with the same specs. The new vbios will change the pcie id for the card without changing the functionality, letting you split up the two cards under iommu
The later isn't needed as they are in different slots they have different buss IDs and thus should never collide with IOMMU. You are still able to assign them to different different VMs
@@FlaxTheSeedOnebut not to use one on the host and one for passthrough
@@Momi_Vyou dont need to use one for the host. turn on serial console if your cpu doesn't have integrated gpu.
@@omegatotal I know. But the original comment provides a way to solve the "two identical GPUs" issue (which is inherent to this method of passthrough, not just on Proxmox where serial is an option) that also applies to other virtio passthrough scenarios (like a desktop/workstation virtualization setup). And it's not solved by different slots (which the comment I replied to implied), though I must admit pcie id is not the right term, vendor/device id is a more accurate name
@@FlaxTheSeedOne I would have thought that too but it contradicts what was said in the video and seems to be a quirk of the Chinese motherboard with mobile cpu
FYI while it's fine to run a Truenas VM with PCIe passthrough to a SATA controller, the problem you can stumble upon are IOMMU groups.
If you try to do this and you can't ungroup the SATA controller from a IOMMU that has other important components (say the APU) it may cause the Proxmox host to crash; just tested this on a X300-STX motherboard with a Ryzen 4750G and the SATA controller basically shares the IOMMU group with almost everything and no amount of grub parameters and blacklists allowed me to get this going. I was just expecting too much of a Deskmini x300 😆
You COULD just enable samba on proxmox, but that would be a very bad security risk (as VMs would get access to the Host filesystem).
Technically... it is possible to pass-through a GPU, in a system with only one GPU (no integrated GPU). This is what I currently do with Proxmox and a 6900XT. 😉 Running virtualised TrueNas, and Linux gaming VM.
I would assume it's possible, it is possible with esxi...
My server has no igpu and wont boot without a graphics card. I block the kernel modules so i can pass it through. The risk is now there is no console output for proxmox if you cant connect over the network.
Yep, same here. I have proxmox GUI for about 2 minutes until the VM boots up.
@@bonicb11b3 turn on serial console.
@@bonicb11b3 yes you lose console but you can connect to vm desktop in any manager e.g. royaltsx. if you need console access through proxmox you can change the display output to vmware compatable
Darn it. I should have done this video. I got it working about a month ago. Great information!! So many people discouraged me from doing it as they said it wouldn't work. It works great for me.
My install of Proxmox on a Dell r530 is EFI but it does not have a file in etc/kernal/cmdline. There is a cmdline in /proc but that cant be edited. Running 8.04.
i always kinda like iommu as a name
its a mouthful but at least its not easily confused with the many other acronyms
i remember on something of the low end aorus gaming boards it used to be under overclocking settings > cpu > miscellanious cpu settings
I always think that IOMMU is just the thing that Doctor Strange battles in the movie.
Thanks Jeff. As always an excellent and succinct guide. Cheers for making the effort! 😊
Impressive to the point and yet full of details tutorial !
I have a 3700x and a p1000. Is it not possible to use this p1000 for plex transcoding since proxmox requires a display?
I do have a quadro k620 that could go into an x1 slot with an adapter. Would this resolve my issue?
I know this is older, but is there a reason you didn't select the PCI Express Option when adding the Passthrough and Primary (for GPU)? (Timestamp 11:00 and 15:50)
In my proxmox setup all I did was add iommu=on and selected the device on vm. Didn't have to do any of blacklists or anything. Maybe that's your issue.
Depends on the GPU. On the Enterprise grade video cards like the Nvidia Tesla P4 you have to use their special video drivers to make it work. Open source drivers won't work at all.
I am beginning to feel like Proxmox just out performs everything even VMware ESXi which I have used. I think at some point I am gonna build a "virtualization" server, and move my TrueNAS from Bare Metal to Virtual Metal. But since I need a software server more urgently, Proxmox is gonna have to take a back burner, but I'll still watch for the education.
Thanks for this vid, unfornutaly I didn't get it work. I'm using a Dell Optiplex 7050 running an Intel Core I5 - 7500T and booting in EFI. If I put in your commands, I get a message that the system is booted up in EFI but no grub efi amd64 was found.
Even my /etc/kernel/cmdline file was empty at the first time....? What could be went wrong? I need IOMMU for a VM....
Using a Dell Optiplex 7090 and I too am missing a /etc/kernel/cmdline file. Did you ever get this to work?
It's awesome having a homelab, but not as awesome when you've put the server in a mildly inaccessible spot, headless. Especially when you follow a PCI passthrough tutorial and the system reboots and doesn't come back.
One important thing I ran into installing TruNAS Scale on ProxMox 8.0.4.
When you add the EFI storage disable Pre-Enroll keys.
Failure to do so can cause the error: bad shim signature
THANK YOU THANK YOU !!!!!! Was pounding my head on the wall trying to figure that one out.....
@@deanolivas3011 I was right there doing the same thing 3 nights ago. Gave up came back the next day and after working through a bunch of suggestions ran into this at the bottom of one trunas forum... I figured I would share this with anyone watching the video...
Been looking at converting the home lab to Prox, but can't find information on virtual storage options. Currently running vSAN and the performance has been outstanding. Looking for something on the Open side of the table that will do auto tiering and other functionality between SSD and HDD. Any recommendations?
I'm trying to learn how to install and implement VM's and ultimately build a homelab, just for self satisfaction and knowledge.
FYI Many Ryzen chipset drivers have a bug in their passthrough code. There was an early version that worked, then a new version that didn't, and a newer one that did. I spent hours troubleshooting making sure everything was right in all the configs nothing. Did a BIOS update and perfect in a moment. I was on a x470 chipset with a Ryzen 2700.
Hello everyone, are they any resources or videos I can use/follow to learn how to install and setup proxmox step by step like I'm a 5 year old. I'm totally new and trying to learn. I bought a protectli vault 6 port device and wanted to install proxmox and then install pfsense on top of that. I hope I'm saying it right. Would anyone be willing to help me?
LearnLinuxTV has a course of videos like this.
@endymion84 thank you very much.
Quality stuff again. Was excited when I saw the thumbnail that finally I will see how to passthrough properly an nvme ssd to a truenas vm. Unfortunately this not happened this time.
Hope that you will cover that as well somewhen and if you could explain how to get the truenas vm to put the hdd's to sleep, that would be just the cherry on top.
Cheers Jeff.
Exactly what I had been looking for. Thanks for sharing.
When I first started the TrueNAS vm after creating it, I got the following error(s) at the UEFI boot screen:
BdsDxe: failed to load Boot0002 "UEFI QEMU QEMU HARDDISK " from [Pci Device Path] : Not Found
BdsDxe: loading Boot0001 "UEFI QEMU DVD-ROM QM00003 " from [Pci Device Path]
BdsDxe: failed to load Boot0001 "UEFI QEMU DVD-ROM QM00003 " from [Pci Device Path] : Access Denied
The fix for this is to disable "Attempt Secure Boot" in the UEFI Bios.
In order to get to the Bios, I had to let the UEFI boot process fail out of the PXE and HTTP boot. (This took 2-4 minutes.) No amount of hitting Escape would speed things up. Eventually you'll end up at a screen that says "UEFI Interactive Shell" at the top. There should be a yellow "Shell>" prompt. If you type "exit" at the prompt, you'll be taken to the Bios.
Go to "Device Manager" > Secure Boot Configuration, select "Attempt Secure Boot" and hit spacebar to uncheck the box. Go back to the main screen to save and exit. Proxmox will reboot the VM and you should then see the TrueNAS installer.
This happened with TrueNAS Core 13.0-U6.1 on Proxmox 8.1.4.
This actually solved my problem so thanks a lot mate!!!
FYI, if you are passing through a storage controller and runninto slow boot time's of your VM after try disabling ROM-Bar on the passthrough
Three questions: 1. Were any Torpedos harmed in the making of this video? 2. Did you film this fast enough to not get warm beer when you shot this? 3. Your beer glass seems to leaking during the making of this vide - the beer is magically disappearing sequentially throughout the video - what is happening?
Thank you for this update. This is one if the more challenging tasks for me in proxmox and I was only successful through sheer dumb luck the last time I did this.
The good news? Its still deployed and the only thing I have changed is the GPUs and Storage controller.
I've found that sometimes using the "All Functions" option is what is actually causing the failure. Just adding the secondary device manually is more compatible.
I love your videos.
They educate me a lot.
Whst ive also learnt is i for plex and jellyfin you dont need to run a VM for just that. Its simple to run it in an lxc container. It's more efficient for my use case.
Correct me if my understanding of proxmox is wrong, after all a noob here, but lxc containers have full access to the hardware that promox has. So for example where you have to blacklist the hardware in proxmox for VM pass through, you dont for containers?
The only thing I'm struggling with is WiFi card pass through on my silly setup. I dont think itll work on an lxc container but im struggling on VM too.
I had planned to use my setup if proxmox as the following:
Hardware connects to my internet. OPNsense as my router/fw etc. second nic goes to switch. It is also bridged in proxmox.
Then second lxc or VM for openwrt to use WIFI in AP which is compatible with openwrt in AP mode, thats been checked. I struggle eith that.
It also runs jellyfin and PLEX in 2 different containers.
I mainly use PLEX but playing around with jellyfin recently.
I also have another container for pihole. I am looking at adguard too but i think they're bith dns sinkholes.
All these units use about 6 to 12w depending on demand with a peak of 28w when i was doing silly stuff.
The truenas proxmox server is different and i have a oroxmox backup server running too. This is all because of your simple tutorials. Really appreciate the work you put in
When I run dmesg | grep -e DMAR -e IOMMU in proxmox It doesn't show the line where it says it's enabled however I can still add by HBA PCI card to the VM under the Raw devices. Is this normal behaviour? I'm running a Ryzen 7900 with a B650E motherboard.
12:42 helped me to root cause my problem: Proxmox was using my NVIDIA Quadro P2000 as my primary display source. In the BIOS, I had to go to Advanced -> AMD PBS -> Primary Graphics Adaptor and set it to D-Sub. My mobo has onboard graphics but my CPU does not.
@craftcomputing Do you have an updated version of this? My passthrough was working but now it's not. Everything is still setup the same...
This exact functionality I got working with an Nvidia P400 in Proxmox v7. I hadn't upgraded to 8 for fear of going through this again. Now I may have to take the dive.
Does someone know why i dont have an cmdline file ( /etc/kernel/cmdline ). There is no. i have installed Virtual Environment 8.0.3 and also tried 8.1.2
the same issue in 8.1.10. Where the heck is cmdline?🤔
Thank you so much for this! Just what I was looking for
Thanks for the great video! I am hoping to try this on my Dell R720 with a Windows VM.
Seems you were able to fix the ERYING motherboard and not being able to passthrough pci-e card. How you do it?
Wonderful video, thank you. Regarding SATA controllers, for some servers where PCI Passthrough is not possible (because they perhaps share the same IOMMU group as the hosts SATA controller for example; controller for proxmox drive and controller for the nas drives), I often see the solution of passing through the hard drives themselves as opposed to passthrough the controller itself; qm set 592 -scsi2 /dev/disk/by-id/ata-ST3000DM001-1CH166_Z1F41BLC.
Would this be an acceptable and reliable solution instead of using the "pcie_acs_override" patch which has security vulnerability?
Thank You