I am keeping here my progress on this, at the moment I’ve created an ansible role which should cover everything: GitHub - paolomainardi/framework-desktop-proxmox-iac: This repository contains Ansible, Terraform and other scripts used in a lab enviroment (take it at your risk)
I am not using the warmup procedure, as at the moment at least for me, has the same defect of keep the gpu in a broken state if stopped.
I upgraded proxmox on my machine and GPU Passthrough broke. It seems like 6.17.2-2-pve kernel is the issue. I reverted to 6.14.11-4-pve and it’s working again.
Thanks for the hint. In step five, I explicitly mention that I have extracted this vbios file (since I was confused about the vbios files going around). I did not download it from a page, and to be sure, that people do not get the wrong one, I posted the SHA256sum.
Also @AquaMorph: I can confirm that 6.17.2-2-pve is not working.
Hey,
I am trying out your scripts to compare performance in VM vs lxc.
Few remarks:
- The network configuration stuff could be improved and made more intuitive:
Per default, it uses a gateway10.0.0.1and an ip10.0.0.<LXC-ID>. Some more hints how this relates to the generalvmbr0would be appreciated, or a config setup that reflects the existing configured network.
Also, for any LXC idea >255 this creates non-valid ips. - Is there any reason, why both the “old script” (option
030) exists in parallel to option031?
Any chances that this will get in a more stable situation? I’m still hesitating to get the Framework Desktop reading the proxmox related topics, especially this reboot bug.
Would like to replace my 6 years old desktop and use it for a couple of Linux and Windows VMs .
Simply waiting for proxmox to get a more recent kernel is likely the easiest solution.
Hey @beralt
Regarding 1)
Yes, that could be improved like asking for a network-prefix or so. It uses per default 10.0.0.X thats right, if you have higher IDs just replace the prefixed ip, if you dont like it. PVE IDs start with 100 and 255 is the end of the ip octet, the recommendation however would writeout invalid ips, yes. Not sure on how to change this to the better. Open to feedback or a PR.
Regarding 2)
I created the nailed down AMD version with specific ROCm first and then generalized the script to cover both ROCm and Nvidia too. If the generalized script is final, the amd version can be removed, yes.