On Mon, Jul 26, 2021 at 12:24 PM christinefragoso--- via Devel <devel@sel4.systems> wrote: > > Hello, > > I'm trying to run the cma34cr_centos application from > camkes-vm-examples-manifest, but I get this error: "Kernel entry via Unknown > syscall, word: 65". > > I've set up VMware as described at https://docs.sel4.systems/Hardware/VMware/. > > In camkes-vm-examples-manifest/cma34cr_centos_x86_build, I've built the > kernel: > > ../init-build.sh -DCAMKES_VM_APP=cma34cr_centos > > Then I ran these commands: > > ninja > sudo ./seL4vmw.py images/kernel-x86_64-pc99 > images/capdl-loader-image-x86_64-pc99 > vmrun -T player start $HOME/vmware/seL4/seL4.vmx > while :; do > socat -d -d UNIX-CONNECT:/tmp/vsock,forever PTY,link=/tmp/mytty > done > > After VMware boots, I ran minicom in a separate terminal to see the serial > output: > > minicom -D /tmp/mytty > > Here is the full log: > > Welcome to minicom 2.7.1 > > OPTIONS: I18n > Compiled on Dec 23 2019, 02:06:26. > Port /tmp/mytty, 08:47:50 > > Press CTRL-A Z for help on special keys > > Boot config: debug_port = 0x3f8 > Boot config: disable_iommu = false > Detected 1 boot module(s): > module #0: start=0xcf3000 end=0x3821bb8 size=0x2b2ebb8 name='' > Parsing GRUB physical memory map > Physical Memory Region from 0 size 9f800 type 1 > Physical Memory Region from 9f800 size 800 type 2 > Physical Memory Region from dc000 size 24000 type 2 > Physical Memory Region from 100000 size bfde0000 type 1 > Adding physical memory region 0x100000-0xbfee0000 > Physical Memory Region from bfee0000 size 1f000 type 3 > Physical Memory Region from bfeff000 size 1000 type 4 > Physical Memory Region from bff00000 size 100000 type 1 > Adding physical memory region 0xbff00000-0xc0000000 > Physical Memory Region from f0000000 size 8000000 type 2 > Physical Memory Region from fec00000 size 10000 type 2 > Physical Memory Region from fee00000 size 1000 type 2 > Physical Memory Region from fffe0000 size 20000 type 2 > Physical Memory Region from 100000000 size 140000000 type 1 > Adding physical memory region 0x100000000-0x240000000 > Got VBE info in multiboot. Current video mode is 16703 > ACPI: RSDP paddr=0xf6a00 > ACPI: RSDP vaddr=0xf6a00 > ACPI: RSDT paddr=0xbfeee733 > ACPI: RSDT vaddr=0xbfeee733 > Warning: Your kernel was not compiled for the current microarchitecture. > Kernel loaded to: start=0x100000 end=0xc1f000 size=0xb1f000 entry=0x100300 > ACPI: RSDT paddr=0xbfeee733 > ACPI: RSDT vaddr=0xbfeee733 > ACPI: FADT paddr=0xbfefef67 > ACPI: FADT vaddr=0xbfefef67 > ACPI: FADT flags=0x21 > ACPI: 0 IOMMUs detected > ACPI: MADT paddr=0xbfeee937 > ACPI: MADT vaddr=0xbfeee937 > ACPI: MADT apic_addr=0xfee00000 > ACPI: MADT flags=0x1 > ACPI: MADT_APIC apic_id=0x0 > ACPI: MADT_APIC apic_id=0x2 > ACPI: MADT_APIC apic_id=0x4 > ACPI: Not recording this APIC, only support 2 > ACPI: MADT_APIC apic_id=0x6 > ACPI: Not recording this APIC, only support 2 > ACPI: MADT_APIC apic_id=0x8 > ACPI: Not recording this APIC, only support 2 > ACPI: MADT_APIC apic_id=0xa > ACPI: Not recording this APIC, only support 2 > ACPI: MADT_APIC apic_id=0xc > ACPI: Not recording this APIC, only support 2 > ACPI: MADT_APIC apic_id=0xe > ACPI: Not recording this APIC, only support 2 > ACPI: MADT_IOAPIC ioapic_id=1 ioapic_addr=0xfec00000 gsib=0 > ACPI: MADT_ISO bus=0 source=0 gsi=2 flags=0x5 > ACPI: 2 CPU(s) detected > ELF-loading userland images from boot modules: > size=0x3fab000 v_entry=0x408828 v_start=0x400000 v_end=0x43ab000 > p_start=0x3822000 p_end=0x77cd000 > Moving loaded userland images to final location: from=0x3822000 to=0xc1f000 > size=0x3fab000 > Starting node #0 with APIC ID 0 > Mapping kernel window is done > Starting node #1 with APIC ID 2 > Booting all finished, dropped to user space > create_object@main.c:673 [Cond failed: err != seL4_NoError] > Failed to find device frame/untyped at paddr = 0xb0000000 > seL4 root server abort()ed > Debug halt syscall from user thread 0xffffff823e027400 "rootserver" > halting... > Kernel entry via Unknown syscall, word: 65 > > Any idea what's wrong? I just want to get one x86 application with cross VM > connectors working.
Hi, The cma34cr* applications can only be used on a cma34cr CPU (https://www.rtd.com/PC104/CM/CMA34CR/CMA34CR.htm) and won't work with VMWare unfortunately. The "minimal" application should work on VMWare as it doesn't have any configuration tied to the emulated platform. Similarly with optiplex9020 and zmq_samples. > > The other x86 applications (optiplex9020, cma34cr_ubuntu, zmq_samples) in > camkes-vm-examples-manifest don't work for other reasons. > _______________________________________________ > Devel mailing list -- devel@sel4.systems > To unsubscribe send an email to devel-leave@sel4.systems _______________________________________________ Devel mailing list -- devel@sel4.systems To unsubscribe send an email to devel-leave@sel4.systems
