Re: [pve-devel] [PATCH qemu] api: qemu: create: default cpu to x86-64-v2-AES

[Thomas Lamprecht <t.lamprecht@proxmox.com>]

Am 22/10/2024 um 14:15 schrieb Maximiliano Sandoval:
> Thomas Lamprecht <t.lamprecht@proxmox.com> writes:
> 
>> And even then, would this still break restoring backups made before that
>> change?
>> If, this would fall under the changes that need versioning the guest
>> configs. Which naturally is possible but is IMO also not something I'd
>> do lightly, as that's something that might have wide-reaching consequences.
> 
> Would it make more sense to do this only for the CLI tool, and only when creating new VMs?
> 

Hmm, it would feel a bit odd to me to single that specific "mismatch" between
UI default and CLI/schema out but ignore the others, like e.g., the memory
default of 2048, or some dynamic defaults like the OS-type dependent ones.

And while it would have reduced impact, it would be still a breaking change
that might affect peoples automation/scripts.
But if more than just the CPU type would be looked at, and adapted such that
UI and CLI behave more the same, it might be indeed a feasible way to improve
UX slightly on the next major release next year.
Conveying the reason for different defaults and how one can look into which
one will be applied would warrant a short paragraph in the docs then too.
And taking the chance and looking at the CT story on this would be great too,
e.g., like is 512 MB really still a good default for UI/CLI, or unprivileged
vs. privileged.


_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel