Machine type latest missing for windows ?

[H4R0]

I would like to pin windows machines to "latest" but it is not in the list.

After the recent upgrade windows machines are set to "5.1", linux is set to "latest"

I know this is due to a workaround, but why is latest not available for windows ?

Windows machine:

 

[t.lamprecht]

This is by design, Windows cannot cope with the machine type changing and just will break in subtle or not so subtle ways sooner or later, and this is also what QEMU devs recommend after we had a discussion on their mailing list, due to a recent bug which we uncovered, where an ACPI change was not tracked and said change broke network and often also boot disks for Windows.

Why do you want to pin it to latest? Often those machine changes do not have a real immediate benefit for the end user - and you still get all the non-machine changes nonetheless when starting the VM with a new QEMU version.

 

[H4R0]

This is by design, Windows cannot cope with the machine type changing and just will break in subtle or not so subtle ways sooner or later, and this is also what QEMU devs recommend after we had a discussion on their mailing list, due to a recent bug which we uncovered, where an ACPI change was not tracked and said change broke network and often also boot disks for Windows.

Why do you want to pin it to latest? Often those machine changes do not have a real immediate benefit for the end user - and you still get all the non-machine changes nonetheless when starting the VM with a new QEMU version.

I only use windows for testing therefore I don't care about breaking changes.

If it is like now it's a set and forget option. The option would never be changed by end users.


I'm fine if it is just a config file option. I assume if I set machine type back to "q35" it will revert the change ?

BTW why does it create a "[clean]" config duplicate ?

 

[t.lamprecht]

I only use windows for testing therefore I don't care about breaking changes.

If you re-create Windows VM it will set to the latest version on creation.

If it is like now it's a set and forget option. The option would never be changed by end users.

That's the idea.

I assume if I set machine type back to "q35" it will revert the change ?

No, it will assume 5.1 or, if the QEMU version installed is older, the next actually available version.
As the update from 5.1 to 5.2 had the aforementioned breaking change in ACPI we must assume that to avoid breaking old existing VMs.

 

[shpasser]

I experienced the same here after upgrading from "proxmox pve 7.2" to "proxmox pve 7.3-3".

But my question is more about understanding.

When I created my Windows 10 VM I used "promox pie 7.2" with "Machine Type" "pc-i44FX", now after the upgrade to 7.3-3 the "Machine Type" reads as "pc-i44FX-6.2".

Q1) Why did the "Machine Type" version became 6.2?
Shouldn't it be 7.2 since I used "promox pie 7.2" to create the VM?

Q2) The highest version I can choose is 7.1, why is it?
Shouldn't it be 7.2?

Thanks in advance.

 

[t.lamprecht]

Q1) Why did the "Machine Type" version became 6.2?
Shouldn't it be 7.2 since I used "promox pie 7.2" to create the VM?

The machine version comes from QEMU, not the Proxmox VE (manager) version.

Q2) The highest version I can choose is 7.1, why is it?
Shouldn't it be 7.2?

See answer to Q1) above, newest QEMU available in Proxmox VE is 7.1.