mirror of
https://chromium.googlesource.com/crosvm/crosvm
synced 2024-11-25 05:03:05 +00:00
No description
b7191b0188
Currently, create_composite generates a read-only composite disk by default.
But in embedded system, sometime we need to use a real disk partition as the
backing file. In this case, it is required to create a writable composite disk.
So an optional "writable" argument is added in the command line.
BUG=b:318862474
TEST=cargo test --features composite-disk
TEST=./tools/presubmit
TEST=create a writable composite disk and use it as the backing of virtio-blk,
the writing works well.
Signed-off-by: Junnan Wu <junnan01.wu@samsung.com>
Change-Id: I05033473cf28628887926b18fe17429e267f26f3
Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/5179893
Reviewed-by: Daniel Verkamp <dverkamp@chromium.org>
Commit-Queue: Daniel Verkamp <dverkamp@chromium.org>
Reviewed-by: Alexandre Courbot <acourbot@chromium.org>
|
||
|---|---|---|
| .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 | ||
| resources | ||
| riscv64 | ||
| rutabaga_gfx | ||
| sandbox | ||
| serde_keyvalue | ||
| src | ||
| swap | ||
| system_api | ||
| tests | ||
| third_party | ||
| tools | ||
| tube_transporter | ||
| usb_sys | ||
| usb_util | ||
| vendor | ||
| vfio_sys | ||
| vhost | ||
| virtio_sys | ||
| vm_control | ||
| vm_memory | ||
| win_audio | ||
| win_util | ||
| x86_64 | ||
| .dockerignore | ||
| .envrc | ||
| .gitattributes | ||
| .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.
