Search results

I am waiting for NVIDIA move.

Those commands did not help. I am currently speaking to Nvidia enterprise support Tier II to fix this. They asked me to talk with Proxmox support team so i also sent them support ticket.

So the upgrading firmware did not help. I am looking for next steps. Already wrote to asrock support, also i will write to nvidia but i think it might be motherboard issue. And thinking what more can i do more. Anyway i would like to thank you for your suggestion. If you need for example RTX5090...

Trying some 4 extra parameters to see if it will help or not. Will report when issue happens again. quiet idle=nomwait pci=nocrs pci=realloc processor.max_cstate=5 amd_iommu=on iommu=pt vfio_iommu_type1.allow_unsafe_interrupts=1 vfio-pci.ids=10de:22e8,10de:2bb1 initcall_blacklist=sysfb_init

Hmm, Wonderins if this is the same case as mine ? I am getting issue when guest VM powers off, then i got those issues and also CPU soft lockup and i cant use that GPU afterwards. https://forum.proxmox.com/threads/passthrough-rtx-5090-cpu-soft-bug-lockup-d3cold-to-d0-after-guest-shutdown.168424/

Upgraded, another 2 days passed and i got soft lockup and the same issue again :( Si it is still not solved.

@adolfotregosa oh i get it, i thought it was requirement to get it stable. Fow low idle yeah that os ok. I will be looking into switching between nvidia and vfio but honestly first thing that came to my mind is to fire up vm with nvidia driver istead of messing in proxmox. Do you have some ready...

Where did you read that binding nvidia driver when GPU is released and unbinding it when it is going to be passthrough is requirement ? I thought this was needed for older GPUs. And that the resetting script wont work on newer cards. Can you send me some link to this ? I have flashed some...

I am using it but jus saying that in seabios i had crash before 100% times and after that firmware upgrade i am not getting it. This is just some indicator that i am on good path.

@adolfotregosa well i had some nice progress already ! Before that firmware upgrade, when i tried to passthrough more than one GPU (so 2 gpus) to linux VM using seabios then i had 100% failure resulting in d0 d3 error + CPU soft lockup. ! Now i flashed those two and i tried seabios and it works...

@adolfotregosa Still, do you think loading nvidia driver in proxmox still makes sense / is it needed ? I am wondering ... Actually if i am correct. Without loading nvidia, i think GPUs are taking 100watts instead of 10w when idle. Need to double check it.

Interesting. I flashed one and then booted with two RTX 6000 and it even sees that one does not need this anymore. Interesting..... If that will work, i will be obligated to give you something !!!! Flashing everyrhing i have and will see if this issue will show up again.

You had exactly CPU lockup in your case exactly ? What was happening in your case can you tell me more ? EDIT: sure will take a look tmr. I am wondering if i can do that in windows VM xD - will see.

There is no nvidia drivers on proxmox as i am using passthrough. No drivers at all and all are blacklisted so that only vfio binds to those GPUs. Well RTX6000 do not have newer bios as they were just released. And for 5090 i will take a look but i dont think that is the issue as all GPUs have...

This happens usually within 1-48 hours after shutdown of guest VM and both Linux and Windows VM. When i was testing it, i could not get that result but users are doing something or there is some exception going on here. And when that happens, i am unable to reset that GPU and when i unbind...

I think i have the same problem but i have created new thread. Were you be able to fix this ? Already fighting with that 2 weeks and i need to fix this asap ! Got issue with RTX5090 and RTX PRO 6000 so i guess this might be passthrough issue rather than nvidia/amd specific. My thread

EDIT2: I think this solved the issue. Still confirming. https://forum.proxmox.com/threads/passthrough-rtx-6000-5090-cpu-soft-bug-lockup-d3cold-to-d0-after-guest-shutdown.168424/page-2#post-795256 EDIT1: Got response from nvidia that they were able to reproduce this issue and they are thinking...

Had the same issue when i was using vmbr on eno1 interface (eno2 is unplugged whole time). Tried many things. But then i just made bond0 lacp3+4 from eno1 eno2 and then vmbr0 i mage on top of bond0 and it works. I don't have packet lost anymore while before i had like 30% packer lost on every...

Hello guys. After struggling with this problem fro a year in OVH datacenter i finally might have something ! Standard options in sysctl are: vm.dirty_background_ratio = 10 vm.dirty_ratio = 20 And when my SERVER HAVE 265GB or DDR memory !!! - then : 256 GB * 20% = 50 GB So in that case if i am...

Its a mess and i had problem. I will try with those here, thx for tip. I will respond if i succeeded. EDIT: Yep, this solved all my problems :)