From: "DERUMIER, Alexandre" <alexandre.derumier@groupe-cyllene.com>
To: "pve-devel@lists.proxmox.com" <pve-devel@lists.proxmox.com>,
"d.csapak@proxmox.com" <d.csapak@proxmox.com>,
"f.ebner@proxmox.com" <f.ebner@proxmox.com>,
"aderumier@odiso.com" <aderumier@odiso.com>
Subject: Re: [pve-devel] [PATCH pve-manager] qemu: bump max cores to 256 by socket
Date: Tue, 16 Jan 2024 14:08:21 +0000 [thread overview]
Message-ID: <5fd038cc440c6dfd4e97961f8e098dae4c3f328a.camel@groupe-cyllene.com> (raw)
In-Reply-To: <cc57273b-8f61-4a14-8758-39a9fc24e21b@proxmox.com>
>>Is the QEMU error message understandable? If yes, I don't see much
>>value
Well, indeed, the message is pretty clear.
maybe just add documentation about limit for q35 && i440fx ?
(I have a customer with a new epyc v4, asking me about this, and I had
no idea that they was a different limit between q35 && i440fx)
with i440fx (and 512 cores)
# qm start 105
kvm: Invalid SMP CPUs 512. The max CPUs supported by machine 'pc-
i440fx-8.1' is 255
with q35 (and 4096 cores)
# qm start 105
kvm: Invalid SMP CPUs 4096. The max CPUs supported by machine 'pc-q35-
8.1' is 1024
-------- Message initial --------
De: Fiona Ebner <f.ebner@proxmox.com>
À: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
"DERUMIER, Alexandre" <alexandre.derumier@groupe-cyllene.com>,
d.csapak@proxmox.com <d.csapak@proxmox.com>, aderumier@odiso.com
<aderumier@odiso.com>
Objet: Re: [pve-devel] [PATCH pve-manager] qemu: bump max cores to 256
by socket
Date: 15/01/2024 14:08:39
Am 15.01.24 um 13:43 schrieb DERUMIER, Alexandre:
>
>
> Maybe an improvement in qemu-server, could be to add additional check
> at vm start, (maybe a simple warn), depending of qemu version or
> setup.
> For example, 1024 cores only works with q35 && qemu 8.1,
> it could be interesting to give an clean hint mesage to user instead
> a qemu process error.
>
Is the QEMU error message understandable? If yes, I don't see much
value
in adding such a heuristic and warning ourselves. If no, we can either
improve the QEMU error message or do as you suggested.
next prev parent reply other threads:[~2024-01-16 14:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-12 20:08 Alexandre Derumier
2024-01-15 11:46 ` Dominik Csapak
2024-01-15 12:43 ` DERUMIER, Alexandre
2024-01-15 13:08 ` Fiona Ebner
2024-01-16 14:08 ` DERUMIER, Alexandre [this message]
2024-01-16 15:20 ` Fiona Ebner
2024-02-20 12:50 ` [pve-devel] applied: " Thomas Lamprecht
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=5fd038cc440c6dfd4e97961f8e098dae4c3f328a.camel@groupe-cyllene.com \
--to=alexandre.derumier@groupe-cyllene.com \
--cc=aderumier@odiso.com \
--cc=d.csapak@proxmox.com \
--cc=f.ebner@proxmox.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal