Proxmox CPU type Windows 11

O

oak.h

New Member
Jan 6, 2024
7
0
1
Hello,

I would like to test Windows 10 to 11 upgrades on VMs running a Proxmox host that has an unsupported CPU. Is there a specific CPU type that I can use for these VMs so that even though the host CPU is unsupported the guest would see the virtual processor as supported?

I know its possible to clean install Windows 11 on any CPU via various methods but the point isnt about getting Windows 11 to these VMs but rather I need to test the upgrade process itself so clean install is out of question here.

Thank you for any input in advance!
 
Hello,

If you use any CPU type which is not `host` then QEMU will present the CPU as a virtual CPU and Windows and won't be able to tell whether it is supported or not. I would recommend to test the default CPU type `x86-64-v2-AES`.

e.g. this is how a virtual CPU looks inside one of my linux guests:

Code: 
$ lscpu
Architecture:             x86_64
  CPU op-mode(s):         32-bit, 64-bit
  Address sizes:          40 bits physical, 48 bits virtual
  Byte Order:             Little Endian
CPU(s):                   4
  On-line CPU(s) list:    0-3
Vendor ID:                AuthenticAMD
  BIOS Vendor ID:         QEMU
  Model name:             QEMU Virtual CPU version 2.5+
    BIOS Model name:      pc-i440fx-9.1  CPU @ 2.0GHz
    BIOS CPU family:      1
    CPU family:           15
    Model:                107
    Thread(s) per core:   1
    Core(s) per socket:   4
    Socket(s):            1
    Stepping:             1
    BogoMIPS:             8783.49
    Flags:                fpu de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx lm rep_good nopl cpuid extd_apicid tsc
                          _known_freq pni ssse3 cx16 sse4_1 sse4_2 x2apic popcnt aes hypervisor lahf_lm cmp_legacy 3dnowprefetch vmmcall
 
  • Like
Reactions: _gabriel
Maximiliano said:
Hello,

If you use any CPU type which is not `host` then QEMU will present the CPU as a virtual CPU and Windows and won't be able to tell whether it is supported or not. I would recommend to test the default CPU type `x86-64-v2-AES`.

e.g. this is how a virtual CPU looks inside one of my linux guests:

Code: 
$ lscpu
Architecture:             x86_64
  CPU op-mode(s):         32-bit, 64-bit
  Address sizes:          40 bits physical, 48 bits virtual
  Byte Order:             Little Endian
CPU(s):                   4
  On-line CPU(s) list:    0-3
Vendor ID:                AuthenticAMD
  BIOS Vendor ID:         QEMU
  Model name:             QEMU Virtual CPU version 2.5+
    BIOS Model name:      pc-i440fx-9.1  CPU @ 2.0GHz
    BIOS CPU family:      1
    CPU family:           15
    Model:                107
    Thread(s) per core:   1
    Core(s) per socket:   4
    Socket(s):            1
    Stepping:             1
    BogoMIPS:             8783.49
    Flags:                fpu de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx lm rep_good nopl cpuid extd_apicid tsc
                          _known_freq pni ssse3 cx16 sse4_1 sse4_2 x2apic popcnt aes hypervisor lahf_lm cmp_legacy 3dnowprefetch vmmcall
Click to expand...
Thank you, now the MS `HardwareReadiness.ps1` sas the computer is capable so thats a good sign. Lets see how the upgrade goes, fingers crossed!
 
You must log in or register to reply here.
Top Bottom