all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Fiona Ebner <f.ebner@proxmox.com>
To: "DERUMIER, Alexandre" <alexandre.derumier@groupe-cyllene.com>,
	"pve-devel@lists.proxmox.com" <pve-devel@lists.proxmox.com>,
	"d.csapak@proxmox.com" <d.csapak@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 16:20:24 +0100	[thread overview]
Message-ID: <a68823d3-e51b-4689-940f-b9a87d9bd5a0@proxmox.com> (raw)
In-Reply-To: <5fd038cc440c6dfd4e97961f8e098dae4c3f328a.camel@groupe-cyllene.com>

Am 16.01.24 um 15:08 schrieb DERUMIER, Alexandre:
> 
>>> 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)
> 

Sure, we can mention that the limit depends on the machine version in
the CPU section and/or machine version section. Note it's not only type,
but version, e.g. q35-8.0 has 288 as a limit:
https://github.com/qemu/qemu/blob/master/hw/i386/pc_q35.c#L419




  reply	other threads:[~2024-01-16 15:20 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
2024-01-16 15:20         ` Fiona Ebner [this message]
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=a68823d3-e51b-4689-940f-b9a87d9bd5a0@proxmox.com \
    --to=f.ebner@proxmox.com \
    --cc=aderumier@odiso.com \
    --cc=alexandre.derumier@groupe-cyllene.com \
    --cc=d.csapak@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