Is it just as simple as uninstalling the NVIDIA GRID drivers then rebuilding the 6.8 kernel? I'm in that position right now as I'm pinned to the 6.5 kernel right now in order to have the cluster continue to run. However, I'm running into an issue as I'm seeing kernel taint errors which may explain why the hosts in my cluster are randomly dropping out.
Great news. Did you uninstall the NVIDIA drivers first? I'm currently pinned to the 6.5 kernel and everytime I do apt dist-upgrade the kernel build fails and if I try to boot into the 6.8 kernel it hangs on boot.Hello evryone , kernel 6.8.12-2-pve + Nvidia driver 550.90.05 (17.3) + patch , everything work fine
Nvidia RTX2080
First boot with 6.8 , next download nvidia driver and patch it , then install na patched driver (when start install the driver , ask you to uninstall ....)
proxmox-boot-tool kernel pin 6.8.12-2-pve
reboot
chmod +x NVIDIA-Linux-x86_64-550.90.05-vgpu-kvm.run
./NVIDIA-Linux-x86_64-550.90.05-vgpu-kvm.run --apply-patch 550.90.05.patch
./NVIDIA-Linux-x86_64-550.90.05-vgpu-kvm-custom.run --dkms -m=kernel
reboot
nvidia-smi
+-----------------------------------------------------------------------------------------+
| NVIDIA-SMI 550.90.05 Driver Version: 550.90.05 CUDA Version: N/A |
|-----------------------------------------+------------------------+----------------------+
| GPU Name Persistence-M | Bus-Id Disp.A | Volatile Uncorr. ECC |
| Fan Temp Perf Pwr:Usage/Cap | Memory-Usage | GPU-Util Compute M. |
| | | MIG M. |
|=========================================+========================+======================|
| 0 NVIDIA GeForce RTX 2080 On | 00000000:86:00.0 Off | N/A |
| 0% 52C P8 29W / 260W | 8163MiB / 8192MiB | 0% Default |
| | | N/A |
+-----------------------------------------+------------------------+----------------------+
+-----------------------------------------------------------------------------------------+
| Processes: |
| GPU GI CI PID Type Process name GPU Memory |
| ID ID Usage |
|=========================================================================================|
| 0 N/A N/A 28716 C+G vgpu 2024MiB |
| 0 N/A N/A 31114 C+G vgpu 2024MiB |
| 0 N/A N/A 38171 C+G vgpu 2024MiB |
| 0 N/A N/A 46857 C+G vgpu 2024MiB |
+-----------------------------------------------------------------------------------------+
My problem is that on the hosts that had 535 and 550 drivers installed and running the 6.5 kernel, during the apt dist-upgrade to get the new kernel the 6.8.4 and 6.8.12 kernels both fail to compile properly (based on the dkms make.log errors) and when I try to boot either it hangs on boot. I suppose I could try those kernels in recovery mode...
But I think I might just do a clean uninstall of the drivers, re-run apt dist-upgrade and hope for the best.
But I think I might just do a clean uninstall of the drivers, re-run apt dist-upgrade and hope for the best.
Perfect. Actually, I had to patch in 6.5, install the patched driver, then run apt dist-upgrade to rebuild the 6.8.x kernels then reboot to the 6.8 kernel. Without the dist-upgrade step it would hang. I think if I run into a similar issue with future kernels, rebuild the NVIDIA driver first
Are we going to be able to assign vGPUs/mediated devices from the user interface eventually?
Hi all
I have installed the patch for kernel 6.8.12-2-pve with driver version 535.183.04. The installation worked and nvidia-smi shows the graphics card. However, mdevctl types shows nothing.
When starting, you can see that the devices are activated:
Does anyone know the problem and has a solution for it?
Thank you and best regards
I have installed the patch for kernel 6.8.12-2-pve with driver version 535.183.04. The installation worked and nvidia-smi shows the graphics card. However, mdevctl types shows nothing.
When starting, you can see that the devices are activated:
Does anyone know the problem and has a solution for it?
Thank you and best regards
Dear Boysa22
Thanks for the answer, sometimes you can't see the forest for the trees... I'll try it out right away - thanks!
I'm still on 6.5 for the time being. It's working. I don't have a need to change it. I want to see how Proxmox handles assigning vGPU resources with the changes in 6.8 before trying to go down that road again.
just fyi, my patches were applied.
i think not every package was bumped/built yet, but most of them should be on the pvetest repository
i think not every package was bumped/built yet, but most of them should be on the pvetest repository
Awesome!
Did I get this right, that the gui will be usable again?
Should we use mdev again?
What is the proper way now to use vgpu? Sorry, I lost the overview
while the underlying sysfs paths and exact mechanism changed a bit, we opted to map it to our old interface on the pve side
so the pve config is the same as previoiusly (so
we did this because
* we hope there won't be any more of such changes (fingers crossed)
* to keep the old configs working on upgrade
so the pve config is the same as previoiusly (so
hostpci0: 000:XX:YY.Z,mdev=nvidia-123) even though there are technically no 'mediated devices' involvedwe did this because
* we hope there won't be any more of such changes (fingers crossed)
* to keep the old configs working on upgrade