mirror of
https://chromium.googlesource.com/crosvm/crosvm
synced 2024-11-25 05:03:05 +00:00
c1c27448a3
Currently, crosvm running with --bios <OVMF executable> will only boot from available block devices if started with a clean BIOS pflash. If crosvm is not run with a clean pflash, OVMF will get confused and refuse to boot. The reason for this behavior is that OVMF expects a "bootorder" file to be present in the fw_cfg device to calibrate its boot order. This CL allows fw_cfg to specify bootorder, solving the inconsistent booting behavior. Boot order is specified from the command line with the bootindex=NUM argument.The bootindex argument is available for block devices specified with the --block flag. Note that the --fw-cfg flag must be specified w/ at least on file (can be an empty file with a random name) on the command line for fw_cfg to actually be made available to the guest. Also, further investigation is needed if we wish to boot from pmem devices in the future. See crosvm run -h for more information about the bootindex argument. BUG=b:243051819 Change-Id: Ieae1e2cacc14c018832b228db898884281c38a96 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/4755415 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Commit-Queue: Sebastian Hereu <sebastianhereu@google.com> |
||
|---|---|---|
| .. | ||
| src | ||
| tests | ||
| Cargo.toml | ||