Guests and GPU Dashboard Cards
Read virtual-machine, jail, application, and GPU statistics on the FreeCORE 15.1 dashboard.
FreeCORE 15.1 adds a Guests card to the dashboard and GPU cards for explicitly configured graphics drivers. These cards show current host observations. They do not start guests, install drivers, or prove that an application's service is healthy.
Guests
The Guests card groups virtual machines, running jails, and running Applications separately. Applications use their configured names rather than their container identifiers. Stopped VM definitions remain in the VM list; the jail and application counts come from running processes, so they are not totals of everything installed.
| Field | Meaning |
|---|---|
| Guests | Number of VM definitions and observed running jails and applications. |
| CPU | Combined guest CPU use as a percentage of the host's total logical CPU capacity. It is not a percentage of one guest's assigned vCPUs. |
| Memory | Approximate resident process memory attributed to the displayed guest families. |
| VM memory | Observed resident memory followed by configured memory, in GiB. A stopped VM shows a dash for observed memory. |
| Jail or application memory | Sum of resident memory reported by that guest's processes, marked as approximate. |
| Services | A compact breakdown of VM and jail memory and the remaining base-system estimate. RC1 omits Applications memory from this footer even though the aggregate Memory figure includes it. These are estimates, not separate allocations to add to the host memory total. |
CPU requires consecutive samples; Gathering data can appear initially. The card requests updates every five seconds while it is active. Guest identity information is cached, so a newly started or stopped guest can take longer to appear correctly.
Resident-memory sums can count memory shared by processes more than once. Use them to understand which guests consume resources, rather than as an exact accounting of physical memory.
Running VMs appear before stopped VMs. Within each family, rows are ordered by CPU use, then memory and name. The compact list shows up to five VMs and shares the remaining space between jails and applications. + more opens the corresponding management screen. Clicking a guest row also opens its family's screen.
No VMs, jails or applications is an empty sample. Guest statistics unavailable means the sample could not be obtained, rather than that no guests exist. Open Virtual Machines, Jails, or Applications to inspect the relevant definitions and service state.
When GPU Cards Appear
A GPU card requires an enabled RC tunable named kld_list containing a
recognized graphics-driver module. Dashboard discovery recognizes drm,
drm2, i915kms, amdgpu, radeonkms, nvidia, nvidia-modeset, and
nvidia-drm. Hardware detection alone does not enable the cards.
Use the driver appropriate to the installed hardware and the FreeCORE
release. An entry in this list is a dashboard discovery condition, not a
promise that the module supports every device. Review existing tunables
under System > Tunables; do not replace other modules in kld_list
merely to display a card.
The dashboard creates one card for each eligible detected GPU after this condition is met. Devices reported as no-driver are omitted. If there is no suitable inventory, no GPU card is added. A system without a GPU can still display the rest of the dashboard normally.
Read GPU Statistics
The card identifies the device, its PCI address, driver, and device nodes. It displays utilization, encoder/decoder activity, VRAM, and temperature only when those values are available from the driver.
NVIDIA telemetry uses nvidia-smi. AMD telemetry uses the AMDGPU interface
and an accessible DRM device node. Intel and other detected devices can
provide identity and process-consumer information without utilization
counters. Missing counters are not displayed as zero usage; the card can
show Driver reports no utilization counters.
| State | Meaning |
|---|---|
| active | A consumer is observed, or reported utilization is above zero. |
| idle | A driver or usable device node is present, with no observed consumer or positive utilization. |
| passthrough | The device is assigned to a VM or detached for PCI passthrough. Host utilization counters are not collected. |
Used by lists observed host processes, jails, or VMs, with process counts and GPU memory where available. The card shows at most four consumer rows and indicates additional consumers with + more. A consumer being listed does not establish how much GPU processing it is doing.
For passthrough, the card shows the VM association when known and the PCI selector. Read utilization from within the guest; the card does not fetch guest telemetry. Selecting the VM association opens Virtual Machines.