Recent content by luckman212

Ok thanks. I removed it from the PBS GUI just by clicking the little red trash icon. I guess it would re-appear if I benchmark again. I don't know about opening a bugreport - is it actually a bug? (or a feature...?)

Today when I logged in after updating to 4.2.0 I noticed a new item in my Datastore (NFS share from Synology) called host/benchmark (screenshot below) What is this, is it expected to be there?

I reduced the # of API calls by writing a shell function and doing some of the heavy lifting in JQ, but it's still a but clunky. Ok, thanks for confirming at least. Maybe this is something that can be improved in the future.

I have some maintenance scripts where I need to pause/resume a set of VMs on my PVE 9.1 cluster. I want this script to operate on all VMs that are set to auto-start (onboot=1) I found the /nodes/{node}/qemu API endpoint, but sadly the onboot parameter is not included in its output. I can get...

I have these too. Is there any way to stop them from even reaching the journalctl log? They are filling up my Proxmox GUI log screen...

Same issue! PVE 9.1.1 + Synology DSM 7.3 I have tried setting node.session.scan = manual in /etc/iscsi/iscsid.conf and then deleting the IPv6 nodes but that doesn't survive a reboot. Help!

Just adding here, I had a similar Code 43 issue that I was tearing my hair out over. Spent days trying to get it working. See github issue #387 In the end, I rolled a brand new VM (everything else stayed the same) and voila, it worked fine. Worth a try maybe?

Nice! What's the correct way to update a PVE9.0 node to 9.1? would it be just apt update apt dist-upgrade

Just adding a data point: I also experience this error from time to time on my 9.0.11 cluster

Anything new/different here, 2 years and 2 major versions later? I'd also like to know if putting my 3 PVE 9 nodes behind a reverse proxy so I can access e.g. "proxmox.mydomain.lan" without worrying about which node might be up/down or rebooting etc...

So far so good, a few hours in 3-node cluster running PVE 9.0.11: (2x) Intel 285H + (1x) Intel 225H Also running https://github.com/strongtz/i915-sriov-dkms for iGPU passthru, working...

Got it, thanks @patch Yes I updated to 6.14.8-2 just now and vfio is sort of working again for me with i915-sriov-dkms driver 2025.07.22 But, my Win11 vm isn't getting accelerated graphics anymore for some reason. But, the VFs are there root@pve01:~# { dmesg | egrep 'VFs?$'; lspci | grep VGA; }...

Is proxmox-kernel 6.14.8-2~bpo12+1 still only available in the pvetest repo? Any idea when it will flip over to pve-no-subscription?

Sorry if this is the wrong place to ask but could you point me in the right direction for how to generate/switch to the self-compiled 6.14.8 kernel?

@floh8 I found a very similar request already, so I added this suggestion to it: https://bugzilla.proxmox.com/show_bug.cgi?id=6014#c1