Actions
Bug #14681
open
use kstats for remaining bhyve data
Status:
New
Priority:
Normal
Assignee:
-
Category:
bhyve
Start date:
Due date:
% Done:
0%
Estimated time:
Difficulty:
Medium
Tags:
Gerrit CR:
External Bug:
Description
Bhyve maintains various metrics about internal instance state, which is exposed by a custom ioctl interface. Presently, bhyvectl is the only consumer of this data. It would be nice to convert those metrics so they are exposed via kstats, rather than the bespoke framework and ioctl interface in the kernel vmm.
Related issues
Updated by Patrick Mooney 3 months ago
- Related to Bug #15699: bhyve should lift VM_MAXCPU limit added
Actions