I don't know... let me check with API and see if there is anything useful in the API response first... in general I would not expect API client or CLI command to follow with a grep of journal log to look for success/failure
No, pve01 is online (all nodes are online…) Actually, when I checked in the GUI, I realized somehow that HA was disarmed. Must have been left in an inconsistent state after the last shutdown failure. After I re-armed HA, the ha-manager...
The update to 9.2.20 hasn't changed anything, the ha-manager crm-command node-maintenance enable pve01 command still does not succeed in setting the node to maintenance mode.
The node(s) just do not ever enter maintenance mode. No error message is printed, and I don't really see anything relevant in the syslogs either. I upgraded to PVE 9.2.20 yesterday, so I will test again
I tried to look up how to filter by tag in the Proxmox VE GUI, it says to use e.g. tag:windows but that didn't work for me (PVE 9.2.20). I had to just type "windows". But that also finds VM with name "windows03" which might not be actually tagged...
This has been working for me for many months, up until very recently
ha-manager crm-command node-maintenance enable pve01
Now, it's no longer working. Not sure why! PVE 9.2.18, 3 node cluster, no ceph
I decided to remove all virtio drivers and reinstall from v173 like you mentioned @_gabriel
I kept the disk on SCSI for now.
Will see how things go. Thanks
I had to disable driver signing enforcement with
bcdedit /set loadoptions DDISABLE_INTEGRITY_CHECKS
bcdedit /set TESTSIGNING ON
after that, I was able to install the virtio 302 drivers... with help from Driver Store Explorer to clean up the old...
I'm experiencing this problem (very infrequently) in my homelab.
It ONLY ever occurs with Windows VMs, which leads me to believe it's more nuanced than just "bad RAM" on the PVE host or the PBS server. I've done numerous diagnostic tests (memory...
@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.