qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Zay <peterzay1@gmail.com>
To: Rajesh A <rajesh.a@tatacommunications.com>
Cc: "qemu-discuss@nongnu.org" <qemu-discuss@nongnu.org>,
	 "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	"Ramya R (GIMEC)" <ramya.r@tatacommunications.com>,
	 "V G ASHWINI ." <Ashwini.VG@contractor.tatacommunications.com>
Subject: Re: QEMU cpu socket allocation
Date: Tue, 17 May 2022 16:03:04 -0400	[thread overview]
Message-ID: <CAMdoaaNDWF87_h+rucDjwDpCvvhH5EZR+NoeNT=4+rFCGX1GXg@mail.gmail.com> (raw)
In-Reply-To: <KL1PR0401MB4793897A84C6EA0959F0645EEECE9@KL1PR0401MB4793.apcprd04.prod.outlook.com>


[-- Attachment #1.1: Type: text/plain, Size: 1040 bytes --]

Hi Rajesh,

Would the more intuitive CPU setting of (Sockets,Cores,Threads) = (1,16,1)
be ok?

Thanks.


On Tue, May 17, 2022 at 10:03 AM Rajesh A <rajesh.a@tatacommunications.com>
wrote:

> Hi QEMU dev
>
>
>
> Virt Manager is able to configure a QEMU VM with more CPU sockets than the
> physical host has.
>
> For example, in the below VM, when I request 16 vCPU cores,  by default it
> takes as 16 Sockets with 1 core each. The host itself has only 2 Sockets.
>
>    1. How does QEMU allow this and how the VM works?
>    2. What is the recommended configuration of Sockets/Cores/Threads for
>    best VM performance of a 16 core VM running on a 2 sockets host ?
>
>
>
>
>
> regards,
>
>
>
> *Rajesh A*
> Engineering Media Movement
> Media Services
>
>
>
> Direct +91 44 66674575   |  Mobile +91 9043011101   |  IP 564575
> rajesh.a@tatacommunications.com
>
>
> <http://tatacommunications.com/>
>
> www.tatacommunications.com
>
> <https://twitter.com/#!/tata_comm>
>
>  @tata_comm <https://twitter.com/#!/tata_comm>
>
>
>
>
>


-- 
Peter

[-- Attachment #1.2: Type: text/html, Size: 5948 bytes --]

[-- Attachment #2: image002.jpg --]
[-- Type: image/jpeg, Size: 2710 bytes --]

[-- Attachment #3: image003.jpg --]
[-- Type: image/jpeg, Size: 691 bytes --]

[-- Attachment #4: image004.png --]
[-- Type: image/png, Size: 76850 bytes --]

  reply	other threads:[~2022-05-17 20:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-17 10:50 QEMU cpu socket allocation Rajesh A
2022-05-17 20:03 ` Peter Zay [this message]
2022-05-18  6:23   ` Rajesh A
2022-05-18 14:09     ` Peter Zay
2022-05-18  8:33 ` Daniel P. Berrangé

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='CAMdoaaNDWF87_h+rucDjwDpCvvhH5EZR+NoeNT=4+rFCGX1GXg@mail.gmail.com' \
    --to=peterzay1@gmail.com \
    --cc=Ashwini.VG@contractor.tatacommunications.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-discuss@nongnu.org \
    --cc=rajesh.a@tatacommunications.com \
    --cc=ramya.r@tatacommunications.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;
as well as URLs for NNTP newsgroup(s).