Search results

Open new Thread for your case. Then post your Ceph configuration into. (replicas/network/disks model). Try move a VM outside Ceph.

https://github.com/pbatard/rufus/issues/2568#issuecomment-2387934171 Then retry

EDIT: Pressing "Esc" from noVNC Keyboard wake up VM here (test with a vanilla Debian 12 & vanilla Ubuntu 24 ) BTW : in Debian 12, "Automatic Suspend" is set to 20 minutes ( weird, should be inactive by default if VM detected). and "qemu-guest-agent" package is auto installed. in Ubuntu 24...

Fleecing is PVE side. https://pve.proxmox.com/pve-docs/chapter-vzdump.html#_vm_backup_fleecing

"Non local" = "not over WAN" PBS require fast network and disks to prevent timeout in source VM. There is "Fleecing" option nowadays can mitigate some slow cases.

Non local Proxmox Backup Server ?

because your issue is different. VssOption only prevents breaking SQL diffirential backup chain from another within-guest backup software.

Have you sudo apt install qemu-guest-agent + set QEMU Guest Agent to Enabled in PVE - VM - Options ?

Homelab with consumer disks should do backup before RAID.

its usage related. Enterprise should use ZFS mirror as boot/system (at least ZFS partition mirror)

ZFS will most wear out SSD than cluster/logs itself.

indeed, I was reading too fast. Reproducible here. For use case, where PBS Datastore is only USB, I only start PB-Proxy service during backup/sync/GC/verif then stop PB-Proxy service and unmount drive to allow hotplug.

There is custom binaries with enabled multi way concurrency in fetching chunks Post in thread 'Abysmally slow restore from backup' https://forum.proxmox.com/threads/abysmally-slow-restore-from-backup.133602/post-779127

size indicates an empty disk

if PBS datastore is attached to PVE, you need to disable PVE side too. /sbin/pvesm set PBS-DatastoreName --disable 1

is for Arm64 cpu You need a x64 iso.

Updates are Fully Cumulative since Windows 10, there isn't diff between build July 2025 and a Monthly updated RTM build since October 2024. Agreed and thanks for your reports , but as new Topic to avoid confusion.

so you can edit previous posts to correct wrong statement. BSOD unsupported processor is present only with June 2025 ( kb5060842 ) Microsoft fixed it with July 2025 ( kb5062553 )

Have you tried with "RTM" Windows 24H2 build 26100.1742 to confirm if related ?

because