[SOLVED] (7.1) Windows 11 CPU Type

[kromberg]

I am trying to get a Windows 10 guest to upgrade to Windows 11 and keeps failing on the stupid CPU check. The host is running pve-manager/7.1-4/ca457116 and has a pair of Xeon E5-2680v3 CPUs. I have tried qemu64 and host, but it doesnt matter. I also modified the Windows 11 ISO as point out in the following post( the referenced youttube video ).

https://forum.proxmox.com/threads/windows-11-kvm-processor-not-supported.98149/#post-434998

What is the trick that needs to be done to satisfy the CPU check?

 

[dylanw]

Hi,

Could you post the Windows VM config file as well as the output pveversion -v?
Did you add a trusted platform module (TPM) [1] to the system and give it at least 4 cores?
Did you try to use the 'kvm64' processor, with the flags that Thomas listed, in the linked forum post? (kvm64,flags=+md-clear;+pcid;+spec-ctrl;+ssbd;+aes)

Best regards,
Dylan

[1] https://pve.proxmox.com/pve-docs/pve-admin-guide.html#qm_virtual_machines_settings

 

[kromberg]

VM config file:
root@odin:~# cat /etc/pve/nodes/odin/qemu-server/103.conf agent: 1 bios: ovmf boot: order=sata0;ide2;net0 cores: 4 efidisk0: datastore2s:vm-103-disk-1,efitype=4m,pre-enrolled-keys=1,size=1M hostpci0: 0000:04:00.0 ide2: datastore1:iso/virtio-win-0.1.208.iso,media=cdrom,size=543390K machine: pc-q35-6.1 memory: 16392 meta: creation-qemu=6.1.0,ctime=1638645805 name: azog net0: virtio=72:6A:21:66:DC:F5,bridge=vmbr1,firewall=1 net1: virtio=C6:D3:8D:3B:7C:AC,bridge=vmbr2,firewall=1 numa: 0 ostype: win10 sata0: datastore2s:vm-103-disk-0,size=100G scsihw: virtio-scsi-pci smbios1: uuid=68e87021-5393-492a-b1c9-b5b7eec22e34 sockets: 2 tpmstate0: datastore2s:vm-103-disk-2,size=4M,version=v2.0 vga: virtio,memory=512 vmgenid: 9fce4a0f-f1a8-449b-b098-2e241d01ed50

pveversion -v output:
root@odin:~# pveversion -v proxmox-ve: 7.1-1 (running kernel: 5.13.19-1-pve) pve-manager: 7.1-4 (running version: 7.1-4/ca457116) pve-kernel-5.13: 7.1-4 pve-kernel-helper: 7.1-4 pve-kernel-5.13.19-1-pve: 5.13.19-2 ceph-fuse: 15.2.15-pve1 corosync: 3.1.5-pve2 criu: 3.15-1+pve-1 glusterfs-client: 9.2-1 ifupdown2: 3.1.0-1+pmx3 ksm-control-daemon: 1.4-1 libjs-extjs: 7.0.0-1 libknet1: 1.22-pve2 libproxmox-acme-perl: 1.4.0 libproxmox-backup-qemu0: 1.2.0-1 libpve-access-control: 7.1-1 libpve-apiclient-perl: 3.2-1 libpve-common-perl: 7.0-14 libpve-guest-common-perl: 4.0-3 libpve-http-server-perl: 4.0-3 libpve-storage-perl: 7.0-15 libspice-server1: 0.14.3-2.1 lvm2: 2.03.11-2.1 lxc-pve: 4.0.9-4 lxcfs: 4.0.8-pve2 novnc-pve: 1.2.0-3 proxmox-backup-client: 2.0.14-1 proxmox-backup-file-restore: 2.0.14-1 proxmox-mini-journalreader: 1.2-1 proxmox-widget-toolkit: 3.4-2 pve-cluster: 7.1-2 pve-container: 4.1-2 pve-docs: 7.1-2 pve-edk2-firmware: 3.20210831-2 pve-firewall: 4.2-5 pve-firmware: 3.3-3 pve-ha-manager: 3.3-1 pve-i18n: 2.6-1 pve-qemu-kvm: 6.1.0-2 pve-xtermjs: 4.12.0-1 qemu-server: 7.1-3 smartmontools: 7.2-1 spiceterm: 3.2-2 swtpm: 0.7.0~rc1+2 vncterm: 1.7-1 zfsutils-linux: 2.1.1-pve3

It does have TPM v2.0 added along with 8 cores and 16GB of ram. I have tried kvm64, qemu64, and host as the CPU type all with the same result.

 

[0bit]

Use this script to bypass check
https://github.com/AveYo/MediaCreationTool.bat/tree/main/bypass11

 

[kromberg]

Which one of the two scripts do I run?

 

[0bit]

Which one of the two scripts do I run?

Skip_TPM_Check_on_Dynamic_Update.cmd

 

[kromberg]

After running that, the upgrade is still failing saying that the type is not supported. Even before running the skip, it would not complain about the TPM.

 

[kromberg]

Got the check to finally pass. Needed the machine type to be set to the q35 option.

root@odin:~# cat /etc/pve/qemu-server/103.conf agent: 1 bios: ovmf boot: order=sata0;ide2;net0 cores: 4 efidisk0: datastore2s:vm-103-disk-1,efitype=4m,pre-enrolled-keys=1,size=1M hostpci0: 0000:04:00.0 ide2: datastore1:iso/virtio-win-0.1.208.iso,media=cdrom,size=543390K machine: pc-q35-6.1 memory: 16392 meta: creation-qemu=6.1.0,ctime=1638645805 name: azog net0: virtio=72:6A:21:66:DC:F5,bridge=vmbr1,firewall=1 net1: virtio=C6:D3:8D:3B:7C:AC,bridge=vmbr2,firewall=1 numa: 0 ostype: win10 sata0: datastore2s:vm-103-disk-0,size=100G scsihw: virtio-scsi-pci smbios1: uuid=68e87021-5393-492a-b1c9-b5b7eec22e34 sockets: 2 tpmstate0: datastore2s:vm-103-disk-2,size=4M,version=v2.0 vga: virtio,memory=512 vmgenid: 9fce4a0f-f1a8-449b-b098-2e241d01ed50