[peikachu]

Summary

Align zone1's memory layout in zone1-linux-virtio.json and virtio-backend.json on qemu-aia with zone1-linux.dts and zone1-linux-passthrough.json:

• zone1 RAM: 0x83000000/0x0C000000 → 0x85000000/0x0A000000
• kernel/entry: 0x84000000 → 0x86000000; dtb: 0x83000000 → 0x85000000
• backend zone0_ipa/zonex_ipa/size updated to match

Motivation

0x80000000~0x85000000 is reserved for OpenSBI and hvisor, so zone0 has no stage-2 mapping for it. hvisor zone start copies the kernel into this range, which traps into hvisor. hvisor then tries to decode the instruction as MMIO and panics because it is a vector store (trap instruction is not Load or Store, inst 0x02050027). Even without the panic, a kernel at 0x84000000 would lie outside the memory@85000000 node in zone1's dtb.

The new layout is the same as zone1-linux-passthrough.json: dtb at the start of RAM (0x85000000), kernel at 0x86000000. This range is inside zone0's RAM, so zone0 can mmap it to load the kernel and serve the virtqueues.

Verification

On riscv64/qemu-aia (Linux 6.13 for zone0 and zone1): started zone1 with zone1-linux-virtio.json plus the virtio backend. zone1 booted to a shell, and hvisor reported no ERROR.