Recent content by kcybulski

I I updated over the weekend and tonight there was one error that stopped the nightly task. This task was triggering this error pretty regularly. I was hoping this would be resolved after it worked for three days without a hitch.

Hi, I updated MSSQL to driver 271 and the 129 error is back, although it is less frequent but it is back. I am going back to 208 tonight.

I'm fine with "If you enable bitmap persistence, it's your responsibility to clear dirty bitmap if you make changes to VM storage" policy. Krzysztof

On VM that is shutdown ? Any changes to storage will be done by Admin (or Admin controlled scripts). You can make this future opt in, add check box to VM storage config "Preserve dirty bitmap after shutdown" so admin know about limitations. You create snapshot after power down and delete it...

Sorry to bring back old thread. What about creating snapshots after VM power down ? 1) If there are no changes to storage when VM is off you delete the snapshot and keep bitmap before start/backup, 2) if there are changes you keep snapshot and return error and ask admin to delete snapshot...

Hi, It is possible to block account from sending outgoing emails if there was more than 100 messages send in last minute ? In almost all cases this mean user password was stolen, and is used to send SPAM. Best Regards Krzysztof

The migration started now. Thanks.

pvesm list local-ssd | grep 105 local-ssd:105/vm-105-disk-0.qcow2 qcow2 136365211648 105 I can't delete the the disk from local-ssd Cannot remove image, a guest with VMID '105' exists! You can delete the image from the guest's hardware pane But in Hardware tab of VM there is no unassigned...

Hi, I have proxmox 6.04 cluster, upgraded from 5.4. When I try to do offline migration of VM between servers I get error: storage 'local-ssd' is not available on node 'proxmox3' The local-ssd storage is not used by this VM. What can cause this error ? VM configuration and full log below...