Search results

once VirtIO set, is Intel E1G kept is incompatible drivers listing ? (you need to install virtio drivers, see the docs)

set vNIC to VirtIO

don't forget httpS://ip:8006/

aes is already in x86-64-v3 hv* args are already applied when guest os type is set to Windows

Router and Proxmox (when firewall not used) has nothing to do with network between guests. Try with enabling local Administrator. EDIT: Try disabling guest's Windows firewall

no, I suggest you one way. ZFS is the way for multi boot disks, but it's slower because the overhead for checksum and integrity, even more with none datacenter drives. ZFS is enterprise oriented.

has nothing to do with network between guests. triple check within your guests. No third party app within guest ? Have you multiple Windows accounts ? Windows 11 lock out account after multiple failure. edit: do you use hostname to connect ? if yes, try ip

nested-virt is available by default with host vCpu , has it changed since PVE9 ?

Sizes can be set with "Options" button during install. if you don't need iso, keep installing PVE on the 500GB disk ( installer will create a ~380G local-lvm Datastore ). Just remember if you reinstalling PVE, the default local-lvm Datastore will be erased. PVE installer always erase the "Target...

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