You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems to depend only on Boot System Or From Connected Disk, which uses some SEABIOS variables.
This seems to be a good first candidate for enabling Dasharo (coreboot+SeaBIOS) on QEMU Q35.
There are following issues to achieve correct results:
Support for QEMU Q35 and OS installation should be enabled
The current implementation of qemu-run.sh assumes either firmware (seabios|uefi), OS (OS testing), or OS_install (OS installation). Firmware has more minor memory requirements than OS.
Support for running qemu-run.sh on remote target
I'm also in a VM, so various accelerations would not work. For my setup to make things work, I need to start the emulator on a remote bare metal machine or as a separate VM in Qubes OS/xcp-ng, which could make things even more scalable.
Starting in Qubes has the problem of compromising system security (telnet port, etc.), so there are better ideas than this.
Starting on xcp-ng, we may have issues exposing the resources we currently use (BIOS file, QEMU monitor, telnet connection), but this is worth discussing with the CP community.
Bare metal is most straightforward for now.
The text was updated successfully, but these errors were encountered:
pietrushnic
changed the title
DMI00[1-4] - seems to depend only on Boot System Or From Connected Disk, which uses some SEABIOS variables
Enablink DMI00[1-4] for Dasharo (coreboot+SeaBIOS)
Nov 26, 2024
It seems to depend only on
Boot System Or From Connected Disk
, which uses someSEABIOS
variables.This seems to be a good first candidate for enabling Dasharo (coreboot+SeaBIOS) on QEMU Q35.
There are following issues to achieve correct results:
The current implementation of
qemu-run.sh
assumes either firmware (seabios|uefi), OS (OS testing), or OS_install (OS installation). Firmware has more minor memory requirements than OS.qemu-run.sh
on remote targetStarting on xcp-ng, we may have issues exposing the resources we currently use (BIOS file, QEMU monitor, telnet connection), but this is worth discussing with the CP community.
The text was updated successfully, but these errors were encountered: