From nobody Sat Feb 15 16:19:25 2025 X-Original-To: freebsd-virtualization@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4YwDdZ002cz5nlWG for ; Sat, 15 Feb 2025 16:19:29 +0000 (UTC) (envelope-from freebsdlouisville@gmail.com) Received: from mail-qt1-x834.google.com (mail-qt1-x834.google.com [IPv6:2607:f8b0:4864:20::834]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4YwDdY1WFSz3Y8Q for ; Sat, 15 Feb 2025 16:19:29 +0000 (UTC) (envelope-from freebsdlouisville@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20230601 header.b=RxtrmGkX; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of freebsdlouisville@gmail.com designates 2607:f8b0:4864:20::834 as permitted sender) smtp.mailfrom=freebsdlouisville@gmail.com Received: by mail-qt1-x834.google.com with SMTP id d75a77b69052e-46fa7678ef3so32838701cf.1 for ; Sat, 15 Feb 2025 08:19:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1739636368; x=1740241168; darn=freebsd.org; h=content-transfer-encoding:in-reply-to:content-language:references :to:subject:user-agent:mime-version:date:message-id:from:from:to:cc :subject:date:message-id:reply-to; bh=0NGrZ0haWmcmhg69JW2CcdOfETfgMIkqqiqo+F9TC2E=; b=RxtrmGkXgSTSN0QyJZoThhtnGHeuBG8/FYocUEFAHJS6z/ouhOeEbu6g/5gpF2bvbR +bKj7DTOnkvgl0jX+v1Uon3codzyWQmCKgTQpk44EqWBLpOUjqZzaCpWzDolVZeHQgPD diYqoOu2y72SyYg4astvCt6oxBS+DoiWDeNl7ItDeZnbGxaLW7+cbdH/MRBGR2Q9Qyiu D06t7gUcGSJq+BdFexMlMbkB7hxqtbqBgdHLA8PCU0I5C5uevGH7lMkD1zpKoJb0OUwz JlUkiaz/mQHL2HZgPuvFQLKQLyIGI68OUlGb+sTpklaRW5G+U7NGiY2MxSeE4oMGJm4N S4Jg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1739636368; x=1740241168; h=content-transfer-encoding:in-reply-to:content-language:references :to:subject:user-agent:mime-version:date:message-id:from :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=0NGrZ0haWmcmhg69JW2CcdOfETfgMIkqqiqo+F9TC2E=; b=HqpjyVeAiysQ5il8rw7ildKDWJjkx0I+dBvg/KaODd9N2WPswApKdy2aakuZIVdbzW A7svPywfdAK25TO167BPR3Ci91JNUE6ZET7tTWVsolhIFWKG8LuS2oOmKd/7pIc96f/2 AyK90egAPQrN8g8HTf5ujVkNIaTWvC3hFXMmsiIcdVb0p95fycib8xczf+7ABS1FZa/1 AvjfTqffWS3cXU/FiKiUghPy6ZFqOmhAWVCUAfId74KrNlj1NwoX/322GohHWskYEtx3 rSxqNC/d5INqQh1oW2bLQeYsd/ydJBMZVcVMkzq63SKOHmiC3BFpBwb+L1ZTX524G3BE fT+A== X-Forwarded-Encrypted: i=1; AJvYcCU50Px1xOpm2JLish88MhDUwoXskojPiXw3wsaneCTu9LdjiydYjZbR9Zaki73MGQS7oNvAGleB7dIc/+DYTMo+IPcQihlG@freebsd.org X-Gm-Message-State: AOJu0Yxa10Y0TkecwPzWCVjQesgw9lhGH3I5nEVXvLpOBVLgesE5r3ts OmL2XSglIdCp3ctWA577H2NQ91BZVhWe1oX/L0frPcbaL/QSn7q5jI1RpW7X X-Gm-Gg: ASbGncvwEIgYf93Ie7Dtz4KYFT99MjrM/aCxghyy8/YqCfkl5v4hJVbOEYCHK8nkOWE zJ92novysdtaZOkKFwYRkZSWhFdOIWMUUfMniHVMhtx6+B7uJzUNVbKt21+Rg3gR3vJqP5hIN24 VXD+Lsgd2eucPoah/UNbt4kx37InDhR+SXroP4qOI0c6a7D9cXOvhTxX+EZqJlT4P+8ThzMrdZy 0IZW8doow4ov0wqrxKjejzFoILkT6qWpGE+ZA+tUu1gw3lqIz2U7UZyNQT0LpZUp1ljgaVTdFES WJO8RrPEndqUD8GAgH9uKCcXlLIdBKCOEjVJErfc4IGrT8RiWsR/A+KDst5LXiFtClEGFBWNBw= = X-Google-Smtp-Source: AGHT+IFI05OatYjlC8M8hNw0WVOrZ8jF1sYVqJWJxCT43APVyZmwtolKSvQ+dE7zrSWRYw80Bu6Ljg== X-Received: by 2002:a05:622a:87:b0:471:9f06:aebf with SMTP id d75a77b69052e-471dbd73820mr40301241cf.30.1739636368172; Sat, 15 Feb 2025 08:19:28 -0800 (PST) Received: from ?IPV6:2600:1015:a030:7620:5a80:a579:2c9e:9ca? ([2600:1015:a030:7620:5a80:a579:2c9e:9ca]) by smtp.gmail.com with ESMTPSA id d75a77b69052e-471c2b047d4sm28718691cf.69.2025.02.15.08.19.26 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sat, 15 Feb 2025 08:19:27 -0800 (PST) From: FreeBSD Louisville X-Google-Original-From: FreeBSD Louisville Message-ID: Date: Sat, 15 Feb 2025 11:19:25 -0500 List-Id: Discussion List-Archive: https://lists.freebsd.org/archives/freebsd-virtualization List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-virtualization@freebsd.org Sender: owner-freebsd-virtualization@FreeBSD.org MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Can I allocate some CPUs to the bhyve host? To: Paul Procacci , freebsd-virtualization@freebsd.org References: <978106d8-1ad0-4227-a387-aa4bece0b156@Gmail.com> Content-Language: en-US In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Spamd-Result: default: False [-1.01 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_SPAM_SHORT(0.99)[0.994]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20230601]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; ARC_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; FREEMAIL_TO(0.00)[gmail.com,freebsd.org]; FREEMAIL_FROM(0.00)[gmail.com]; TO_DN_SOME(0.00)[]; FROM_HAS_DN(0.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; FROM_EQ_ENVFROM(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; PREVIOUSLY_DELIVERED(0.00)[freebsd-virtualization@freebsd.org]; MID_RHS_MATCH_FROM(0.00)[]; MLMMJ_DEST(0.00)[freebsd-virtualization@freebsd.org]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::834:from] X-Rspamd-Queue-Id: 4YwDdY1WFSz3Y8Q X-Spamd-Bar: - Thanks for the quick response and your time. I may have confused the issue. I want to dedicate a certain number of CPUs to the host, thereby assuring CPUs are not over-provisioned to guests. On 2/15/25 10:54, Paul Procacci wrote: > On Sat, Feb 15, 2025 at 10:34 AM FreeBSD Louisville > wrote: >> It appears to me that a user could over-provision CPUs to guests, >> causing massive slowdown of the system. Can I specify CPUs to be >> "locked" to the host? If I have 16 processors available, could I start >> guests that want 32 CPUs? >> >> > The maximum number of vcpus is limited to the number of cpus. > You can "lock" cpus to a guest by way of cpuset -- which I don't > suggest doing unless you know what you are doing. > > ~Paul >