Hi Amit,

It appears that some part of your configuration tries to use 8192 sized Dataport regions. The tutorial assumes 4096 sized regions. What happens when you try and run the solution version? Calling the following from the top level directory will create a new camkes-vm-crossvm tutorial checkout but with a finished revision of the tutorial: ./init --tut camkes-vm-crossvm --solution

This one should correctly boot. I saw the following when I just ran it: ``` [ 0.791550] ip (679) used greatest stack depth: 6696 bytes left OK Device "dataport" found with major number 247

Creating dataport node /dev/camkes_data Allocating 4096 bytes for /dev/camkes_data Creating consuming event node /dev/camkes_done_printing Creating emitting event node /dev/camkes_do_print

Welcome to Buildroot buildroot login: [ 2.361712] random: fast init done

Welcome to Buildroot buildroot login: root Password: # print_client hello world [ 22.825969] dataport received mmap for minor 1 hello world # ```

Kind regards, Kent. ________________________________________ From: Devel devel-bounces@sel4.systems on behalf of Amit Goyal amitgoyal@cse.iitb.ac.in Sent: Thursday, December 13, 2018 7:01 PM To: devel@sel4.systems Subject: Re: [seL4] Camkes Cross-VM Communication

Hi,

Can someone please provide a possible solution?

-- Thanks and Regards, Amit Goyal

On 2018-12-08 06:36, Amit Goyal wrote:

Hi All,

I am using Ubuntu 16.04 on 64 Bit, i7 machine and running Camkes Cross-VM communication tutorial available at: https://docs.sel4.systems/Tutorials/camkes-vm-crossvm.html

I am able to build the system properly but when I run the system, I get the following error:

---

Creating dataport node /dev/camkes_reverse_src Creating dataport node /dev/camkes_reverse_dest Allocating 8192 bytes for /dev/camkes_reverse_src dataport_map_guest@cross_vm_dataport.c:25 Dataport guest size and host size are different (8192 and 4096) dataport_vmcall_handler@cross_vm_dataport.c:75 Failed to map dataport into guest VM_FATAL_ERROR ::: vmexit handler return error vmm_print_guest_context:27 | ================== GUEST OS CONTEXT ================= vmm_print_guest_context:30 | exit info : reason 0x12 qualification 0x0 instruction len 0x3 interrupt info 0x0 interrupt error 0x0 vmm_print_guest_context:32 | guest physical 0x0 rflags 0x286 vmm_print_guest_context:34 | guest interruptibility 0x0 control entry 0x34 vmm_print_guest_context:37 | eip 0xd881714a vmm_print_guest_context:39 | eax 0x 1 ebx 0x 1 ecx 0x 1 vmm_print_guest_context:41 | edx 0x16a42000 esi 0x 2000 edi 0x 10 vmm_print_guest_context:43 | ebp 0xd6b17f0c vmm_print_guest_context:45 | cr0 0x80050033 cr3 0x16b1e000 cr4 0x2680

---

I tried troubleshooting it a bit and changed the file:

~/camkes_vm_com/projects/vm-linux/camkes-linux-artifacts/camkes-linux-init-scripts/buildroot_init/camkes_init as follows:

Earlier: dataport_init /dev/camkes_reverse_src 8192 /dev/camkes_reverse_dest 8192 Changed: dataport_init /dev/camkes_reverse_src 4096 /dev/camkes_reverse_dest 4096

But this also does not work.

Please suggest.

_______________________________________________ Devel mailing list Devel@sel4.systems https://sel4.systems/lists/listinfo/devel