Actions
Bug #15699
open
bhyve should lift VM_MAXCPU limit
Status:
New
Priority:
Normal
Assignee:
-
Category:
bhyve
Start date:
Due date:
% Done:
0%
Estimated time:
Difficulty:
Medium
Tags:
Gerrit CR:
External Bug:
Description
Bhyve currently uses a fixed value of 32 for VM_MAXCPU. Upstream (FreeBSD) has since moved to dynamic allocation of vCPUs when it comes to the kernel vmm, eliminating the use of VM_MAXCPU for resource sizing there. We should do something similar, allowing userspace to specify a maxcpu limit on a per-VM basis, when creating said instances. It would probably make sense to clamp the max possible vCPUs per instance to the number of CPUs available in the system.
If maxcpus is to be a parameter specified at VM create time (probably the most simple approach), then it would make sense for this work to build off of #15124 .
Related issues
Updated by Patrick Mooney 10 days ago
- Related to Bug #15124: bhyve create should be nvlist driven added
Actions