mirror of
https://github.com/cloud-hypervisor/cloud-hypervisor.git
synced 2024-07-07 10:15:45 +00:00
docs: Remove all virtio-mmio references
Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
This commit is contained in:
parent
8b9c9bc97f
commit
58474854f2
@ -16,20 +16,10 @@ sudo apt-get install libfdt-dev
|
|||||||
|
|
||||||
## Build
|
## Build
|
||||||
|
|
||||||
For Virtio devices, you can choose MMIO or PCI as transport option.
|
Using PCI devices requires GICv3-ITS for MSI messaging. GICv3-ITS is very common in modern servers.
|
||||||
|
|
||||||
### MMIO
|
|
||||||
|
|
||||||
```bash
|
```bash
|
||||||
cargo build --no-default-features --features mmio,kvm
|
cargo build --no-default-features --features kvm
|
||||||
```
|
|
||||||
|
|
||||||
### PCI
|
|
||||||
|
|
||||||
Using PCI devices requires GICv3-ITS for MSI messaging. GICv3-ITS is very common in modern servers, but your machine happen to be old ones with GICv2(M) (like Raspberry Pi 4) or GICv3 without ITS, MMIO can still work.
|
|
||||||
|
|
||||||
```bash
|
|
||||||
cargo build --no-default-features --features pci,kvm
|
|
||||||
```
|
```
|
||||||
|
|
||||||
## Image
|
## Image
|
||||||
@ -51,7 +41,7 @@ To build the development container:
|
|||||||
./scripts/dev_cli.sh build-container
|
./scripts/dev_cli.sh build-container
|
||||||
```
|
```
|
||||||
|
|
||||||
To build Cloud-hypervisor in the container: (The default option for Virtio transport is MMIO.)
|
To build Cloud-hypervisor in the container:
|
||||||
|
|
||||||
```bash
|
```bash
|
||||||
./scripts/dev_cli.sh build
|
./scripts/dev_cli.sh build
|
||||||
@ -62,7 +52,7 @@ To build Cloud-hypervisor in the container: (The default option for Virtio trans
|
|||||||
Assuming you have built Cloud-hypervisor with the development container, a VM can be started with command:
|
Assuming you have built Cloud-hypervisor with the development container, a VM can be started with command:
|
||||||
|
|
||||||
```bash
|
```bash
|
||||||
sudo build/cargo_target/aarch64-unknown-linux-gnu/debug/cloud-hypervisor --kernel kernel.bin --disk path=rootfs.ext4 --cmdline "keep_bootcon console=hvc0 reboot=k panic=1 pci=off root=/dev/vda rw" --cpus boot=4 --memory size=512M --serial file=serial.log --log-file log.log -vvv
|
sudo build/cargo_target/aarch64-unknown-linux-gnu/debug/cloud-hypervisor --kernel kernel.bin --disk path=rootfs.ext4 --cmdline "keep_bootcon console=hvc0 reboot=k panic=1 root=/dev/vda rw" --cpus boot=4 --memory size=512M --serial file=serial.log --log-file log.log -vvv
|
||||||
```
|
```
|
||||||
|
|
||||||
If the build was done out of the container, replace the binary path with `target/debug/cloud-hypervisor`.
|
If the build was done out of the container, replace the binary path with `target/debug/cloud-hypervisor`.
|
||||||
|
@ -75,12 +75,8 @@ feature is enabled by default.
|
|||||||
|
|
||||||
## Virtio devices
|
## Virtio devices
|
||||||
|
|
||||||
For all virtio devices listed below, both `virtio-mmio` and `virtio-pci`
|
For all virtio devices listed below, only `virtio-pci` transport layer is
|
||||||
transport layers are supported, `virtio-pci` being the default.
|
supported.
|
||||||
|
|
||||||
Both `virtio-mmio` and `virtio-pci` can be compiled out. `virtio-pci` is
|
|
||||||
built-in by default, and enabled by default. If both transport layers were
|
|
||||||
built at the same time, `virtio-pci` would be the default transport layer.
|
|
||||||
|
|
||||||
### virtio-block
|
### virtio-block
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user