Recent content by dcsapak

i did try to reproduce but couldn't, more information about your setup (ct/ceph config etc.) would be useful. does this persist after you reboot your nodes?

no, AFAIK the open telemetry plugin in PVE only supports json currently.

can you post the full vm config? (qm config ID) and which driver did you try to install exactly (on which windows version?) EDIT: also the mapping config would be interesting

yes that is possible... did you try with 'pcie_aspm=off' on the kernel commandline? alternatively you could try to set 'vfio-pci.disable_idle_d3=1' to prevent the card from going to d3 state in idle with the vfio-pci driver

hi, first there is an easier way to get to the sysfs path: /sys/bus/pci/devices/<id>/ so in your case /sys/bus/pci/devices/0000:04:00.0/ could you try with that path? echo 2 > /sys/bus/pci/devices/0000:04:00.0/sriov_numvfs and if it does not work either, could you check the...

can you check the file-restore logs under /var/log/proxmox-backup/file-restore (on the Proxmox VE host)? this message appears usually when there is a filesystem in use in the guest that is not readable with a linux kernel also, please update your PVE installation, 8.1 is really old and missing...

can you please post the complete journal output from the last boot (journalctl -b) ? maybe we can see more what might be an issue? i have an arc pro b50 here in my workstation and after updating the firmware it works fine

had a very similar issue on my (launch) ryzen 1700, tried some things from https://wiki.archlinux.org/title/Ryzen but in the end the only thing that solved it was to replace the cpu with something newer...

possibly, but hard to say with the data here. you could try things like disabling power state management (e.g. in the bios of with pcie_aspm=off on the kernel commandline) sorry if my last post was badly worded, what i actually wanted you to test (if possible) is leave one of the currently...

Until there is a patch available, here is a documented mitigation: https://github.com/V4bel/dirtyfrag/tree/master#mitigation (EDIT: i know the link was in the first post already, but wanted to explicitly mention the mitigation section)

maybe a different pool/allocation policy scheme makes more sense for you? see e.g. the 'weekday' scheme in the docs: https://pbs.proxmox.com/docs/tape-backup.html#weekday-scheme

yes i can confirm. the bug is that the cli parameter has the wrong name on the api the parameter is named 'group-filter' and the cli only passes it's parameter through to there i sent a patch to the list to correct the cli parameter name to 'group-filters'...

it's just a general requirement that the pdm needs network access, otherwise it can't do anything. I'd not read too much into the 'dedicated' wording here. Of course it depends on the actual setup what kind of nic is needed. e.g. with many remotes the bandwidth requirements increase

ok thanks for the logs. while the ubsan line is something somebody should take a look at, i think it's also just a symptom of the underlying issue. if the card is not in use, i doubt this is a software bug since the kernel does not just randomly disconnect pci devices if they're not doing...

just fyi: we have a table of tested driver versions with kernel compatibility in our wiki: https://pve.proxmox.com/wiki/NVIDIA_vGPU_on_Proxmox_VE