Search results

You must distinguish a reliable way of testing GPU passthrough on the VM first, don't mind about what weirdness you observe at this point the console blanking on the physical console is influenced by video=vseafb:off video=efifb:off and also nomodeset I don't think i forget something here you...

if the monitor goes black and only VNC is working that is a good thing :)

FWIW, i now have my RADEON VII working in pass through again for a linux VM. Feel free to setup a private chat to discuss your setup. Paired with NX (nomachine.com) it works at extreme speed and high quality, even with the free version.

please make sure it is the right bios, i only guessed

best way to understand what is going on is to enter the shell and stop start VM from there, ### must be replaced with VM-ID qm stop ### qm start ### qm list you must also configure like this here is share a configuration that workd for me, the line is appended to what was in...

this appears to have resolved the issue, i hate solutions like this but this time it didn't matter too much, rrd data can be harvested regardless

Oct 22 18:03:01 pmx pmxcfs[386322]: [status] notice: RRDC update error /var/lib/rrdcached/db/pve2-vm/138: -1 Oct 22 18:03:01 pmx pmxcfs[386322]: [status] notice: RRDC update error /var/lib/rrdcached/db/pve2-vm/134: -1 Oct 22 18:03:01 pmx pmxcfs[386322]: [status] notice: RRDC update error...

i continuously have this issue, there is no fix in sight, the clock is in sync continuously, even for VM which are stopped

you should really consider upgrading the bios Version 7B89v1E Release Date 2020-06-16 File Size 9.28 MB Description - Updated AMD AGESA ComboAm4PI 1.0.0.6 - Fix HDMI audio lost issue when use AMD RX570 vga card.

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