Recent content by davlaw

Another occurrence, reviewing the log for the task it appears to be unable to open file/path for the VM conf file and is unable to update/remove the lock status So since this log would indicate issue is at the proxmox node? INFO: transferred 4.63 GiB in 259 seconds (18.3 MiB/s) INFO: adding...

Gonna add one more thought, qemu-guest-agent. Since its required for the snapshots on the guest. Any version requirements there? I do have a few older windows VMs that I might have a problem Getting any newer version for..

Guess I can add something I just came to mind, I have changed my tape backups frequency from daily to every 2 hours. Could there be some interference when tape backup comes across a VM that is being backed up?

I have random occurrences of VM being left in a "locked for backup" in PVE Since this involves both PBS and PVE I'm not sure where this should be posted, but hope the whole proxmox team will see this. I am at a loss, but suspect under-powered (such as bandwidth) network or other hardware...

I have seen things like this when there is a timeout, not sure how long it waits on getting a "lock"

someone please lock/close this tread there is no longer any useful information here

I don't have much to add to your report with your environment and only am replying because I have seen VMs get locked as well. But in my case the are locked in "backup" state with no backup currently being performed. PBS is involved so I was not sure which on is the cause . Apology if not...

Kind of facing similar conditions, No client for windows and if they did most likely would not work on my older windows vms anyway. I have spun up 4 debian vm's that I used as "bridges", mount the shares from the windows machine to and then use the backup client to backup the data. Its not a...

Any value in our environment? Looks like its been around a few years but I stumbled on it today researching something else Guess if it was a "hot" item I would find more on it, but maybe it has a niche use case?

we have a winner, as noted above restart of the vm in question was needed

found this https://forum.proxmox.com/threads/solved-pve-certificate-expires-in-more-than-2-years.79152/ while the certs are now have valid dates, spice still does not like them... so reboot vm in question and last resort the node. We will see

Well here is what I have ended up with so far pvecm updatecerts --force Gives me the following (re)generate node files generate new node certificate CA expires in less than 2 weeks, unable to generate certificate. viewing ssl cert data shows vailid sine 2023-01-25 05:14:45 expires 2023-02-06...

I'm getting Mar 09 04:25:45 vlogic3 QEMU[2449776]: kvm: warning: Spice: error:14094415:SSL routines:ssl3_read_bytes:sslv3 alert certificate expired I'm off to research updating certs, but noticed the comment above about the restarts

Thank you sir.. very true

Crap, just saw it.. CNL vs CLN. that should solve it?!??!