Search results

coincidentally i also have an MSI motherobard (x370) the bios is up to date make sure Agesa 1.0.0.6 enabled BIOS is present to enable iommu groups which are essential for pass through if i understand correctly to my understanding, powering down the VM is required resettting the GPU or GPU's...

After spending many hours on this very topic. Stop buying AMD GPU. I was stupid enough to buy an AMD Radeon VII which also has the reset issue. Basically AMD should very well be able to fix this but simply ignores this topic. It is not even documented on their portal. File bug reports as much...

to reset the GPU between VM stop and VM start where pass through is applied do "lspci | grep VGA -A 1" for the correct pci id's use this script and replace XX: with the for mentioned ids Code: #!/bin/bash # #replace xx\:xx.x with the number of your gpu and sound counterpart # # echo...

This may be of interest to you, the guy likes to talk but hey, maybe there is something in there. https://www.youtube.com/watch?v=k-tnFzPaVBY This is the actual patch, note this is patch is unsupported and neither proxmox, neither AMD will support it either...

ah, yes. Run the script between VM with pass-through stop and start. FYI: yesterday i wrote an angry mail at AMD for not clarifying how to pinpoint or resolve this since two cases exist. One blaming the AMD CPU (first gen Ryzen only) and the second blaming the AMD GPU (unknown which) but no...

is passthrough working ?

FOR AMD GPU only do "lspci | grep VGA -A 1" for the correct pci id's use this script and replace XX: with the for mentioned ids #!/bin/bash # #replace xx\:xx.x with the number of your gpu and sound counterpart # # echo "disconnecting amd graphics" echo "1" | tee -a...

things to validate * is the rom of the expected size and is it valid ? * you may find this link useful https://www.techpowerup.com/vgabios/?architecture=&manufacturer=&model=5700+XT&interface=&memType=&memSize=&since= Installing the GPU drivers on proxmox will result in problems, do not do it...

this was solved by not using udhcpc as the dhcp client, it is unclear how to configure udhcpc to use -F $HOSTNAME to propagate the hostname in the dhcp lease request, using a different dhcp client fixes this terrible issue

SOLVED: this is exclusively caused by UDHCPC not having a suitable default config

same problem, LXC has hostname configured but does not register with the dhcpd service as with a hostname dhcp client used is udhcpc, passing the -F $HOSTNAME parameter fails

FWIW, all windows needs to do is look at the BIOS to know it is running in a VM :-)

Dear, For all proxmox VM i simply configure the hostname and the DHCP service maps it to an FQDN so i can ping myhost.sub.sub.mydom.tld Except for the one container i'm running, that does not work at all, whatever i try. The only difference i notice is the dhcp client here is udhcpc but i've...

yes, separate the network into functionality like (internet/mgmt/office) it will offer realistic segmentation and avoid mishaps

checking the output of dmesg for iommu and vfio keywords should tell you more

you may need to search /var/log/* instead, dmesg may be overflowing and not showing anything if you setiommu=pt then you should get: iommu: Default domain type: Passthrough (set via kernel command line) typically i also check on iommu in dmesg or /var/log/* there should be quite a bit of...

check for pvx kernel: iommu: Default domain type: Passthrough in the dmesg output with: dmesg | grep Passthrough

Did you update the 6.2 to the most recent version ? Did you consider supplementing the bios as a rom-option file to the VM ? personally is use both iommu= and intel_iommmu= to assure the mode is set correctly. For your setup: iommu=pt intel_iommu=on also try by including the nomodeset...

Don't take my word for it, here are a few considerations. be aware, very aware, if this proxmox cluster is running at home you are extending the office network to home and vice versa, you may be held accountable if anything goes wrong such as your home network is compromised. Unless you own the...

to my knowledge, if a device is performing outbound NAT only then the inbound will fail per default if no NAT is configured to do so. Same result.