From nobody Wed Dec 1 16:17:56 2021 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 E1DD418B2C0E for ; Wed, 1 Dec 2021 16:18:48 +0000 (UTC) (envelope-from bsdlists@jld3.net) Received: from mail.jld3.net (mail.jld3.net [45.55.236.93]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4J445h5yKDz3q3R for ; Wed, 1 Dec 2021 16:18:48 +0000 (UTC) (envelope-from bsdlists@jld3.net) Received: from localhost (localhost [127.0.0.1]) by mail.jld3.net (Postfix) with ESMTP id 93F76415BF; Wed, 1 Dec 2021 09:18:42 -0700 (MST) X-Virus-Scanned: amavisd-new at jld3.net Received: from mail.jld3.net ([127.0.0.1]) by localhost (mail.jld3.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id y0J_wrm5ZPEV; Wed, 1 Dec 2021 09:18:41 -0700 (MST) Received: from [172.21.35.248] (c-24-9-144-115.hsd1.co.comcast.net [24.9.144.115]) (using TLSv1.2 with cipher AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: jld) by mail.jld3.net (Postfix) with ESMTPSA id 3F72540574; Wed, 1 Dec 2021 09:18:41 -0700 (MST) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.jld3.net 3F72540574 DKIM-Filter: OpenDKIM Filter v2.11.0 mail.jld3.net 3F72540574 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jld3.net; s=8d052f02dde2; t=1638375521; bh=e+hBCaI3vWTcYk32R+d8u4MAYCiy8wUoUNJspqlOLRs=; h=From:To:Subject:Date:Message-ID:MIME-Version:From; b=lUb1dFvKvCBt7OcxFY6JzVNhPF4FhgKLyl1Ej6E3BsjPKUUcKMG12AulfVM44LxOQ swR0e2gbnehphOJADFktm4UvLICVEktL1h213iXT+KxkOu+m/WVL4CPVqrzTt3knNx CuFCDLmmg+twr9/ZNCyCCLihWM7RcV75RFNCn504= To: jbo@insane.engineer Cc: freebsd-virtualization@freebsd.org Subject: Re: bhyve vCPU limit Date: Wed, 01 Dec 2021 09:17:56 -0700 X-Mailer: MailMate (1.13.2r5673) Message-ID: <4E8A7FD3-B01E-4ADE-A290-360F3B04AC0F@jld3.net> In-Reply-To: References: List-Id: Discussion List-Archive: https://lists.freebsd.org/archives/freebsd-virtualization List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-virtualization@freebsd.org X-BeenThere: freebsd-virtualization@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; format=flowed X-Rspamd-Queue-Id: 4J445h5yKDz3q3R X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] Reply-To: bsdlists@jld3.net From: John Doherty via freebsd-virtualization X-Original-From: John Doherty X-ThisMailContainsUnwantedMimeParts: N That limitation appears to still exist in FreeBSD 13.0-RELEASE: [root@grit] # freebsd-version -k ; grep 'VM_MAXCPU' /usr/src/sys/amd64/include/vmm.h 13.0-RELEASE #define VM_MAXCPU 16 /* maximum virtual cpus */ I ran into this in May 2021 and with some help from folks on this list was able to increase it. The simplest (if not minimalist) way to do that is: 1. edit /usr/src/sys/amd64/include/vmm.h to increase that value: I used 48 2. make buildworld 3. make installworld The increased value has been working fine for me since I did that. I run a couple of VMs with 24 vCPUs each and several others with smaller numbers all the time and have run others with as many as 48 temporarily. No problems that I have seen. I don't use cbsd so can't comment on that. On Wed 2021-12-01 04:24 AM MST -0700, wrote: > Hello folks, > > I'm using the sysutils/cbsd port for managing bhyve VMs on multiple > hosts. > CBSD does currently not allow to assign more than 16 vCPU cores to a > VM. > I've reached out to the CBSD author(s) to check up on this situation. > I was > referred to an E-Mail from this mailing list from 2014 at which point > this was > apparently a bhyve limitation. > > I'd like to understand whether this limitation is still present to > this date. Or > whether bhyve is able to assign more than 16 vCPU cores to a VM? > > Thank you for all your hard work & Best regards,