blob: a47e55e90780d3b67c645715b7b8d30a72b32a8c (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
|
graphic: 0.819
device: 0.731
semantic: 0.653
PID: 0.414
other: 0.384
boot: 0.327
performance: 0.322
debug: 0.288
socket: 0.274
network: 0.265
permissions: 0.262
vnc: 0.240
files: 0.224
KVM: 0.095
qemu-system-riscv64: Some ROM regions are overlapping When memory set <= 16
Description of problem:
Steps to reproduce:
1. Build the qemu
2. run `./build/riscv64-softmmu/qemu-system-riscv64 --nographic -machine virt -m 16`
3. got error message:
```
qemu-system-riscv64: Some ROM regions are overlapping
These ROM regions might have been loaded by direct user request or by default.
They could be BIOS/firmware images, a guest kernel, initrd or some other file loaded into guest memory.
Check whether you intended to load all this guest code, and whether it has been built to load to the correct addresses.
The following two regions overlap (in the memory address space):
/home/shiroko/Developments/qemu/build/pc-bios/opensbi-riscv64-generic-fw_dynamic.bin (addresses 0x0000000080000000 - 0x0000000080019b50)
fdt (addresses 0x0000000080000000 - 0x0000000080100000)
```
Additional information:
Using `./build/riscv64-softmmu/qemu-system-riscv64 --nographic -machine virt -m 17` could bootup and seen OpenSBI messages.
This problem appears on qemu-system-riscv32 too.
|