Upgraded CPU, Windows 11 VM starts into repair when using "host"

[mehdital]

Went from an i5 10500 to an i5 13400. New motherboard and RAM as well. Virtualization activated from the bios. Proxmox boots fine. However, my Windows 11 VM is seen as running by Proxmox but Windows fails to start, and I end up in the repair page every time. The VM boots fine when I choose QEMU64 or KVM64 as CPU, but that comes with a big performance penalty and some programs crash on the VM when not using host.

Here is what I tried so far:
Upgrading to kernel 6.2
Removing all added devices (incl gpu)
upgraging machne type to q35-7.2

but none of the above helped.
What else can I try to fix this?

Here are my settings:

agent: 1
balloon: 0
bios: ovmf
boot: order=virtio0;net0;ide2
cores: 16
cpu: kvm64,flags=+pdpe1gb
efidisk0: local-zfs:vm-104-disk-0,efitype=4m,pre-enrolled-keys=1,size=1M
hookscript: local:snippets/cpu-pin.sh
hostpci0: 0000:01:00,pcie=1,x-vga=1
hostpci1: 0000:02:00.0,pcie=1
ide2: local:iso/virtio-win-0.1.225.iso,media=cdrom,size=519590K
machine: pc-q35-7.2
memory: 24576
meta: creation-qemu=6.2.0,ctime=1670252283
name: windows11
net0: e1000=76:D7:CA:24:DF:87,bridge=vmbr0,firewall=1
numa: 0
onboot: 1
ostype: win11
scsihw: virtio-scsi-single
smbios1: uuid=76df4de2-6920-40cc-a620-1f63e6844302
sockets: 1
tpmstate0: local-zfs:vm-104-disk-1,size=4M,version=v2.0
usb0: host=1209:4f54,usb3=1
usb1: host=046a:b102,usb3=1
usb2: host=05ac:024f,usb3=1
usb3: host=0bda:8771,usb3=1
vga: none
virtio0: local-zfs:vm-104-disk-2,size=1T
vmgenid: 4c307a89-cc94-4290-a88e-2b73b747d06d

and output of pveversion -v

perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
    LANGUAGE = (unset),
    LC_ALL = (unset),
    LANG = "en_GB.UTF-8"
    are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
proxmox-ve: 7.4-1 (running kernel: 6.2.16-4-bpo11-pve)
pve-manager: 7.4-16 (running version: 7.4-16/0f39f621)
pve-kernel-6.2: 7.4-4
pve-kernel-5.15: 7.4-4
pve-kernel-6.2.16-4-bpo11-pve: 6.2.16-4~bpo11+1
pve-kernel-5.15.108-1-pve: 5.15.108-2
pve-kernel-5.15.107-1-pve: 5.15.107-1
pve-kernel-5.15.85-1-pve: 5.15.85-1
pve-kernel-5.15.30-2-pve: 5.15.30-3
ceph-fuse: 15.2.16-pve1
corosync: 3.1.7-pve1
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.1.0-1+pmx4
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.24-pve2
libproxmox-acme-perl: 1.4.4
libproxmox-backup-qemu0: 1.3.1-1
libproxmox-rs-perl: 0.2.1
libpve-access-control: 7.4.1
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.4-2
libpve-guest-common-perl: 4.2-4
libpve-http-server-perl: 4.2-3
libpve-rs-perl: 0.7.7
libpve-storage-perl: 7.4-3
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 5.0.2-2
lxcfs: 5.0.3-pve1
novnc-pve: 1.4.0-1
proxmox-backup-client: 2.4.3-1
proxmox-backup-file-restore: 2.4.3-1
proxmox-kernel-helper: 7.4-1
proxmox-mail-forward: 0.1.1-1
proxmox-mini-journalreader: 1.3-1
proxmox-offline-mirror-helper: 0.5.2
proxmox-widget-toolkit: 3.7.3
pve-cluster: 7.3-3
pve-container: 4.4-6
pve-docs: 7.4-2
pve-edk2-firmware: 3.20230228-4~bpo11+1
pve-firewall: 4.3-5
pve-firmware: 3.6-5
pve-ha-manager: 3.6.1
pve-i18n: 2.12-1
pve-qemu-kvm: 7.2.0-8
pve-xtermjs: 4.16.0-2
qemu-server: 7.4-4
smartmontools: 7.2-pve3
spiceterm: 3.2-2
swtpm: 0.8.0~bpo11+3
vncterm: 1.7-1
zfsutils-linux: 2.1.11-pve1

 

[fschauer]

Usually the Windows installer requires the CPU type to be set to something other than host.
Once the installation is complete you should be able to set the CPU type to host.

 

[mehdital]

Usually the Windows installer requires the CPU type to be set to something other than host.
Once the installation is complete you should be able to set the CPU type to host.

From another thread, someone suggested adding hidden=1 to the cpu flags and disabling secure boot for the VM from the proxmox bios.
Adding hidden=1 fixed it for me and I finally get 95% of native performance with 3DMark Timespy benchmark! (passing all cpu cores to the VM, no other paramters)

 

[andrewchk]

From another thread, someone suggested adding hidden=1 to the cpu flags and disabling secure boot for the VM from the proxmox bios.
Adding hidden=1 fixed it for me and I finally get 95% of native performance with 3DMark Timespy benchmark! (passing all cpu cores to the VM, no other paramters)

Hi, I am new to the proxmox space, could you please tell me how to do such hidden=1 thing? I can't change the CPU type to host, blue screen or repair issue.

Thank you in advance.

 

[fschauer]

Hi, I am new to the proxmox space, could you please tell me how to do such hidden=1 thing? I can't change the CPU type to host, blue screen or repair issue.

Thank you in advance.

In /etc/pve/qemu-server/<vmid>.conf you can set this line:

cpu: host,hidden=1

 

[andrewchk]

Thank you for the reply.

I've added the line to the conf file, restarted the VM and got the same BOD screen. Then changed back to x86-64-v2-AES with hidden=1, and restarted at a keyboard layout selection screen. Removed hidden=1, and it boots up normally.

Any further hints would be highly appreciated.

Thanks.