Date: Wed, 01 Dec 2021 16:12:44 -0700 From: John Doherty via freebsd-virtualization <freebsd-virtualization@freebsd.org> To: "Oleg Ginzburg" <olevole@olevole.ru> Cc: "Miroslav Lachman" <000.fbsd@quip.cz>, rgrimes@freebsd.org, jbo@insane.engineer, freebsd-virtualization@freebsd.org Subject: Re: bhyve vCPU limit Message-ID: <FF810706-07B8-4B2E-8286-749834D354F4@jld3.net> In-Reply-To: <CAMsb%2BmbY4ZbtFvBHd15naGT-BdXAVKg6BAOTpnBNg7hNcg2Czw@mail.gmail.com> References: <PigdsByvTXmOLg46mIkWprP1GQQPuxEiHn55uKNYuSBIzBFFe-CVGYdJ2FuzYSd5OebhMlSpRGMIisaN07yzjSSaWz8JQ7LeXDeINIZg_D8=@insane.engineer> <4E8A7FD3-B01E-4ADE-A290-360F3B04AC0F@jld3.net> <30e4454c-414a-833f-3829-586a450e7205@quip.cz> <CAMsb%2BmbY4ZbtFvBHd15naGT-BdXAVKg6BAOTpnBNg7hNcg2Czw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed 2021-12-01 11:13 AM MST -0700, <olevole@olevole.ru> wrote: > As far as I remember, it is not enough to simply change one parameter > in .h file: https://bhyvecon.org/bhyveconOttawa2019-Rodney.pdf I may be wrong but my understanding is that prior to the work described = in that presentation, some of the bhyve data structures were such that = vCPU counts above 21 would not be possible. That work resolved that but = the VM_MAXCPU value was left at 16. On my system, I'm sure that all I did was edit vmm.h, make buildworld, = and make installworld. I did some other stuff while sort of stumbling toward that eventual = solution, described here: <https://lists.freebsd.org/pipermail/freebsd-virtualization/2021-May/0095= 08.html> Once what I was doing wrong was pointed out, it seemed to me that after = editing that file, "make buildworld" and "make installworld" would be = the simplest way to do things, so that's what I did. It's been working = fine for six months or so.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?FF810706-07B8-4B2E-8286-749834D354F4>