You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
4. Execute `./axvisor.sh run` to build AxVisor and start it in QEMU.
105
100
106
-
### ArceOS as guest
107
-
108
-
1. Build a client image file suitable for your own architecture. Taking the ArceOS mainline code as an example, run `make PLATFORM=aarch64-qemu-virt SMP=1 A=examples/helloworld` to generate `helloworld_aarch64-qemu-virt.bin`.
109
-
110
-
2. Create a disk image file and place the guest machine image into the file system.
111
-
112
-
- Use the `./axvisor.sh disk_img` command to generate an empty FAT32 disk image file named `disk.img`.
113
-
- Manually mount `disk.img`, and then place your guest machine image into the file system.
114
-
115
-
```console
116
-
mkdir -p tmp/tmp_img
117
-
sudo mount disk.img tmp/tmp_img
118
-
sudo cp /PATH/TO/YOUR/GUEST/VM/IMAGE tmp/tmp_img/
119
-
sudo umount tmp/tmp_img
120
-
```
121
-
122
-
3. Modify the configuration items in the corresponding `./configs/vms/<ARCH_CONFIG>.toml`
123
-
- `image_location="fs"` indicates loading from the file system.
124
-
- `kernel_path` specifies the path to the kernel image in the file system.
125
-
- `entry_point` specifies the entry address of the kernel image.
126
-
- `kernel_load_addr` specifies the loading address of the kernel image.
127
-
- others
128
-
129
-
```console
130
-
cp configs/vms/linux-qemu-aarch64.toml tmp/
131
-
```
132
-
133
-
4. Execute `./axvisor.sh defconfig` to set up the development environment and generate AxVisor config `.hvconfig.toml`.
134
-
135
-
5. Edit the `.hvconfig.toml` file to set the `vmconfigs` item to the path of your guest configuration file, for example:
0 commit comments