On Wed, Mar 22, 2023 at 06:10:18AM -0300, Daniel Henrique Barboza wrote: > Today, trying to boot a RISC-V Fedora Rawhide image in a RISC-V QEMU domain > results in the following error: > > ==== > error: Failed to start domain 'riscv-fedora' > error: internal error: process exited while connecting to monitor: > 2023-03-20T17:31:02.650862Z 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. > ==== > > This happens because the default RISC-V QEMU firmware, OpenSBI, is > always loaded unless "-bios none" is passed in the command line, and the > Fedora Rawhide guest kernel has its own ROM. Other machines such as > PPC64 'pseries' shows the same behavior: the default firmware is always > loaded unless specified otherwise with the '-bios' option. What happens when these kernels are used on bare metal ? Presumably bare metal always has firmware, and the kernels successfuly overwrite it ? If so, what makes QEMU special such that it breaks ? With regards, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
