Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for Fwcfg type configuration of bootroom as now supported by bhyve. #575

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

iAlexanderMoon
Copy link

Bhyve added support for QEMU Firmware Configuration (fw_cfg) Device.

These changes enable configuring the vm to use qemu firmware instead of default fwctl.

Added a template for flatcar linux that uses the new configuration to pass "ignition" file for vm configuration through the firmware.

Update man page.

Added support for configuring fwcfg type in the bootloader line now that bhyve supports using QEMU Firmware Configuration Device as well as bhyve's  fwctl interface.
Add template for Flatcar Container Linux with commented out grub for ISO installation or configured for uefi with loader configured with QEMU Firmware Configuration Device and passing an ignition file for which is used on first run.
@thebiss
Copy link

thebiss commented Jan 11, 2025

This is excellent! I just tested it on FreeBSD 14, and was able to boot the latest Fedora coreos image and configure with an ignition file using this method. Previously, coreos-install had to be used to customize and maintain one image per vm.

One recommendation / request: In the man page change, emphasize that the -A option to generate ACPI tables must be included, as shown in the flatcar.conf example. With out it, I found coreos doesn't pick up the fw_cfg parameters, and ignition doesn't work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants