Recent content by _gabriel

indeed I mean "Firewall" (post edited). If Firewall not enable, no rules are applied so LXC should works out the box. ipv6 is, by default, SLAAC which doesn't dhclient. I have no experience with dhcp ipv6. EDIT: try increase timeout in /etc/dhcp/dhclient.conf uncomment lines : timeout & retry

PVE Firewall is only active if set to "Yes" under Datacenter \ Firewall \ Options \ Firewall. Try set to "Off" to globally turno off PVE firewall, as the default. BTW, IPv6 clients require accepting ICMPv6 packets.

is PVE firewall active ?

as VM within PVE or physical external ? is your Edge router have IPv6 ? IPv6 uses RA to get IPv6 prefix from router then generates its own IPv6 itself , it's not like IPv4 DHCP. BTW, /etc/sysctl.conf is no more used since Debian13, *.conf are in /etc/sysctl.d/ EDIT: Just tried a debian13 LXC...

What distrib LXC used ? What about cat /proc/sys/net/ipv6/conf/eth0/accept_ra ?

You have errors with new server 2019 VM, so the migration and related is not the root cause.

forget migration until clean VM has errors.

There was bug in PVE 9.0 with ISO uploaded to ZFS. https://forum.proxmox.com/threads/proxmox-ve-9-0-iso-upload-corrupts-some-windows-server-2025-isos.169531/post-791724

add >/dev/null 2>&1 to your command

why ? keep the tunnel p2p with custom AllowedIPs

1 is not required as virtualization is not available when cpu type is not "host". 3 is not easy as just switch. requires forced virtio scsi drivers installation : automatic way https://forum.proxmox.com/threads/a-small-game-changer-for-windows-migration-to-proxmox.181582/ @OP : what is your...

VBS silently enables virtualization, even if hyperv or WSL not enabled. https://forum.proxmox.com/threads/proxmox-ve-8-4-14-and-virtualization-based-security-vbs.174821/

Modern Windows like Win11 or 2025 virtualizes itself (=nested virtualization) when cpu type is set to host.

Microsoft allows downgrade. you need to get media and product key yourself or ask your OEM manufacturer. Media/Keys sources are not really relevant, proof of the original 2025 purchase is. You can try the eval ISO to dig out. win11 eval ISO can be used too as they use same binaries, same build...