From nobody Mon Nov 24 05:18:43 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 4dFDdD5H7Qz6J4p9 for ; Mon, 24 Nov 2025 05:18:56 +0000 (UTC) (envelope-from jason@tubnor.net) Received: from mail.tubnor.net (mail.tubnor.net [103.236.162.16]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA512) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4dFDdC4PPlz3gXq for ; Mon, 24 Nov 2025 05:18:55 +0000 (UTC) (envelope-from jason@tubnor.net) Authentication-Results: mx1.freebsd.org; none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tubnor.net; s=20220915; t=1763961524; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=DF3q8hpU1/Jq2ShGt1w4MOckhMnUirh2PaHaLBgwtsg=; b=gIgdCwB8XFBStHYFqihB9+B25Dh11cNinfryszD5v4WZAHGToCd8lglnCOMr4tKa0nqtct BPAeFxtLJd6kp5sU6utK8aaAv8iBmIEoQWF9fQQvr1i1Ndv7842NzzgDioGzuoWszrJAXd M1ZBVWjr+EKrPGW+DV5wmZrKxsb+N4s= Received: from [IPV6:2403:5812:73e6:1:f72c:5c13:d2ae:844] ( [2403:5812:73e6:1:f72c:5c13:d2ae:844]) by mamel01.vic.tubnor.au (OpenSMTPD) with ESMTPSA id 3c2c178c (TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO); Mon, 24 Nov 2025 16:18:43 +1100 (AEDT) Message-ID: Date: Mon, 24 Nov 2025 16:18:43 +1100 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: pinning cores To: freebsd-virtualization@freebsd.org, void@f-m.fm References: Content-Language: en-US From: Jason Tubnor In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Rspamd-Queue-Id: 4dFDdC4PPlz3gXq On 23/11/25 22:15, void wrote: > Hi, > > Does anyone using bhyve, pin cores? > On a bhyve server with SHT *disabled* (dual Xeon, > 10 non-HT cores on each) I'd like to pin > 1 core from each cpu per vm for 4 VMs. > > What's the syntax using vmrun.sh? Or is it best > to directly use bhybe like bhyve -c 2 -m 16G -w -H etc etc Say if you want to pin virtual core 0 to physical core 3 and virtual core 1 to physical core 5 (2vCPU guest), you would add the following option: -p 0:3 -p 1:5 If you use vm-bhyve, you'd add the below to the guest's .conf file: bhyve_options="-p 0:3 -p 1:5" Cheers, Jason