From: Bagas Sanjaya <bagasdotme@gmail.com>
To: "Toralf Förster" <toralf.foerster@gmx.de>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Linux KVM" <kvm@vger.kernel.org>
Cc: Sean Christopherson <seanjc@google.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>
Subject: Re: kconfig does not accept a lower value for KVM_MAX_NR_VCPUS
Date: Mon, 20 Jan 2025 06:55:38 +0700 [thread overview]
Message-ID: <Z42Q-sbPMA9zZMIC@archie.me> (raw)
In-Reply-To: <03a04e86-c629-44df-9022-05c42b4c736f@gmx.de>
[-- Attachment #1: Type: text/plain, Size: 929 bytes --]
On Sun, Jan 19, 2025 at 12:04:04PM +0100, Toralf Förster wrote:
> I was wondering why I cannot put a lower value here during make oldconfig:
>
>
> Maximum number of vCPUs per KVM guest (KVM_MAX_NR_VCPUS) [1024] (NEW) 16
> Maximum number of vCPUs per KVM guest (KVM_MAX_NR_VCPUS) [1024] (NEW) 8
> Maximum number of vCPUs per KVM guest (KVM_MAX_NR_VCPUS) [1024] (NEW)
>
Hi Toralf,
From arch/x86/kvm/Kconfig:
>config KVM_MAX_NR_VCPUS
> int "Maximum number of vCPUs per KVM guest"
> depends on KVM
> range 1024 4096
> default 4096 if MAXSMP
> default 1024
> help
> Set the maximum number of vCPUs per KVM guest. Larger values will increase
> the memory footprint of each KVM guest, regardless of how many vCPUs are
> created for a given VM.
I don't know your use case, but you can safely choose the default (1024).
Thanks.
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next parent reply other threads:[~2025-01-19 23:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <03a04e86-c629-44df-9022-05c42b4c736f@gmx.de>
2025-01-19 23:55 ` Bagas Sanjaya [this message]
2025-01-21 15:55 ` kconfig does not accept a lower value for KVM_MAX_NR_VCPUS Sean Christopherson
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=Z42Q-sbPMA9zZMIC@archie.me \
--to=bagasdotme@gmail.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--cc=tglx@linutronix.de \
--cc=toralf.foerster@gmx.de \
--cc=x86@kernel.org \
/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