As @mato has submitted a pull request with abstractions that allow for generalization of the ukvm monitor towards other hypervisor APIs such as Hypervisor.Framework on Mac OS X, libvmmapi(bhyve) on FreeBSD and others, it would make sense to change the name of the monitor to something more generic to prevent confusion on non-KVM hypervisors. A possible name might be umon or ukmon, however, as @mato has pointed out, renaming ukvm has an impact on downstreams such as MirageOS.
As @mato has submitted a pull request with abstractions that allow for generalization of the ukvm monitor towards other hypervisor APIs such as Hypervisor.Framework on Mac OS X, libvmmapi(bhyve) on FreeBSD and others, it would make sense to change the name of the monitor to something more generic to prevent confusion on non-KVM hypervisors. A possible name might be
umonorukmon, however, as @mato has pointed out, renaming ukvm has an impact on downstreams such as MirageOS.