Windows Server 2022 Stucks after Restore Backup on different Host

[C0kkie]

Hello,

i tried to move my windows vm from a host to another with backup/restore method.
The problem is now that the vm stucks on boot on new system.
On old system the backup works if i restore it.
The only difference is that oldsystem is amd and the new one intel cpu

root@proxmox01 ~ # pveversion -v
proxmox-ve: 8.0.2 (running kernel: 6.2.16-19-pve)
pve-manager: 8.0.9 (running version: 8.0.9/fd1a0ae1b385cdcd)
pve-kernel-6.2: 8.0.5
proxmox-kernel-helper: 8.0.5
proxmox-kernel-6.2.16-19-pve: 6.2.16-19
proxmox-kernel-6.2: 6.2.16-19
ceph-fuse: 16.2.11+ds-2
corosync: 3.1.7-pve3
criu: 3.17.1-2
glusterfs-client: 10.3-5
ifupdown: residual config
ifupdown2: 3.2.0-1+pmx7
libjs-extjs: 7.0.0-4
libknet1: 1.28-pve1
libproxmox-acme-perl: 1.5.0
libproxmox-backup-qemu0: 1.4.0
libproxmox-rs-perl: 0.3.1
libpve-access-control: 8.0.7
libpve-apiclient-perl: 3.3.1
libpve-common-perl: 8.0.10
libpve-guest-common-perl: 5.0.5
libpve-http-server-perl: 5.0.5
libpve-rs-perl: 0.8.7
libpve-storage-perl: 8.0.4
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 5.0.2-4
lxcfs: 5.0.3-pve3
novnc-pve: 1.4.0-3
proxmox-backup-client: 3.0.4-1
proxmox-backup-file-restore: 3.0.4-1
proxmox-kernel-helper: 8.0.5
proxmox-mail-forward: 0.2.1
proxmox-mini-journalreader: 1.4.0
proxmox-widget-toolkit: 4.1.1
pve-cluster: 8.0.5
pve-container: 5.0.6
pve-docs: 8.0.5
pve-edk2-firmware: 4.2023.08-1
pve-firewall: 5.0.3
pve-firmware: 3.9-1
pve-ha-manager: 4.0.3
pve-i18n: 3.0.7
pve-qemu-kvm: 8.1.2-3
pve-xtermjs: 5.3.0-2
qemu-server: 8.0.8
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0

 

[C0kkie]

Ok

adding

args: -cpu SandyBridge,hv_relaxed,hv_spinlocks=0x1fff,hv_vapic,hv_time,+vmx

works, are there problems with the i5-13500?

 

[C0kkie]

Anybody a idea?

 

[bzb-rs]

remove all cpu flags and try with kvm cpu type.

If not remove all flags and change cpu type to kvm and then take an backup and try to restore on your destination host.

 

[davemcl]

After restore change CPU type to host or match the destination CPU.

 

[C0kkie]

KVM64 works, host doesnt

 

[cwt]

Do you get any errors in the log when starting the VM with host as CPU type? Or does it simply stuck on the boot screen? Did you run a different CPU on the previous PVE and what type was that?

 

[C0kkie]

Do you get any errors in the log when starting the VM with host as CPU type? Or does it simply stuck on the boot screen? Did you run a different CPU on the previous PVE and what type was that?

@cwt I dont see any logs it just stucks
on the previous PVE it was a amd cpu and now its a intel

 

[cwt]

Maybe you could try to set the CPU affinity, for example 0-3.

 

[C0kkie]

Maybe you could try to set the CPU affinity, for example 0-3.

doesnt work. I also found some other thread that its maybe related that i have wsl2 installed and it still makes problems with proxmox and intel

 

[C0kkie]

Someone else a idea?