HOSTCTL(8) - System Manager’s Manual # HOSTCTL(8) - System Manager’s Manual
NAME # hostctl - display or modify contents of the host’s key-value store
SYNOPSIS # hostctl [-qt] [-f device] [-i input] [-o output] key [value]
DESCRIPTION # The hostctl program provides a generic interface for accessing key-value stores on the system’s host. It is primarily used for an abstracted way to exchange information with hypervisors that are supported by the pvbus(4) subsystem.
...
HOSTCTL(8) - System Manager’s Manual # HOSTCTL(8) - System Manager’s Manual
NAME # hostctl - display or modify contents of the host’s key-value store
SYNOPSIS # hostctl [-qt] [-f device] [-i input] [-o output] key [value]
DESCRIPTION # The hostctl program provides a generic interface for accessing key-value stores on the system’s host. It is primarily used for an abstracted way to exchange information with hypervisors that are supported by the pvbus(4) subsystem.
...
HYPERV(4) - Device Drivers Manual # HYPERV(4) - Device Drivers Manual
NAME # hyperv - Hyper-V guest nexus device
SYNOPSIS # hyperv0 at pvbus?
DESCRIPTION # hyperv driver performs Synthetic Interrupt Controller initialization, sets up hypercalls, and provides access to VMBus services required by paravirtualized devices such as disk and network interfaces.
An access is also provided to the Key-Value Pair exchange interface via pvbus(4). All keys are associated to one of several key pools: Auto, Guest, External or Guest/Parameters.
...
PVBUS(4) - Device Drivers Manual # PVBUS(4) - Device Drivers Manual
NAME # pvbus - paravirtual device tree root
SYNOPSIS # pvbus0 at mainbus0
#include <sys/types.h>
#include <sys/ioctl.h>
#include <dev/pv/pvvar.h>
DESCRIPTION # pvbus is used on virtual machines that are running on hypervisors. It provides a pseudo-bus for all paravirtual devices that do not attach to a well-known bus like pci(4). The pvbus driver is responsible for detecting the hypervisor interface, checking the capabilities, attaching the paravirtual devices, and providing access to supported information stores.
...
PVCLOCK(4) - Device Drivers Manual # PVCLOCK(4) - Device Drivers Manual
NAME # pvclock - paravirtual clock driver
SYNOPSIS # pvclock* at pvbus?
DESCRIPTION # The pvclock driver supports the paravirtual clock that is available in KVM and other hypervisors. pvclock uses a shared page between the host and the hypervisor to synchronize the TSC clock in an efficient way.
SEE ALSO # pvbus(4)
HISTORY # The pvclock driver first appeared in OpenBSD 6.
...
VMMCI(4) - Device Drivers Manual # VMMCI(4) - Device Drivers Manual
NAME # vmmci - VMM control interface
SYNOPSIS # vmmci* at virtio?
DESCRIPTION # The vmmci driver provides a control interface for virtual machines running inside OpenBSD vmm(4) (virtual machine monitor) hosts.
The driver handles shutdown and reboot requests from the vmm(4) host by signalling init(8) with SIGUSR2 and SIGINT respectively.
SEE ALSO # pvbus(4), vmm(4), init(8), vmd(8)
...
VMT(4) - Device Drivers Manual # VMT(4) - Device Drivers Manual
NAME # vmt - VMware Tools driver
SYNOPSIS # vmt0 at pvbus0
DESCRIPTION # The vmt driver is a kernel level implementation of VMware Tools. VMware Tools are intended to provide better support for operating systems running inside virtual machines.
vmt handles shutdown and reboot requests from the host by signalling init(8) with SIGUSR2 and SIGINT respectively. vmt will log notifications that the guest has been suspended or resumed by the host.
...
XEN(4) - Device Drivers Manual # XEN(4) - Device Drivers Manual
NAME # xen - Xen domU nexus device
SYNOPSIS # xen0 at pvbus?
DESCRIPTION # xen driver performs HVM domU guest initialization, provides abstraction for virtual Xen interrupts, access to the XenStore configuration storage as well as a device probing facility for paravirtualized devices such as disk and network interfaces.
When running under XenServer, to let the host know that the guest has finished initializing and to allow graceful shutdown, set the following XenStore properties with hostctl(8) in rc.
...