From: "DERUMIER, Alexandre" <alexandre.derumier@groupe-cyllene.com>
To: "pve-devel@lists.proxmox.com" <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH-SERIES qemu/qemu-server/manager 0/1] add and set x86-64-v2 as default model for new vms
Date: Thu, 18 May 2023 05:03:08 +0000 [thread overview]
Message-ID: <29c413366dac0555a4bc5ca79859e5e2ec4c1e37.camel@groupe-cyllene.com> (raw)
In-Reply-To: <1684308750.d03m3tvuwp.astroid@yuna.none>
> FWIW, there was a v3:
Yes, this was last version.
The end of discussion was here:
https://lists.gnu.org/archive/html/qemu-devel/2021-06/msg02128.html
I wasn"t merged, because moslty, you can't have spectre/meltdown/...
mitigation enabled cross amd/intel, and also, generally users don't mix
intel/amd, so it's already possible to choose the lowest inte/amd cpu
model of the cluster.
Personnally, I think it could really be usefull for mixed intel/amd
cluster. (as kvm64 will not work with newer distros). It's better than
kvm64 anymay. (but no mitigation).
a better way could be to auto choose the best compatible cpu model
across cluster for user at vm creation.
with some kind of new virtual "best" cpumodel at vm creation only (then
the correct best compatible cpu model is compute and write in vm
configuration).
We could stream host cpumodel/revision/flags with pvestatd,
then compare flags to choose the correct model.
(mitigations autotuning could be great too)
all flags are documented in libvirt here:
https://gitlab.com/libvirt/libvirt/-/blob/master/src/cpu_map/
the simple algo is something like:
- if nocluster/single node, set cpumodel to max/host
- elsif cluster have only intel hosts, find best intel cpumodel
- elsif cluster have only amd hosts, find best amd cpumodel
- elsif cluster have mixed intel/amd hosts, find best x64-64-vX cpu
model
prev parent reply other threads:[~2023-05-18 5:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-17 7:02 Alexandre Derumier
2023-05-17 7:02 ` [pve-devel] [PATCH qemu-server 1/1] cpuconfig: add new x86-64-abi models Alexandre Derumier
2023-05-17 7:02 ` [pve-devel] [PATCH pve-qemu 1/1] patch: add 0001-add-cpu-models-x86-64-abi.patch Alexandre Derumier
2023-05-17 7:46 ` Fiona Ebner
2023-05-17 8:25 ` DERUMIER, Alexandre
2023-05-17 9:08 ` Fiona Ebner
2023-05-19 9:16 ` Thomas Lamprecht
2023-05-17 7:02 ` [pve-devel] [PATCH pve-manager 1/1] qemu: processor : set x86-64-abi2 as default cputype for create wizard Alexandre Derumier
2023-05-17 7:34 ` [pve-devel] [PATCH-SERIES qemu/qemu-server/manager 0/1] add and set x86-64-v2 as default model for new vms Fabian Grünbichler
2023-05-18 5:03 ` DERUMIER, Alexandre [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=29c413366dac0555a4bc5ca79859e5e2ec4c1e37.camel@groupe-cyllene.com \
--to=alexandre.derumier@groupe-cyllene.com \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox