Recent content by luckman212

@fiona thank you, clusterlog looks ok to me... pretty quiet root@pve02:~# cat /etc/pve/.clusterlog { "data": [ {"uid": 132, "time": 1787578686, "pri": 6, "tag": "pvedaemon", "pid": 1926470, "node": "pve01", "user": "root@pam", "msg": "starting task...

I'm getting these too, only on 1 node of my 3-node cluster (PVE 9.2.11) Is echo "1" >/etc/pve/.debug still suggested?

@damiengm they didn't tell you what they did? did they just turn off IPv6 completely on the interface, or were they able to somehow selectively disable it on the iSCSI portal only?

In case it helps anyone, I ended up settling on using v0.1.189 since it's WHQL-certified and 2012R2 strict driver signing requirements are satisfied without too much mucking around.

As of 2026-08-14 what is the suggested version of virtio-win drivers to use for 2012R2 VMs on PVE 9? I am using 0.1.221 and it seems to work fine. But worried about the comment above about buggy scsi driver... is 0.1.189 a better choice?

I stopped my Synology from advertising IPv6 on the iscsi targets with something like: nas_ip=192.168.10.10 sed -Ei "s/^(network_portals)=(.*)/\1=$nas_ip:3260/" /usr/syno/etc/iscsi_target.conf You can use Task Scheduler to run this code at startup.

Anyone got any stories (positive or negative) about this 7.1 kernel?

Eager to try this! My homelab uses 5Gbps USB-C Realtek r8157-based NICs for the storage network, and I have struggled with the DKMS driver. In 7.1 that driver is now mainlined into the kernel: https://lwn.net/Articles/1066121

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?