Search results

default ext4/Lvmthin for datastore will be fine and the fastest. e.g: 500G for PVE and iso (custom sizes at install : disk = 400G and maxvz = 0 to not create the default local-lvm Datastore on the 500G ) 1 Lvmthin datastore per 1TB NVMe Restore backup from PBS in case of emergency.

-cpu host,-hypervisor,model=1 alternative boot ok post December 2025 Windows Update. -cpu host,-hypervisor,model=1 forces EPYC 1th gen code name "Naples" but better cosmetic as real processor name displayed. -cpu EPYC,-hypervisor model=49 forces EPYC 1th gen + override model to 2th gen code name...

if creds are asked, then this is within guest problem or wrong/duplicate ip or wrong/duplicate hostname

That's the sentence when PVE is publicly exposed. Please, use PVE to whitelist autorized ip or VPN.

Same after today Microsoft Windows Update. args: -cpu EPYC,-hypervisor is required instead args: -cpu host,-hypervisor / args: -cpu: EPYC-Rome-v4,-hypervisor

Seems nested virt. active by default since Win11. Try 'max' vcpu type : cpu: max args: -cpu max,-hypervisor

"host" vcpu type for Win11/Win2025 guests is slower than x86-64-v2-aes/v3 ( best is "max" ) because nested virtualization is often active because of VBS, where other vcpu type prevent nested virt.

No problems and reliable here with two small cases for Sync Job over SMB over WAN , a not optimal path and not recommended but works fine and speed is honorable : 1/ since 3y : Datastore over SMB over WAN, Sync from local Datastore USB HDD ( ~2H daily for 15~20GB pulled said in summary sync job...

EDIT: Dit you add back the Datastore in the PBS side ? with "Avdanced" tick to reveal "Reusing existing datastore"

Fleecing mitigates, but the recommended and safest is local BPS backup then Sync over WAN/VPN. Fleecing from the docs : When a backup for a VM is started, QEMU will install a "copy-before-write" filter in its block layer. This filter ensures that upon new guest writes, old data still needed for...

Can be your http application only accepts LAN IPs

https://www.proxmox.com/en/services/training-courses/videos/proxmox-virtual-environment/whats-new-in-proxmox-ve-9-1 typo "for Kernel 16.7"

yes

"max" should be the best performance. "x86-64-v2" without aes is for ancient cpu, what is your real cpu ?

"host" is not more the fastest since Windows latest version often enables virtualization which triggers the unwanted nested virtualization.

post screenshot of the Controller tab. No RAID does not meant no RAID controller.

Don't forget to enable "Max Performance profile" in BIOS and double check if Disk Writecache is enabled, often it's disabled because designed for RAID embedded cache usage. BTW, I repeat, try with Lvmthin before all the tuning about ZFS. It could be that your problem is elsewhere.

You can try "max" CPU type

Try disabling Windows Firewall "Remote Desktop" UDP-In rule to dig out.

I don't see the relationship with the Agent. is PVE firewall enabled ? is RDP over UDP used ?