[Bug 271134] bhyve(8), bhyvectl(8), bhyve(4), bhyve_config(5): manual pages cleanup
- In reply to: bugzilla-noreply_a_freebsd.org: "[Bug 271134] bhyve(8) manual page cleanup"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Thu, 21 Aug 2025 22:06:59 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271134
Marcin Cieślak <saper@saper.info> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |saper@saper.info
--- Comment #11 from Marcin Cieślak <saper@saper.info> ---
There is something strange with Fwcfg types.
I think this should be a separate section block...
Boot ROM device backends
• romfile[,varfile]
Map romfile in the guest address space reserved for boot firmware.
If varfile is provided, that file is also mapped in the boot firmware
guest address space, and any modifications the guest makes will be saved
to that file.
Fwcfg types:
fwcfg The fwcfg interface is used to pass information such as the
CPU count or ACPI tables to the guest firmware. Supported
values are ‘bhyve’ and ‘qemu’. Due to backward compatibility
reasons, ‘bhyve’ is the default option. When ‘bhyve’ is
used, bhyve's fwctl interface is used. It currently reports
only the CPU count to the guest firmware. The ‘qemu’ option
uses QEMU's fwcfg interface. This interface is widely used
and allows user-defined information to be passed to the
guest. 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.
--
You are receiving this mail because:
You are on the CC list for the bug.