github/linuxkit
1
0
Fork 0
mirror of https://github.com/linuxkit/linuxkit.git synced 2025-07-18 17:01:07 +00:00
Code Issues Projects Releases Wiki Activity

contrib: Update crosvm README

Browse Source 
Signed-off-by: Rolf Neugebauer <rn@rneugeba.io>
This commit is contained in:
Rolf Neugebauer 2018-11-14 23:15:56 +00:00
parent fa719063a8
commit f1667aac67
1 changed files with 7 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
contrib/crosvm/README.md
View File

@ -26,35 +26,29 @@ You may also have to create an empty directory `/var/empty`.
You can build a LinuxKit image suitable for `crosvm` with the You can build a LinuxKit image suitable for `crosvm` with the
`kernel+squashfs` build format. For example, using `minimal.yml` from `kernel+squashfs` build format. For example, using `minimal.yml` from
the `./examples` directory, run: the `./examples` directory, run (but also see the known issues):
```sh ```sh
linuxkit build -format kernel+squashfs minimal.yml linuxkit build -format kernel+squashfs -decompress-kernel minimal.yml
``` ```
The generated kernel file (`minimal-kernel`) needs to be converted as The `-vmlinux` switch is needed since `crosvm` does not grok
`crosvm` does not grok `bzImage`s. You can convert the LinuxKit kernel compressed linux kernel images.
image with
[extract-vmlinux](https://raw.githubusercontent.com/torvalds/linux/master/scripts/extract-vmlinux):
```sh
extract-vmlinux minimal-kernel > minimal-vmlinux
```
Then you can run `crosvm`: Then you can run `crosvm`:
```sh ```sh
./crosvm run --seccomp-policy-dir=./seccomp/x86_64 \ crosvm run --disable-sandbox \
--root ./minimal-squashfs.img \ --root ./minimal-squashfs.img \
--mem 2048 \ --mem 2048 \
--multiprocess \
--socket ./linuxkit-socket \ --socket ./linuxkit-socket \
minimal-vmlinux minimal-kernel
``` ```
## Known issues ## Known issues
- With 4.14.x, a `BUG_ON()` is hit in `drivers/base/driver.c`. 4.9.x - With 4.14.x, a `BUG_ON()` is hit in `drivers/base/driver.c`. 4.9.x
kernels seem to work. kernels seem to work.
- With the latest version, I don't seem to get a interactive console.
- Networking does not yet work, so don't include a `onboot` `dhcpd` service. - Networking does not yet work, so don't include a `onboot` `dhcpd` service.
- `poweroff` from the command line does not work (crosvm does not seem - `poweroff` from the command line does not work (crosvm does not seem
to support ACPI). So to stop a VM you can use the control socket to support ACPI). So to stop a VM you can use the control socket