Re: guest kernel fails to start when cpuset is used

In reply to: Miroslav Lachman : "Re: guest kernel fails to start when cpuset is used"
Go to: [ bottom of page ] [ top of archives ] [ this month ]

From: Nikos Vassiliadis <nvass_at_gmx.com>
Date: Thu, 19 Mar 2026 16:53:29 UTC

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...