Date: Thu, 19 Mar 2026 18:53:29 +0200 From: Nikos Vassiliadis <nvass@gmx.com> To: Miroslav Lachman <000.fbsd@quip.cz>, freebsd-current@FreeBSD.org Subject: Re: guest kernel fails to start when cpuset is used Message-ID: <1d1cc837-786c-40d4-8420-788c33b992a6@gmx.com> In-Reply-To: <05fbcbb9-be80-4ea4-818c-1e343e1f9305@quip.cz> References: <882fe6bb-3870-4ce7-bd5a-7f50a9ae5774@gmx.com> <05fbcbb9-be80-4ea4-818c-1e343e1f9305@quip.cz>
index | next in thread | previous in thread | raw e-mail
On 3/19/26 13:21, Miroslav Lachman wrote: > On 19/03/2026 11:39, Nikos Vassiliadis wrote: >> Hi, >> >> I was trying to limit a 12-core VM with cpuset. So I limited it to 0-5 >> cores and the kernel seems to fail to start. > > [..] > >> ACPI APIC Table: <BHYVEÂ BVAPIC > >> FreeBSD/SMP: Multiprocessor System Detected: 12 CPUs >> FreeBSD/SMP: 12 package(s) x 1 core(s) >> random: unblocking device. >> ioapic0 <Version 1.1> irqs 0-31 >> Launching APs: 2 8 6 11 10 9 3 4 7 5 1 >> >> And it stays there spinning. >> >> Any ideas? > > I don't think this is a good idea. Why not use -c a -p options for bhyve? > -c <num_of_cores> > -p vcpu:hostcpu Pin guest's virtual CPU vcpu to hostcpu I already am. And while I do not know whether is a good or bad idea, I was kind of surprised that it crashed...home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1d1cc837-786c-40d4-8420-788c33b992a6>