Silent vCPU Overcommit: No Warning When %RDY Latency Exceeds Threshold

VMware Fusion exposes the CPU ready metric (%RDY) in performance charts and optionally in vmware.log when sched.stats.enable = TRUE is set. Under concurrent multi-VM workloads, %RDY rises once combined vCPU demand exceeds physical cores, yet Fusion emits no dedicated log entry or alert when this latency crosses a problematic threshold.

The hypervisor permits assigning more vCPUs than physical cores exist — for example, 8 vCPUs on a 6-core Mac — with default reservations and limits unset. This guarantees scheduling contention under load, but the absence of a "CPU ready threshold exceeded" message means administrators discover the issue only by manually inspecting performance charts or sampled log lines.

Apple Silicon introduces additional variance because Fusion uses the Virtualization Framework, altering scheduler dynamics. The product documentation does not define a %RDY warning threshold, nor does it indicate whether the missing alert is intentional or an oversight.

Is the lack of a %RDY threshold warning a deliberate design choice or an unresolved gap? What sustained %RDY value would justify a warning if one were implemented? Does the presence of Automatic Resource Allocation for memory suggest future vCPU overcommit management?