RE: [edk2-devel] [PATCH 0/1] OvmfPkg/Bhyve: QemuFwCfg support

Hi Gerd,

> But I think I'd tend to keep the bhyve-specific behavior nevertheless,
> so you don't have to worry about qemu quirks.

Ok. I will leave it as is.

> Or go the qemu route and generate the acpi tables on the host instead.
> When you generate the acpi tables in the guest firmware you always have
> the problem that you need to pass all the virtual machine configuration
> information needed to generate the tables to the firmware.  The
> information needed changes over time when new features are added, which
> requires protocol updates, which in turn requires lockstep updates of
> hypervisor and firmware to deploy the new features ...

Personally, I would like to use plain OVMF without any bhyve specific patches
as firmware for bhyve. So, I want to go the qemu route but there's some more
work to do. I already took a look at how qemu creates ACPI tables but don't
understand it yet. Would be very grateful if you or someone else could help
me with that. If someone knows where to find more information about it,
it would also be helpful.

As first step, I'm going to implement FwCfg support without changing any
behaviour.


Thanks,
Corvin


Beckhoff Automation GmbH & Co. KG | Managing Director: Dipl. Phys. Hans Beckhoff
Registered office: Verl, Germany | Register court: Guetersloh HRA 7075