Changeset View
Changeset View
Standalone View
Standalone View
usr.sbin/bhyve/bhyve.8
Show First 20 Lines • Show All 194 Lines • ▼ Show 20 Lines | ||||||||||||
.It Fl l Ar lpcdev Ns Op Cm \&, Ns Ar conf | .It Fl l Ar lpcdev Ns Op Cm \&, Ns Ar conf | |||||||||||
Allow devices behind the LPC PCI-ISA bridge to be configured. | Allow devices behind the LPC PCI-ISA bridge to be configured. | |||||||||||
The only supported devices are the TTY-class devices | The only supported devices are the TTY-class devices | |||||||||||
.Cm com1 , com2 , com3 , | .Cm com1 , com2 , com3 , | |||||||||||
and | and | |||||||||||
.Cm com4 , | .Cm com4 , | |||||||||||
the boot ROM device | the boot ROM device | |||||||||||
.Cm bootrom , | .Cm bootrom , | |||||||||||
and the debug/test device | the | |||||||||||
.Cm fwcfg | ||||||||||||
markj: I think some more elaboration is needed. What is a "fwcfg", what are the valid values, why… | ||||||||||||
type and the debug/test device | ||||||||||||
.Cm pc-testdev . | .Cm pc-testdev . | |||||||||||
.Pp | .Pp | |||||||||||
The possible values for the | The possible values for the | |||||||||||
.Ar conf | .Ar conf | |||||||||||
argument are listed in the | argument are listed in the | |||||||||||
.Fl s | .Fl s | |||||||||||
flag description. | flag description. | |||||||||||
.It Xo | .It Xo | |||||||||||
▲ Show 20 Lines • Show All 128 Lines • ▼ Show 20 Lines | ||||||||||||
AHCI controller attached to a SATA hard drive. | AHCI controller attached to a SATA hard drive. | |||||||||||
.It Cm e1000 | .It Cm e1000 | |||||||||||
Intel e82545 network interface. | Intel e82545 network interface. | |||||||||||
.It Cm uart | .It Cm uart | |||||||||||
PCI 16550 serial device. | PCI 16550 serial device. | |||||||||||
.It Cm lpc | .It Cm lpc | |||||||||||
LPC PCI-ISA bridge with COM1, COM2, COM3, and COM4 16550 serial ports, | LPC PCI-ISA bridge with COM1, COM2, COM3, and COM4 16550 serial ports, | |||||||||||
a boot ROM, and, | a boot ROM, and, | |||||||||||
optionally, the debug/test device. | optionally, a fwcfg type and the debug/test device. | |||||||||||
The LPC bridge emulation can only be configured on bus 0. | The LPC bridge emulation can only be configured on bus 0. | |||||||||||
.It Cm fbuf | .It Cm fbuf | |||||||||||
Raw framebuffer device attached to VNC server. | Raw framebuffer device attached to VNC server. | |||||||||||
.It Cm xhci | .It Cm xhci | |||||||||||
eXtensible Host Controller Interface (xHCI) USB controller. | eXtensible Host Controller Interface (xHCI) USB controller. | |||||||||||
.It Cm nvme | .It Cm nvme | |||||||||||
NVM Express (NVMe) controller. | NVM Express (NVMe) controller. | |||||||||||
.It Cm hda | .It Cm hda | |||||||||||
▲ Show 20 Lines • Show All 156 Lines • ▼ Show 20 Lines | ||||||||||||
Map | Map | |||||||||||
.Ar romfile | .Ar romfile | |||||||||||
in the guest address space reserved for boot firmware. | in the guest address space reserved for boot firmware. | |||||||||||
If | If | |||||||||||
.Ar varfile | .Ar varfile | |||||||||||
is provided, that file is also mapped in the boot firmware guest | is provided, that file is also mapped in the boot firmware guest | |||||||||||
address space, and any modifications the guest makes will be saved | address space, and any modifications the guest makes will be saved | |||||||||||
to that file. | to that file. | |||||||||||
.El | ||||||||||||
.Pp | ||||||||||||
Fwcfg types: | ||||||||||||
.Bl -tag -width 10n | ||||||||||||
.It Ar fwcfg | ||||||||||||
The fwcfg interface is used to pass information such as the CPU count or ACPI tables to the guest firmware. | ||||||||||||
Done Inline Actions
markj: | ||||||||||||
Supported values are | ||||||||||||
Done Inline Actions
Same below. markj: Same below. | ||||||||||||
.Ql bhyve | ||||||||||||
and | ||||||||||||
.Ql qemu . | ||||||||||||
Done Inline Actions
markj: | ||||||||||||
Due to backward compatibility reasons, | ||||||||||||
.Ql bhyve | ||||||||||||
Done Inline Actions
markj: | ||||||||||||
is the default option. | ||||||||||||
Done Inline Actions
markj: | ||||||||||||
When | ||||||||||||
Done Inline Actions
markj: | ||||||||||||
.Ql bhyve | ||||||||||||
is used, bhyve's fwctl interface is used. | ||||||||||||
It currently reports only the CPU count to the guest firmware. | ||||||||||||
The | ||||||||||||
.Ql qemu | ||||||||||||
option uses QEMU's fwcfg interface. | ||||||||||||
Not Done Inline Actions
markj: | ||||||||||||
This interface is widely used and allows user-defined information to be passed to the guest. | ||||||||||||
Not Done Inline Actions
markj: | ||||||||||||
It is used for passing the CPU count, ACPI tables, a boot order and many other things to the guest. | ||||||||||||
Some operating systems such as Fedora CoreOS can be configured by qemu's fwcfg interface as well. | ||||||||||||
.El | .El | |||||||||||
.Pp | .Pp | |||||||||||
Pass-through device backends: | Pass-through device backends: | |||||||||||
.Sm off | .Sm off | |||||||||||
.Bl -bullet | .Bl -bullet | |||||||||||
.It | .It | |||||||||||
.Cm ppt Ar N Oo , Ar passthru-device-options Oc | .Cm ppt Ar N Oo , Ar passthru-device-options Oc | |||||||||||
.It | .It | |||||||||||
▲ Show 20 Lines • Show All 464 Lines • Show Last 20 Lines |
I think some more elaboration is needed. What is a "fwcfg", what are the valid values, why would someone choose one value over the other?