<html><head></head><body><div class="yahoo-style-wrap" style="font-family:lucida console, sans-serif;font-size:13px;"><div dir="ltr" data-setdir="false"><div>Hello,everyone<br><br>I'm trying to run RTEMS such as Xen DomU on QEMU but I'm running into problems. <br>I 've done this according to the following steps:<br><br><ol dir="ltr" data-setdir="false"><li>Configuring and building XEN from source using PetaLinux for xilinx-zcu102-v2019.2 BSP.</li><li><span>Running Xen dom0 on QEMU from pre-built images.</span></li><li><span><span>Building RTEMS for xen_virtual bsp</span></span></li><li><span><span><span>Running RTEMS's hello.exe(<span>testsuites/samples</span>) example as DomU</span><br></span></span></li></ol>Creating a configuration file with the following contents.<br><br> name = "hello"<br> kernel = "hello.bin"<br> memory = 8<br> vcpus = 1<br> gic_version = "v2"<br> vuart = "sbsa_uart"<br><br>Creating the virtual machine by command xl create -c hello.cfg but execution has been failed:<br><br>xilinx-zcu102-2019_2 login: (XEN) Hypervisor Trap. HSR=0x2000000 EC=0x0 IL=1 Syndrome=0x0<br>(XEN) CPU0: Unexpected Trap: Hypervisor<br>(XEN) ----[ Xen-4.11.2-pre arm64 debug=n Not tainted ]----<br>(XEN) CPU: 0<br>(XEN) PC: 0000000000241e68 domain.c#schedule_tail+0x288/0x2b8<br>(XEN) LR: 0000000000241d3c<br>(XEN) SP: 00008000fff27e70<br>(XEN) CPSR: 600002c9 MODE:64-bit EL2h (Hypervisor, handler)<br>(XEN) X0: 0000000000000000 X1: 0000000000000000 X2: 000000004002e0f0<br>(XEN) X3: 0000000000000000 X4: 00008000ffe7d5cc X5: 000000004002e000<br>(XEN) X6: 000080004ffaf677 X7: 000000000027a000 X8: 00008000ffe7d2e0<br>(XEN) X9: 00008000fff27eb0 X10: 00008000fffbbb70 X11: 000000000030fb00<br>(XEN) X12: 000000000030fa20 X13: 000000bf83d650b8 X14: 00008000fff12400<br>(XEN) X15: 0000000000000400 X16: 0000000000000000 X17: ffffffff00000001<br>(XEN) X18: 0000000000000400 X19: 00008000fff3b000 X20: 00008000ffe7d000<br>(XEN) X21: 000000000030f000 X22: 0000000000000000 X23: 0000000000000000<br>(XEN) X24: 0000000000000000 X25: 0000000000000000 X26: 0000000000000000<br>(XEN) X27: 0000000000000000 X28: 0000000000000000 FP: 0000000000000000<br>(XEN) <br>(XEN) VTCR_EL2: 80023558<br>(XEN) VTTBR_EL2: 000200087ff94000<br>(XEN) <br>(XEN) SCTLR_EL2: 30cd187d<br>(XEN) HCR_EL2: 000000000038663f<br>(XEN) TTBR0_EL2: 000000087ff04000<br>(XEN) <br>(XEN) ESR_EL2: 02000000<br>(XEN) HPFAR_EL2: 0000000000f90100<br>(XEN) FAR_EL2: ffffff8008010850<br>(XEN) <br>(XEN) Xen stack trace from sp=00008000fff27e70:<br>(XEN) 000000000030fc00 00008000fff3b000 0000000000000000 0000000000241ed0<br>(XEN) 0000000000000000 0000000000000000 0000000000241e98 0000000000000000<br>(XEN) 0000000000000000 00000000ffffffff 00000000407ff000 0000000000000000<br>(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000<br>(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000<br>(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000<br>(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000<br>(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000<br>(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000<br>(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000<br>(XEN) 0000000040008000 00000000000001d3 0000000000000000 0000000000000000<br>(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000<br>(XEN) 0000000000000000 0000000000000000<br>(XEN) Xen call trace:<br>(XEN) [<0000000000241e68>] domain.c#schedule_tail+0x288/0x2b8 (PC)<br>(XEN) [<0000000000241d3c>] domain.c#schedule_tail+0x15c/0x2b8 (LR)<br>(XEN) <br>(XEN) <br>(XEN) ****************************************<br>(XEN) Panic on CPU 0:<br>(XEN) CPU0: Unexpected Trap: Hypervisor<br>(XEN) <br>(XEN) ****************************************<br>(XEN) <br>(XEN) Reboot in five seconds...<br>qemu-system-aarch64: Trying to execute code outside RAM or ROM at 0x00000000fef319dc<br>This usually means one of the following happened:<br><br>(1) You told QEMU to execute a kernel for the wrong machine type, and it crashed <br> on startup (eg trying to run a raspberry pi kernel on a versatilepb QEMU machine)<br>(2) You didn't give QEMU a kernel or BIOS filename at all, and QEMU executed a <br> ROM full of no-op instructions until it fell off the end<br>(3) Your guest kernel has a bug and crashed by jumping off into nowhere<br><br>This is almost always one of the first two, so check your command line <br>and that you are using the right type of kernel for this machine.<br>If you think option (3) is likely then you can try debugging your <br>guest with the -d debug options; in particular -d guest_errors will <br>cause the log to include a dump of the guest register state at this point.<br><br>Execution cannot continue; stopping here.<br><br>qemu-system-microblazeel: /pmu@0: Disconnected clk=1115630696488 ns<br><br>I searched for an answer for a while and can't find anything. <br>I'll glad if you could give me any suggestions which could be helpful in this regard.<br><br>Best regards</div><div><br></div></div></div></body></html>