mirror of
https://chromium.googlesource.com/crosvm/crosvm
synced 2024-11-25 05:03:05 +00:00
No description
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> |
||
|---|---|---|
| .cargo | ||
| .config | ||
| .devcontainer | ||
| .github | ||
| .vscode | ||
| aarch64 | ||
| acpi_tables | ||
| arch | ||
| argh_helpers | ||
| audio_streams_conformance_test | ||
| audio_util | ||
| base | ||
| bit_field | ||
| broker_ipc | ||
| common | ||
| cros_async | ||
| cros_fdt | ||
| cros_tracing | ||
| cros_tracing_types | ||
| crosvm_cli | ||
| crosvm_control | ||
| crosvm_plugin | ||
| devices | ||
| disk | ||
| docs/book | ||
| e2e_tests | ||
| fuse | ||
| fuzz | ||
| gpu_display | ||
| hypervisor | ||
| infra | ||
| io_uring | ||
| jail | ||
| kernel_cmdline | ||
| kernel_loader | ||
| kvm | ||
| kvm_sys | ||
| libcras_stub | ||
| linux_input_sys | ||
| logo | ||
| media | ||
| metrics | ||
| net_sys | ||
| net_util | ||
| perfetto | ||
| power_monitor | ||
| prebuilts | ||
| proto_build_tools | ||
| protos | ||
| qcow_utils | ||
| resources | ||
| riscv64 | ||
| rutabaga_gfx | ||
| sandbox | ||
| serde_keyvalue | ||
| src | ||
| swap | ||
| system_api | ||
| tests | ||
| third_party | ||
| tools | ||
| tpm2 | ||
| tpm2-sys | ||
| tube_transporter | ||
| usb_sys | ||
| usb_util | ||
| vendor | ||
| vfio_sys | ||
| vhost | ||
| virtio_sys | ||
| vm_control | ||
| vm_memory | ||
| win_audio | ||
| win_util | ||
| x86_64 | ||
| .dockerignore | ||
| .envrc | ||
| .gitignore | ||
| .gitmodules | ||
| .rustfmt.toml | ||
| ARCHITECTURE.md | ||
| Cargo.lock | ||
| Cargo.toml | ||
| CONTRIBUTING.md | ||
| DIR_METADATA | ||
| LICENSE | ||
| mypy.ini | ||
| OWNERS | ||
| OWNERS_COUNCIL | ||
| PRESUBMIT.cfg | ||
| pyproject.toml | ||
| README.chromeos.md | ||
| README.md | ||
| rust-toolchain | ||
crosvm - The ChromeOS Virtual Machine Monitor
crosvm is a virtual machine monitor (VMM) based on Linux’s KVM hypervisor, with a focus on simplicity, security, and speed. crosvm is intended to run Linux guests, originally as a security boundary for running native applications on the ChromeOS platform. Compared to QEMU, crosvm doesn’t emulate architectures or real hardware, instead concentrating on paravirtualized devices, such as the virtio standard.
crosvm is currently used to run Linux/Android guests on ChromeOS devices.
- Documentation
- Announcements
- Developer Mailing List
- #crosvm on matrix.org
- Source code
- API doc, useful for searching API.
- For contribution, see the contributor guide. Mirror repository is available at GitHub for your convenience, but we don't accept bug reports or pull requests there.
- Public issue tracker
- For Googlers: See go/crosvm#filing-bugs.
