* Re: Hart isolation configuration failure (error -3) with OpenSBI 1.8 on QEMU 10.1.3 rva22s64/rva23s64 profiles
2026-01-05 17:42 Hart isolation configuration failure (error -3) with OpenSBI 1.8 on QEMU 10.1.3 rva22s64/rva23s64 profiles Thomas Perrot
@ 2026-01-06 8:34 ` Anup Patel
2026-01-06 10:37 ` Anup Patel
2026-01-07 2:48 ` Xiang W
2 siblings, 0 replies; 9+ messages in thread
From: Anup Patel @ 2026-01-06 8:34 UTC (permalink / raw)
To: Thomas Perrot; +Cc: OpenSBI, qemu-riscv
On Mon, Jan 5, 2026 at 11:13 PM Thomas Perrot <thomas.perrot@bootlin.com> wrote:
>
> Hello,
>
> Happy New Year!
>
> I'm facing a hart isolation configuration error when running OpenSBI
> 1.8 on QEMU 10.1.3 with the RISC-V application profiles rva22s64 and
> rva23s64:
>
> init_coldboot: hart isolation configure failed (error -3)
>
> No issue occurs when using the rv64 profile. The system continues to
> boot after the error, but I'd like to understand the root cause.
>
> I haven't tested OpenSBI 1.8 on real hardware yet - that's my next
> step.
>
> Is there a known QEMU issue? Is there a recommended workaround besides
> using rv64?
I had tested on real SiFive Unleashed and StarFive VisionFive 2 board
along with QEMU virt machine and QEMU sifive_u machine.
On QEMU virt, I had only tested rv64 and max CPU types which
worked fine. I guess I should include rva22s64 and rva23s64
CPU types in my testing as well.
>
> Below is the complete trace:
>
> qemu-system-riscv64 -device virtio-net-
> device,netdev=net0,mac=52:54:00:12:35:02 -netdev
> user,id=net0,hostfwd=tcp:127.0.0.1:2222-:22,hostfwd=tcp:127.0.0.1:2323-
> :23,tftp=/src/build/tmp/deploy/images/qemuriscv64 -object rng-
> random,filename=/dev/urandom,id=rng0 -device virtio-rng-pci,rng=rng0 -
> drive id=disk0,file=/src/build/tmp/deploy/images/qemuriscv64/core-
> image-minimal-qemuriscv64.rootfs-20260105173847.ext4,if=none,format=raw
> -device virtio-blk-device,drive=disk0 -device qemu-xhci -device usb-
> tablet -device usb-kbd -machine virt -cpu rva23s64 -smp 4 -m 256 -
> snapshot -serial mon:stdio -serial null -nographic -device bochs-
> display -bios /src/build/tmp/deploy/images/qemuriscv64/fw_jump.elf -
> kernel /src/build/tmp/deploy/images/qemuriscv64/Image -append
> 'root=/dev/vda rw mem=256M ip=dhcp console=ttyS0 console=hvc0
> earlycon=sbi swiotlb=0
>
> OpenSBI v1.8
> ____ _____ ____ _____
> / __ \ / ____| _ \_ _|
> | | | |_ __ ___ _ __ | (___ | |_) || |
> | | | | '_ \ / _ \ '_ \ \___ \| _ < | |
> | |__| | |_) | __/ | | |____) | |_) || |_
> \____/| .__/ \___|_| |_|_____/|____/_____|
> | |
> |_|
>
> Platform Name : riscv-virtio,qemu
> Platform Features : medeleg
> Platform HART Count : 4
> Platform HART Protection : ---
> Platform IPI Device : aclint-mswi
> Platform Timer Device : aclint-mtimer @ 10000000Hz
> Platform Console Device : uart8250
> Platform HSM Device : ---
> Platform PMU Device : ---
> Platform Reboot Device : syscon-reboot
> Platform Shutdown Device : syscon-poweroff
> Platform Suspend Device : ---
> Platform CPPC Device : ---
> Firmware Base : 0x80000000
> Firmware Size : 357 KB
> Firmware RW Offset : 0x40000
> Firmware RW Size : 101 KB
> Firmware Heap Offset : 0x4d000
> Firmware Heap Size : 49 KB (total), 0 KB (reserved), 13 KB
> (used), 35 KB (free)
> Firmware Scratch Size : 4096 B (total), 1464 B (used), 2632 B
> (free)
> Runtime SBI Version : 3.0
> Standard SBI Extensions :
> time,rfnc,ipi,base,hsm,srst,pmu,dbcn,fwft,legacy,dbtr,sse
> Experimental SBI Extensions : none
>
> Domain0 Name : root
> Domain0 Boot HART : 0
> Domain0 HARTs : 0*,1*,2*,3*
> Domain0 Region00 : 0x0000000080040000-0x000000008005ffff M:
> (F,R,W) S/U: ()
> Domain0 Region01 : 0x0000000080000000-0x000000008003ffff M:
> (F,R,X) S/U: ()
> Domain0 Region02 : 0x0000000000100000-0x0000000000100fff M:
> (I,R,W) S/U: (R,W)
> Domain0 Region03 : 0x0000000010000000-0x0000000010000fff M:
> (I,R,W) S/U: (R,W)
> Domain0 Region04 : 0x0000000002000000-0x000000000200ffff M:
> (I,R,W) S/U: ()
> Domain0 Region05 : 0x000000000c400000-0x000000000c5fffff M:
> (I,R,W) S/U: (R,W)
> Domain0 Region06 : 0x000000000c000000-0x000000000c3fffff M:
> (I,R,W) S/U: (R,W)
> Domain0 Region07 : 0x0000000000000000-0xffffffffffffffff M:
> () S/U: (R,W,X)
> Domain0 Next Address : 0x0000000080200000
> Domain0 Next Arg1 : 0x0000000082200000
> Domain0 Next Mode : S-mode
> Domain0 SysReset : yes
> Domain0 SysSuspend : yes
>
> Boot HART ID : 0
> Boot HART Domain : root
> Boot HART Priv Version : v1.12
> Boot HART Base ISA : rv64imafdcbvh
> Boot HART ISA Extensions :
> smstateen,sscofpmf,sstc,zicntr,zihpm,zicboz,zicbom,svpbmt,sdtrig,svade,
> smnpm,ssstateen
> Boot HART PMP Count : 0
> Boot HART PMP Granularity : 0 bits
> Boot HART PMP Address Bits : 0
> Boot HART MHPM Info : 16 (0x0007fff8)
> Boot HART Debug Triggers : 2 triggers
> Boot HART MIDELEG : 0x0000000000003666
> Boot HART MEDELEG : 0x0000000000f4b509
> init_coldboot: hart isolation configure failed (error -3)
>
Yes, I was able to reproduce this failure on the latest
QEMU virt machine with rva22s64 CPU type.
Regards,
Anup
--
opensbi mailing list
opensbi@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/opensbi
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Hart isolation configuration failure (error -3) with OpenSBI 1.8 on QEMU 10.1.3 rva22s64/rva23s64 profiles
2026-01-05 17:42 Hart isolation configuration failure (error -3) with OpenSBI 1.8 on QEMU 10.1.3 rva22s64/rva23s64 profiles Thomas Perrot
2026-01-06 8:34 ` Anup Patel
@ 2026-01-06 10:37 ` Anup Patel
2026-01-07 2:48 ` Xiang W
2 siblings, 0 replies; 9+ messages in thread
From: Anup Patel @ 2026-01-06 10:37 UTC (permalink / raw)
To: Thomas Perrot; +Cc: OpenSBI, qemu-riscv
On Mon, Jan 5, 2026 at 11:13 PM Thomas Perrot <thomas.perrot@bootlin.com> wrote:
>
> Hello,
>
> Happy New Year!
>
> I'm facing a hart isolation configuration error when running OpenSBI
> 1.8 on QEMU 10.1.3 with the RISC-V application profiles rva22s64 and
> rva23s64:
>
> init_coldboot: hart isolation configure failed (error -3)
>
> No issue occurs when using the rv64 profile. The system continues to
> boot after the error, but I'd like to understand the root cause.
>
> I haven't tested OpenSBI 1.8 on real hardware yet - that's my next
> step.
>
> Is there a known QEMU issue? Is there a recommended workaround besides
> using rv64?
>
> Below is the complete trace:
>
> qemu-system-riscv64 -device virtio-net-
> device,netdev=net0,mac=52:54:00:12:35:02 -netdev
> user,id=net0,hostfwd=tcp:127.0.0.1:2222-:22,hostfwd=tcp:127.0.0.1:2323-
> :23,tftp=/src/build/tmp/deploy/images/qemuriscv64 -object rng-
> random,filename=/dev/urandom,id=rng0 -device virtio-rng-pci,rng=rng0 -
> drive id=disk0,file=/src/build/tmp/deploy/images/qemuriscv64/core-
> image-minimal-qemuriscv64.rootfs-20260105173847.ext4,if=none,format=raw
> -device virtio-blk-device,drive=disk0 -device qemu-xhci -device usb-
> tablet -device usb-kbd -machine virt -cpu rva23s64 -smp 4 -m 256 -
> snapshot -serial mon:stdio -serial null -nographic -device bochs-
> display -bios /src/build/tmp/deploy/images/qemuriscv64/fw_jump.elf -
> kernel /src/build/tmp/deploy/images/qemuriscv64/Image -append
> 'root=/dev/vda rw mem=256M ip=dhcp console=ttyS0 console=hvc0
> earlycon=sbi swiotlb=0
>
> OpenSBI v1.8
> ____ _____ ____ _____
> / __ \ / ____| _ \_ _|
> | | | |_ __ ___ _ __ | (___ | |_) || |
> | | | | '_ \ / _ \ '_ \ \___ \| _ < | |
> | |__| | |_) | __/ | | |____) | |_) || |_
> \____/| .__/ \___|_| |_|_____/|____/_____|
> | |
> |_|
>
> Platform Name : riscv-virtio,qemu
> Platform Features : medeleg
> Platform HART Count : 4
> Platform HART Protection : ---
> Platform IPI Device : aclint-mswi
> Platform Timer Device : aclint-mtimer @ 10000000Hz
> Platform Console Device : uart8250
> Platform HSM Device : ---
> Platform PMU Device : ---
> Platform Reboot Device : syscon-reboot
> Platform Shutdown Device : syscon-poweroff
> Platform Suspend Device : ---
> Platform CPPC Device : ---
> Firmware Base : 0x80000000
> Firmware Size : 357 KB
> Firmware RW Offset : 0x40000
> Firmware RW Size : 101 KB
> Firmware Heap Offset : 0x4d000
> Firmware Heap Size : 49 KB (total), 0 KB (reserved), 13 KB
> (used), 35 KB (free)
> Firmware Scratch Size : 4096 B (total), 1464 B (used), 2632 B
> (free)
> Runtime SBI Version : 3.0
> Standard SBI Extensions :
> time,rfnc,ipi,base,hsm,srst,pmu,dbcn,fwft,legacy,dbtr,sse
> Experimental SBI Extensions : none
>
> Domain0 Name : root
> Domain0 Boot HART : 0
> Domain0 HARTs : 0*,1*,2*,3*
> Domain0 Region00 : 0x0000000080040000-0x000000008005ffff M:
> (F,R,W) S/U: ()
> Domain0 Region01 : 0x0000000080000000-0x000000008003ffff M:
> (F,R,X) S/U: ()
> Domain0 Region02 : 0x0000000000100000-0x0000000000100fff M:
> (I,R,W) S/U: (R,W)
> Domain0 Region03 : 0x0000000010000000-0x0000000010000fff M:
> (I,R,W) S/U: (R,W)
> Domain0 Region04 : 0x0000000002000000-0x000000000200ffff M:
> (I,R,W) S/U: ()
> Domain0 Region05 : 0x000000000c400000-0x000000000c5fffff M:
> (I,R,W) S/U: (R,W)
> Domain0 Region06 : 0x000000000c000000-0x000000000c3fffff M:
> (I,R,W) S/U: (R,W)
> Domain0 Region07 : 0x0000000000000000-0xffffffffffffffff M:
> () S/U: (R,W,X)
> Domain0 Next Address : 0x0000000080200000
> Domain0 Next Arg1 : 0x0000000082200000
> Domain0 Next Mode : S-mode
> Domain0 SysReset : yes
> Domain0 SysSuspend : yes
>
> Boot HART ID : 0
> Boot HART Domain : root
> Boot HART Priv Version : v1.12
> Boot HART Base ISA : rv64imafdcbvh
> Boot HART ISA Extensions :
> smstateen,sscofpmf,sstc,zicntr,zihpm,zicboz,zicbom,svpbmt,sdtrig,svade,
> smnpm,ssstateen
> Boot HART PMP Count : 0
> Boot HART PMP Granularity : 0 bits
> Boot HART PMP Address Bits : 0
> Boot HART MHPM Info : 16 (0x0007fff8)
> Boot HART Debug Triggers : 2 triggers
> Boot HART MIDELEG : 0x0000000000003666
> Boot HART MEDELEG : 0x0000000000f4b509
> init_coldboot: hart isolation configure failed (error -3)
Thinking about this more, this looks like QEMU bug because
there are no PMP entries for rva22s64 and rva23s64 which
is why there is no hart isolation mechanism hence the hart
isolation configure fails.
Regards,
Anup
--
opensbi mailing list
opensbi@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/opensbi
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Hart isolation configuration failure (error -3) with OpenSBI 1.8 on QEMU 10.1.3 rva22s64/rva23s64 profiles
2026-01-05 17:42 Hart isolation configuration failure (error -3) with OpenSBI 1.8 on QEMU 10.1.3 rva22s64/rva23s64 profiles Thomas Perrot
2026-01-06 8:34 ` Anup Patel
2026-01-06 10:37 ` Anup Patel
@ 2026-01-07 2:48 ` Xiang W
2026-01-07 9:31 ` Thomas Perrot
2 siblings, 1 reply; 9+ messages in thread
From: Xiang W @ 2026-01-07 2:48 UTC (permalink / raw)
To: Thomas Perrot, OpenSBI, qemu-riscv
在 2026-01-05一的 18:42 +0100，Thomas Perrot写道：
> Hello,
>
> Happy New Year!
>
> I'm facing a hart isolation configuration error when running OpenSBI
> 1.8 on QEMU 10.1.3 with the RISC-V application profiles rva22s64 and
> rva23s64:
>
> init_coldboot: hart isolation configure failed (error -3)
>
> No issue occurs when using the rv64 profile. The system continues to
> boot after the error, but I'd like to understand the root cause.
>
> I haven't tested OpenSBI 1.8 on real hardware yet - that's my next
> step.
>
> Is there a known QEMU issue? Is there a recommended workaround besides
> using rv64?
>
> Below is the complete trace:
>
> qemu-system-riscv64 -device virtio-net-
> device,netdev=net0,mac=52:54:00:12:35:02 -netdev
> user,id=net0,hostfwd=tcp:127.0.0.1:2222-:22,hostfwd=tcp:127.0.0.1:2323-
> :23,tftp=/src/build/tmp/deploy/images/qemuriscv64 -object rng-
> random,filename=/dev/urandom,id=rng0 -device virtio-rng-pci,rng=rng0 -
> drive id=disk0,file=/src/build/tmp/deploy/images/qemuriscv64/core-
> image-minimal-qemuriscv64.rootfs-20260105173847.ext4,if=none,format=raw
> -device virtio-blk-device,drive=disk0 -device qemu-xhci -device usb-
> tablet -device usb-kbd -machine virt -cpu rva23s64 -smp 4 -m 256 -
QEMU disables PMP by default; the following option needs to be added.
-cpu rva23s64,pmp=true
Regards,
Xiang W
> snapshot -serial mon:stdio -serial null -nographic -device bochs-
> display -bios /src/build/tmp/deploy/images/qemuriscv64/fw_jump.elf -
> kernel /src/build/tmp/deploy/images/qemuriscv64/Image -append
> 'root=/dev/vda rw mem=256M ip=dhcp console=ttyS0 console=hvc0
> earlycon=sbi swiotlb=0
>
> OpenSBI v1.8
> ____ _____ ____ _____
> / __ \ / ____| _ \_ _|
> | | | |_ __ ___ _ __ | (___ | |_) || |
> | | | | '_ \ / _ \ '_ \ \___ \| _ < | |
> | |__| | |_) | __/ | | |____) | |_) || |_
> \____/| .__/ \___|_| |_|_____/|____/_____|
> | |
> |_|
>
> Platform Name : riscv-virtio,qemu
> Platform Features : medeleg
> Platform HART Count : 4
> Platform HART Protection : ---
> Platform IPI Device : aclint-mswi
> Platform Timer Device : aclint-mtimer @ 10000000Hz
> Platform Console Device : uart8250
> Platform HSM Device : ---
> Platform PMU Device : ---
> Platform Reboot Device : syscon-reboot
> Platform Shutdown Device : syscon-poweroff
> Platform Suspend Device : ---
> Platform CPPC Device : ---
> Firmware Base : 0x80000000
> Firmware Size : 357 KB
> Firmware RW Offset : 0x40000
> Firmware RW Size : 101 KB
> Firmware Heap Offset : 0x4d000
> Firmware Heap Size : 49 KB (total), 0 KB (reserved), 13 KB
> (used), 35 KB (free)
> Firmware Scratch Size : 4096 B (total), 1464 B (used), 2632 B
> (free)
> Runtime SBI Version : 3.0
> Standard SBI Extensions :
> time,rfnc,ipi,base,hsm,srst,pmu,dbcn,fwft,legacy,dbtr,sse
> Experimental SBI Extensions : none
>
> Domain0 Name : root
> Domain0 Boot HART : 0
> Domain0 HARTs : 0*,1*,2*,3*
> Domain0 Region00 : 0x0000000080040000-0x000000008005ffff M:
> (F,R,W) S/U: ()
> Domain0 Region01 : 0x0000000080000000-0x000000008003ffff M:
> (F,R,X) S/U: ()
> Domain0 Region02 : 0x0000000000100000-0x0000000000100fff M:
> (I,R,W) S/U: (R,W)
> Domain0 Region03 : 0x0000000010000000-0x0000000010000fff M:
> (I,R,W) S/U: (R,W)
> Domain0 Region04 : 0x0000000002000000-0x000000000200ffff M:
> (I,R,W) S/U: ()
> Domain0 Region05 : 0x000000000c400000-0x000000000c5fffff M:
> (I,R,W) S/U: (R,W)
> Domain0 Region06 : 0x000000000c000000-0x000000000c3fffff M:
> (I,R,W) S/U: (R,W)
> Domain0 Region07 : 0x0000000000000000-0xffffffffffffffff M:
> () S/U: (R,W,X)
> Domain0 Next Address : 0x0000000080200000
> Domain0 Next Arg1 : 0x0000000082200000
> Domain0 Next Mode : S-mode
> Domain0 SysReset : yes
> Domain0 SysSuspend : yes
>
> Boot HART ID : 0
> Boot HART Domain : root
> Boot HART Priv Version : v1.12
> Boot HART Base ISA : rv64imafdcbvh
> Boot HART ISA Extensions :
> smstateen,sscofpmf,sstc,zicntr,zihpm,zicboz,zicbom,svpbmt,sdtrig,svade,
> smnpm,ssstateen
> Boot HART PMP Count : 0
> Boot HART PMP Granularity : 0 bits
> Boot HART PMP Address Bits : 0
> Boot HART MHPM Info : 16 (0x0007fff8)
> Boot HART Debug Triggers : 2 triggers
> Boot HART MIDELEG : 0x0000000000003666
> Boot HART MEDELEG : 0x0000000000f4b509
> init_coldboot: hart isolation configure failed (error -3)
>
> Kind regards,
> Thomas Perrot
--
opensbi mailing list
opensbi@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/opensbi
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Hart isolation configuration failure (error -3) with OpenSBI 1.8 on QEMU 10.1.3 rva22s64/rva23s64 profiles
2026-01-07 2:48 ` Xiang W
@ 2026-01-07 9:31 ` Thomas Perrot
2026-01-08 13:33 ` Anup Patel
0 siblings, 1 reply; 9+ messages in thread
From: Thomas Perrot @ 2026-01-07 9:31 UTC (permalink / raw)
To: Xiang W, OpenSBI, qemu-riscv; +Cc: thomas.perrot@bootlin.com
[-- Attachment #1.1: Type: text/plain, Size: 5880 bytes --]
Hello Xiang,
On Wed, 2026-01-07 at 10:48 +0800, Xiang W wrote:
> 在 2026-01-05一的 18:42 +0100，Thomas Perrot写道：
> > Hello,
> >
> > Happy New Year!
> >
> > I'm facing a hart isolation configuration error when running
> > OpenSBI
> > 1.8 on QEMU 10.1.3 with the RISC-V application profiles rva22s64
> > and
> > rva23s64:
> >
> > init_coldboot: hart isolation configure failed (error -3)
> >
> > No issue occurs when using the rv64 profile. The system continues
> > to
> > boot after the error, but I'd like to understand the root cause.
> >
> > I haven't tested OpenSBI 1.8 on real hardware yet - that's my next
> > step.
> >
> > Is there a known QEMU issue? Is there a recommended workaround
> > besides
> > using rv64?
> >
> > Below is the complete trace:
> >
> > qemu-system-riscv64 -device virtio-net-
> > device,netdev=net0,mac=52:54:00:12:35:02 -netdev
> > user,id=net0,hostfwd=tcp:127.0.0.1:2222-
> > :22,hostfwd=tcp:127.0.0.1:2323-
> > :23,tftp=/src/build/tmp/deploy/images/qemuriscv64 -object rng-
> > random,filename=/dev/urandom,id=rng0 -device virtio-rng-
> > pci,rng=rng0 -
> > drive id=disk0,file=/src/build/tmp/deploy/images/qemuriscv64/core-
> > image-minimal-qemuriscv64.rootfs-
> > 20260105173847.ext4,if=none,format=raw
> > -device virtio-blk-device,drive=disk0 -device qemu-xhci -device
> > usb-
> > tablet -device usb-kbd -machine virt -cpu rva23s64 -smp 4 -m 256 -
> QEMU disables PMP by default; the following option needs to be added.
>
> -cpu rva23s64,pmp=true
>
Thank you. With the additional option, the issue no longer occurs.
Kind regards,
Thomas Perrot
> Regards,
> Xiang W
>
> > snapshot -serial mon:stdio -serial null -nographic -device bochs-
> > display -bios /src/build/tmp/deploy/images/qemuriscv64/fw_jump.elf
> > -
> > kernel /src/build/tmp/deploy/images/qemuriscv64/Image -append
> > 'root=/dev/vda rw mem=256M ip=dhcp console=ttyS0 console=hvc0
> > earlycon=sbi swiotlb=0
> >
> > OpenSBI v1.8
> > ____ _____ ____ _____
> > / __ \ / ____| _ \_ _|
> > | | | |_ __ ___ _ __ | (___ | |_) || |
> > | | | | '_ \ / _ \ '_ \ \___ \| _ < | |
> > | |__| | |_) | __/ | | |____) | |_) || |_
> > \____/| .__/ \___|_| |_|_____/|____/_____|
> > | |
> > |_|
> >
> > Platform Name : riscv-virtio,qemu
> > Platform Features : medeleg
> > Platform HART Count : 4
> > Platform HART Protection : ---
> > Platform IPI Device : aclint-mswi
> > Platform Timer Device : aclint-mtimer @ 10000000Hz
> > Platform Console Device : uart8250
> > Platform HSM Device : ---
> > Platform PMU Device : ---
> > Platform Reboot Device : syscon-reboot
> > Platform Shutdown Device : syscon-poweroff
> > Platform Suspend Device : ---
> > Platform CPPC Device : ---
> > Firmware Base : 0x80000000
> > Firmware Size : 357 KB
> > Firmware RW Offset : 0x40000
> > Firmware RW Size : 101 KB
> > Firmware Heap Offset : 0x4d000
> > Firmware Heap Size : 49 KB (total), 0 KB (reserved), 13 KB
> > (used), 35 KB (free)
> > Firmware Scratch Size : 4096 B (total), 1464 B (used), 2632 B
> > (free)
> > Runtime SBI Version : 3.0
> > Standard SBI Extensions :
> > time,rfnc,ipi,base,hsm,srst,pmu,dbcn,fwft,legacy,dbtr,sse
> > Experimental SBI Extensions : none
> >
> > Domain0 Name : root
> > Domain0 Boot HART : 0
> > Domain0 HARTs : 0*,1*,2*,3*
> > Domain0 Region00 : 0x0000000080040000-0x000000008005ffff
> > M:
> > (F,R,W) S/U: ()
> > Domain0 Region01 : 0x0000000080000000-0x000000008003ffff
> > M:
> > (F,R,X) S/U: ()
> > Domain0 Region02 : 0x0000000000100000-0x0000000000100fff
> > M:
> > (I,R,W) S/U: (R,W)
> > Domain0 Region03 : 0x0000000010000000-0x0000000010000fff
> > M:
> > (I,R,W) S/U: (R,W)
> > Domain0 Region04 : 0x0000000002000000-0x000000000200ffff
> > M:
> > (I,R,W) S/U: ()
> > Domain0 Region05 : 0x000000000c400000-0x000000000c5fffff
> > M:
> > (I,R,W) S/U: (R,W)
> > Domain0 Region06 : 0x000000000c000000-0x000000000c3fffff
> > M:
> > (I,R,W) S/U: (R,W)
> > Domain0 Region07 : 0x0000000000000000-0xffffffffffffffff
> > M:
> > () S/U: (R,W,X)
> > Domain0 Next Address : 0x0000000080200000
> > Domain0 Next Arg1 : 0x0000000082200000
> > Domain0 Next Mode : S-mode
> > Domain0 SysReset : yes
> > Domain0 SysSuspend : yes
> >
> > Boot HART ID : 0
> > Boot HART Domain : root
> > Boot HART Priv Version : v1.12
> > Boot HART Base ISA : rv64imafdcbvh
> > Boot HART ISA Extensions :
> > smstateen,sscofpmf,sstc,zicntr,zihpm,zicboz,zicbom,svpbmt,sdtrig,sv
> > ade,
> > smnpm,ssstateen
> > Boot HART PMP Count : 0
> > Boot HART PMP Granularity : 0 bits
> > Boot HART PMP Address Bits : 0
> > Boot HART MHPM Info : 16 (0x0007fff8)
> > Boot HART Debug Triggers : 2 triggers
> > Boot HART MIDELEG : 0x0000000000003666
> > Boot HART MEDELEG : 0x0000000000f4b509
> > init_coldboot: hart isolation configure failed (error -3)
> >
> > Kind regards,
> > Thomas Perrot
--
Thomas Perrot, Bootlin
Embedded Linux and kernel engineering
https://bootlin.com
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
[-- Attachment #2: Type: text/plain, Size: 105 bytes --]
--
opensbi mailing list
opensbi@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/opensbi
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Hart isolation configuration failure (error -3) with OpenSBI 1.8 on QEMU 10.1.3 rva22s64/rva23s64 profiles
2026-01-07 9:31 ` Thomas Perrot
@ 2026-01-08 13:33 ` Anup Patel
2026-01-08 13:41 ` Daniel Henrique Barboza
0 siblings, 1 reply; 9+ messages in thread
From: Anup Patel @ 2026-01-08 13:33 UTC (permalink / raw)
To: Thomas Perrot; +Cc: Xiang W, OpenSBI, qemu-riscv
Hi Thomas,
On Wed, Jan 7, 2026 at 3:02 PM Thomas Perrot <thomas.perrot@bootlin.com> wrote:
>
> Hello Xiang,
>
> On Wed, 2026-01-07 at 10:48 +0800, Xiang W wrote:
> > 在 2026-01-05一的 18:42 +0100，Thomas Perrot写道：
> > > Hello,
> > >
> > > Happy New Year!
> > >
> > > I'm facing a hart isolation configuration error when running
> > > OpenSBI
> > > 1.8 on QEMU 10.1.3 with the RISC-V application profiles rva22s64
> > > and
> > > rva23s64:
> > >
> > > init_coldboot: hart isolation configure failed (error -3)
> > >
> > > No issue occurs when using the rv64 profile. The system continues
> > > to
> > > boot after the error, but I'd like to understand the root cause.
> > >
> > > I haven't tested OpenSBI 1.8 on real hardware yet - that's my next
> > > step.
> > >
> > > Is there a known QEMU issue? Is there a recommended workaround
> > > besides
> > > using rv64?
> > >
> > > Below is the complete trace:
> > >
> > > qemu-system-riscv64 -device virtio-net-
> > > device,netdev=net0,mac=52:54:00:12:35:02 -netdev
> > > user,id=net0,hostfwd=tcp:127.0.0.1:2222-
> > > :22,hostfwd=tcp:127.0.0.1:2323-
> > > :23,tftp=/src/build/tmp/deploy/images/qemuriscv64 -object rng-
> > > random,filename=/dev/urandom,id=rng0 -device virtio-rng-
> > > pci,rng=rng0 -
> > > drive id=disk0,file=/src/build/tmp/deploy/images/qemuriscv64/core-
> > > image-minimal-qemuriscv64.rootfs-
> > > 20260105173847.ext4,if=none,format=raw
> > > -device virtio-blk-device,drive=disk0 -device qemu-xhci -device
> > > usb-
> > > tablet -device usb-kbd -machine virt -cpu rva23s64 -smp 4 -m 256 -
> > QEMU disables PMP by default; the following option needs to be added.
> >
> > -cpu rva23s64,pmp=true
> >
>
> Thank you. With the additional option, the issue no longer occurs.
I have done an incremental OpenSBI v1.8.1 release
to address this issue. With this incremental release,
you don't have to explicitly pass "pmp=true" to
rva22s64 and rva23s64 CPU types in QEMU.
Regards,
Anup
--
opensbi mailing list
opensbi@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/opensbi
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Hart isolation configuration failure (error -3) with OpenSBI 1.8 on QEMU 10.1.3 rva22s64/rva23s64 profiles
2026-01-08 13:33 ` Anup Patel
@ 2026-01-08 13:41 ` Daniel Henrique Barboza
2026-01-08 15:04 ` Anup Patel
0 siblings, 1 reply; 9+ messages in thread
From: Daniel Henrique Barboza @ 2026-01-08 13:41 UTC (permalink / raw)
To: Anup Patel, Thomas Perrot; +Cc: Xiang W, OpenSBI, qemu-riscv
On 1/8/2026 10:33 AM, Anup Patel wrote:
> Hi Thomas,
>
> On Wed, Jan 7, 2026 at 3:02 PM Thomas Perrot <thomas.perrot@bootlin.com> wrote:
>>
>> Hello Xiang,
>>
>> On Wed, 2026-01-07 at 10:48 +0800, Xiang W wrote:
>>> 在 2026-01-05一的 18:42 +0100，Thomas Perrot写道：
>>>> Hello,
>>>>
>>>> Happy New Year!
>>>>
>>>> I'm facing a hart isolation configuration error when running
>>>> OpenSBI
>>>> 1.8 on QEMU 10.1.3 with the RISC-V application profiles rva22s64
>>>> and
>>>> rva23s64:
>>>>
>>>> init_coldboot: hart isolation configure failed (error -3)
>>>>
>>>> No issue occurs when using the rv64 profile. The system continues
>>>> to
>>>> boot after the error, but I'd like to understand the root cause.
>>>>
>>>> I haven't tested OpenSBI 1.8 on real hardware yet - that's my next
>>>> step.
>>>>
>>>> Is there a known QEMU issue? Is there a recommended workaround
>>>> besides
>>>> using rv64?
>>>>
>>>> Below is the complete trace:
>>>>
>>>> qemu-system-riscv64 -device virtio-net-
>>>> device,netdev=net0,mac=52:54:00:12:35:02 -netdev
>>>> user,id=net0,hostfwd=tcp:127.0.0.1:2222-
>>>> :22,hostfwd=tcp:127.0.0.1:2323-
>>>> :23,tftp=/src/build/tmp/deploy/images/qemuriscv64 -object rng-
>>>> random,filename=/dev/urandom,id=rng0 -device virtio-rng-
>>>> pci,rng=rng0 -
>>>> drive id=disk0,file=/src/build/tmp/deploy/images/qemuriscv64/core-
>>>> image-minimal-qemuriscv64.rootfs-
>>>> 20260105173847.ext4,if=none,format=raw
>>>> -device virtio-blk-device,drive=disk0 -device qemu-xhci -device
>>>> usb-
>>>> tablet -device usb-kbd -machine virt -cpu rva23s64 -smp 4 -m 256 -
>>> QEMU disables PMP by default; the following option needs to be added.
>>>
>>> -cpu rva23s64,pmp=true
>>>
>>
>> Thank you. With the additional option, the issue no longer occurs.
>
> I have done an incremental OpenSBI v1.8.1 release
> to address this issue. With this incremental release,
> you don't have to explicitly pass "pmp=true" to
> rva22s64 and rva23s64 CPU types in QEMU.
Seems like we don't need this patch I sent a few days ago then:
"[PATCH] target/riscv/cpu.c: enable PMP by default for profile CPUs"
https://lore.kernel.org/qemu-devel/20260106205152.3654975-1-daniel.barboza@oss.qualcomm.com/
We can leave this patch alone. We can also leave the update to OpenSBI
1.8 alone as well and update to 1.8.1 to get the fix.
Thanks,
Daniel
>
> Regards,
> Anup
>
--
opensbi mailing list
opensbi@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/opensbi
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Hart isolation configuration failure (error -3) with OpenSBI 1.8 on QEMU 10.1.3 rva22s64/rva23s64 profiles
2026-01-08 13:41 ` Daniel Henrique Barboza
@ 2026-01-08 15:04 ` Anup Patel
2026-01-09 16:06 ` Thomas Perrot
0 siblings, 1 reply; 9+ messages in thread
From: Anup Patel @ 2026-01-08 15:04 UTC (permalink / raw)
To: Daniel Henrique Barboza
Cc: Anup Patel, Thomas Perrot, Xiang W, OpenSBI, qemu-riscv
On Thu, Jan 8, 2026 at 7:12 PM Daniel Henrique Barboza
<daniel.barboza@oss.qualcomm.com> wrote:
>
>
>
> On 1/8/2026 10:33 AM, Anup Patel wrote:
> > Hi Thomas,
> >
> > On Wed, Jan 7, 2026 at 3:02 PM Thomas Perrot <thomas.perrot@bootlin.com> wrote:
> >>
> >> Hello Xiang,
> >>
> >> On Wed, 2026-01-07 at 10:48 +0800, Xiang W wrote:
> >>> 在 2026-01-05一的 18:42 +0100，Thomas Perrot写道：
> >>>> Hello,
> >>>>
> >>>> Happy New Year!
> >>>>
> >>>> I'm facing a hart isolation configuration error when running
> >>>> OpenSBI
> >>>> 1.8 on QEMU 10.1.3 with the RISC-V application profiles rva22s64
> >>>> and
> >>>> rva23s64:
> >>>>
> >>>> init_coldboot: hart isolation configure failed (error -3)
> >>>>
> >>>> No issue occurs when using the rv64 profile. The system continues
> >>>> to
> >>>> boot after the error, but I'd like to understand the root cause.
> >>>>
> >>>> I haven't tested OpenSBI 1.8 on real hardware yet - that's my next
> >>>> step.
> >>>>
> >>>> Is there a known QEMU issue? Is there a recommended workaround
> >>>> besides
> >>>> using rv64?
> >>>>
> >>>> Below is the complete trace:
> >>>>
> >>>> qemu-system-riscv64 -device virtio-net-
> >>>> device,netdev=net0,mac=52:54:00:12:35:02 -netdev
> >>>> user,id=net0,hostfwd=tcp:127.0.0.1:2222-
> >>>> :22,hostfwd=tcp:127.0.0.1:2323-
> >>>> :23,tftp=/src/build/tmp/deploy/images/qemuriscv64 -object rng-
> >>>> random,filename=/dev/urandom,id=rng0 -device virtio-rng-
> >>>> pci,rng=rng0 -
> >>>> drive id=disk0,file=/src/build/tmp/deploy/images/qemuriscv64/core-
> >>>> image-minimal-qemuriscv64.rootfs-
> >>>> 20260105173847.ext4,if=none,format=raw
> >>>> -device virtio-blk-device,drive=disk0 -device qemu-xhci -device
> >>>> usb-
> >>>> tablet -device usb-kbd -machine virt -cpu rva23s64 -smp 4 -m 256 -
> >>> QEMU disables PMP by default; the following option needs to be added.
> >>>
> >>> -cpu rva23s64,pmp=true
> >>>
> >>
> >> Thank you. With the additional option, the issue no longer occurs.
> >
> > I have done an incremental OpenSBI v1.8.1 release
> > to address this issue. With this incremental release,
> > you don't have to explicitly pass "pmp=true" to
> > rva22s64 and rva23s64 CPU types in QEMU.
>
> Seems like we don't need this patch I sent a few days ago then:
>
>
> "[PATCH] target/riscv/cpu.c: enable PMP by default for profile CPUs"
>
> https://lore.kernel.org/qemu-devel/20260106205152.3654975-1-daniel.barboza@oss.qualcomm.com/
>
>
> We can leave this patch alone. We can also leave the update to OpenSBI
> 1.8 alone as well and update to 1.8.1 to get the fix.
I think the QEMU patch is still needed because without PMP
there is nothing to protect M-mode firmware (OpenSBI) from
lower privilege modes.
Regards,
Anup
--
opensbi mailing list
opensbi@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/opensbi
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Hart isolation configuration failure (error -3) with OpenSBI 1.8 on QEMU 10.1.3 rva22s64/rva23s64 profiles
2026-01-08 15:04 ` Anup Patel
@ 2026-01-09 16:06 ` Thomas Perrot
0 siblings, 0 replies; 9+ messages in thread
From: Thomas Perrot @ 2026-01-09 16:06 UTC (permalink / raw)
To: Anup Patel, Daniel Henrique Barboza
Cc: thomas.perrot, Anup Patel, Xiang W, OpenSBI, qemu-riscv
[-- Attachment #1.1: Type: text/plain, Size: 3543 bytes --]
Hello,
On Thu, 2026-01-08 at 20:34 +0530, Anup Patel wrote:
> On Thu, Jan 8, 2026 at 7:12 PM Daniel Henrique Barboza
> <daniel.barboza@oss.qualcomm.com> wrote:
> >
> >
> >
> > On 1/8/2026 10:33 AM, Anup Patel wrote:
> > > Hi Thomas,
> > >
> > > On Wed, Jan 7, 2026 at 3:02 PM Thomas Perrot
> > > <thomas.perrot@bootlin.com> wrote:
> > > >
> > > > Hello Xiang,
> > > >
> > > > On Wed, 2026-01-07 at 10:48 +0800, Xiang W wrote:
> > > > > 在 2026-01-05一的 18:42 +0100，Thomas Perrot写道：
> > > > > > Hello,
> > > > > >
> > > > > > Happy New Year!
> > > > > >
> > > > > > I'm facing a hart isolation configuration error when
> > > > > > running
> > > > > > OpenSBI
> > > > > > 1.8 on QEMU 10.1.3 with the RISC-V application profiles
> > > > > > rva22s64
> > > > > > and
> > > > > > rva23s64:
> > > > > >
> > > > > > init_coldboot: hart isolation configure failed (error
> > > > > > -3)
> > > > > >
> > > > > > No issue occurs when using the rv64 profile. The system
> > > > > > continues
> > > > > > to
> > > > > > boot after the error, but I'd like to understand the root
> > > > > > cause.
> > > > > >
> > > > > > I haven't tested OpenSBI 1.8 on real hardware yet - that's
> > > > > > my next
> > > > > > step.
> > > > > >
> > > > > > Is there a known QEMU issue? Is there a recommended
> > > > > > workaround
> > > > > > besides
> > > > > > using rv64?
> > > > > >
> > > > > > Below is the complete trace:
> > > > > >
> > > > > > qemu-system-riscv64 -device virtio-net-
> > > > > > device,netdev=net0,mac=52:54:00:12:35:02 -netdev
> > > > > > user,id=net0,hostfwd=tcp:127.0.0.1:2222-
> > > > > > :22,hostfwd=tcp:127.0.0.1:2323-
> > > > > > :23,tftp=/src/build/tmp/deploy/images/qemuriscv64 -object
> > > > > > rng-
> > > > > > random,filename=/dev/urandom,id=rng0 -device virtio-rng-
> > > > > > pci,rng=rng0 -
> > > > > > drive
> > > > > > id=disk0,file=/src/build/tmp/deploy/images/qemuriscv64/core
> > > > > > -
> > > > > > image-minimal-qemuriscv64.rootfs-
> > > > > > 20260105173847.ext4,if=none,format=raw
> > > > > > -device virtio-blk-device,drive=disk0 -device qemu-xhci -
> > > > > > device
> > > > > > usb-
> > > > > > tablet -device usb-kbd -machine virt -cpu rva23s64 -smp 4
> > > > > > -m 256 -
> > > > > QEMU disables PMP by default; the following option needs to
> > > > > be added.
> > > > >
> > > > > -cpu rva23s64,pmp=true
> > > > >
> > > >
> > > > Thank you. With the additional option, the issue no longer
> > > > occurs.
> > >
> > > I have done an incremental OpenSBI v1.8.1 release
> > > to address this issue. With this incremental release,
> > > you don't have to explicitly pass "pmp=true" to
> > > rva22s64 and rva23s64 CPU types in QEMU.
> >
> > Seems like we don't need this patch I sent a few days ago then:
> >
> >
> > "[PATCH] target/riscv/cpu.c: enable PMP by default for profile
> > CPUs"
> >
> > https://lore.kernel.org/qemu-devel/20260106205152.3654975-1-daniel.barboza@oss.qualcomm.com/
> >
> >
> > We can leave this patch alone. We can also leave the update to
> > OpenSBI
> > 1.8 alone as well and update to 1.8.1 to get the fix.
>
> I think the QEMU patch is still needed because without PMP
> there is nothing to protect M-mode firmware (OpenSBI) from
> lower privilege modes.
>
Thank you for the update.
Kind regards,
Thomas Perrot
> Regards,
> Anup
--
Thomas Perrot, Bootlin
Embedded Linux and kernel engineering
https://bootlin.com
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
[-- Attachment #2: Type: text/plain, Size: 105 bytes --]
--
opensbi mailing list
opensbi@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/opensbi
^ permalink raw reply [flat|nested] 9+ messages in thread