users January 2023

users@lists.genode.org

27 participants
49 discussions

Re: Roadmap 2023
by Sam Crow 06 Jan '23

06 Jan '23

------ Original message------From: Sam Crow Date: Thu, Dec 29, 2022 10:42 AMTo: users(a)lists.genode.org;Cc: Subject:Re: Roadmap 2023 Hello Genodians,I'd like to reiterate the mobile emphasis without tracking features. My spare SSD is occupied by Haiku release1 beta4 and I see little chance of that being evicted in favor of another desktop OS. My PinePhone would be a much better target, however. I bought it specifically to see how secure a mobile platform could be! Genode was one of the mobile targets I was hoping to try.My primary SSD on my desktop (a 3rd-gen i7), my laptop (a PineBook Pro) and my PinePhone (3GB RAM, 32GB internal storage) are presently all running Manjaro Linux. If I could evict Manjaro from all 3 places, that would be a good year for me. Despite liking the desktop experience, Manjaro has no privacy features that I'm aware of. Microkernels that keep every driver in user-mode and don't allow drivers to "call home" to their manufacturer or their manufacturer's government would be an ideal privacy feature. Binary blobs should be disallowed from such behavior.Finally, I foresee an involvement with WebAssembly to be a replacement for most binary blobs in a short period of time and as soon as that takes place, address sanitizers and other sandboxing technologies could be complimentary to the AGPL license strategy. I have already submitted some patches to the W2C2 project on GitHub at https://github.com/turbolent/w2c2 and would like to hear your thoughts on the subject of using bytecodes to sandbox drivers and other binary blobs.Note: presently drivers cannot be represented in the WASI standard APIs so another API variant will be needed. There is a discussion started on the subject at https://github.com/WebAssembly/WASI/discussions/501#discussioncomment-41887… if interested.Thanks for your time and efforts,Samuel D. Crow

3 3

RK3588 part X small success.
by Michael Grunditz 05 Jan '23

05 Jan '23

When started in EL1. I assume I need to copy the settings from the setup of EL1 to EL2 or something.. I still would like a proper cpu init ( really bad so I might go ahead with it). kernel initialized ROM modules: ROM: [0000000005580000,0000000005580156) config ROM: [000000000048a000,000000000048b000) core_log ROM: [0000000005634000,000000000567b5f8) init ROM: [0000000005588000,00000000056335f8) ld.lib.so ROM: [0000000000488000,0000000000489000) platform_info ROM: [0000000005581000,0000000005587260) test-log Genode 22.11 125 MiB RAM and 64533 caps assigned to init [init -> test-log] hex range: [0e00,1680) [init -> test-log] empty hex range: [0abc0000,0abc0000) (empty!) [init -> test-log] hex range to limit: [f8,ff] [init -> test-log] invalid hex range: [f8,08) (overflow!) [init -> test-log] negative hex char: 0xfe [init -> test-log] positive hex char: 0x02 [init -> test-log] floating point: 1.70 [init -> test-log] multiarg string: "parent -> child.7" [init -> test-log] String(Hex(3)): 0x3 [init -> test-log] Very long messages: [init -> test-log -> log] 1..................................................................................2 [init -> test-log] 3.........................................................................................4 [init -> test-log] 5.........................................................................................6 [init -> test-log] [init -> test-log] Test done.

2 3

arm_64 exception vector and el2 stack
by Michael Grunditz 04 Jan '23

04 Jan '23

Hi Where does Genode/base-hw write the exception vector to the address that hypervisor_exception_vector reports it? It doesn't work. If I leave out the vbar setting I get exceptions from uboot if I do something stupid. If not , nothing. But of course, I might be wrong it is just that I would expect exceptions. For example: When I by mistake put NR_OF_CPUS inconsistently., I get nothing if vbar set, if not, trigger assert. Not sure how this relates (seems odd ) but I think that it is a hint. The el2_stack seems like a very high address. Thanks, Michael

2 5

Re: Roadmap 2023
by Colin Parker 04 Jan '23

04 Jan '23

Hello Genodians, Last year was a good year in Genode for me. I poke around with it at the hobby level, but this year I saw the drivers system substantially re-worked and I was able to successfully port a Linux driver. > What directions are you most excited about? Although many others are excited about Sculpt on phones and SOC/SBC scenarios, I remain excited about the prospect of improving Sculpt on “conventional” machines like laptops and (mini)towers. My thoughts on where things could be: 1) The default Sculpt image can probably be made to boot already on almost any x86 system. A few tweaks could help such as allowing command-line arguments from the boot loader to boot in “safe” mode, forcing fallback to the boot loader’s frame buffer. 2) The default Sculpt configuration is great and provides a low barrier to new users to at least try Sculpt. But to work seriously in Sculpt one wants to install a VM, which is many steps, and to virtualize and already-installed OS is even more steps. It would be fantastic if one could, out-of-the box, virtualize an installed OS. If that’s too much, it might be worth curating USB stick images with pre-installed VM partitions. > > Which topics do you deem as interesting to explore yourself? I might poke around with (2) above, at least trying to follow the existing instructions. I may also try to port some more Linux drivers. I’m curious where Sculpt will go with that - will it be towards live selection of drivers at boot time, like in most Linux distros, or is the idea for lean purpose-built images that contain only the drivers necessarily for a given system? Happy new year to all!

3 3

VMM ARM examples: Issues.
by Sid Agrawal 04 Jan '23

04 Jan '23

Hi, I am attempting to run the *vmm_arm run scripts* and am running into a few issues. I am running this on Ubuntu 22.04 with x86_64. The scenario I am trying is to run a with the *hw kernel with arm_v8a arch.* First Issue: '*src/libc' not found - unable to guess version* *Steps:* *git clone ...* *cd genode-dir* *tool/create_builddir arm_v8a* *# Add additional repos in the build.conf file.* *cd build* *make KERNEL=hw BOARD=virt_qemu_arm_v8a* *make KERNEL=hw BOARD=virt_qemu_arm_v8a run/vmm_arm* # Returns the following errors: including /home/siagraw/genode-hw/tool/run/power_on/qemu including /home/siagraw/genode-hw/tool/run/log/qemu including /home/siagraw/genode-hw/tool/run/boot_dir/hw including /home/siagraw/genode-hw/repos/os/run/vmm_arm.run Error: recipe for 'src/libc' not found - unable to guess version make: *** [Makefile:431: run/vmm_arm] Error 1 So, I removed the libc line from vmm_arm.run, as per the diff below: *diff --git a/repos/os/run/vmm_arm.run b/repos/os/run/vmm_arm.run* index d80052352..a4ec448ab 100644 --- a/repos/os/run/vmm_arm.run +++ b/repos/os/run/vmm_arm.run @@ -16,7 +16,6 @@ if { ![have_board imx7d_sabre] && ![have_board imx8q_evk] && create_boot_directory t import_from_depot [depot_user]/src/[base_src] \ [depot_user]/src/init \ - [depot_user]/src/libc \ [depot_user]/src/log_terminal \ [depot_user]/src/nic_router \ [depot_user]/src/terminal_crosslink \ After that, the VM boots up as below. Second Issue: *Failing mount command and no interactive shell.* [...] [init -> vm] [ 6.227743] NET: Registered PF_PACKET protocol family [init -> vm] [ 6.233521] Key type dns_resolver registered [init -> vm] [ 6.249367] Loading compiled-in X.509 certificates [init -> vm] [ 6.310832] Sending DHCP requests ., OK [init -> vm] [ 6.361405] IP-Config: Got DHCP answer from 10.0.1.1, my address is 10.0.1.2 [init -> vm] [ 6.372772] IP-Config: Complete: [init -> vm] [ 6.378516] device=eth0, hwaddr=02:02:02:02:04:05, ipaddr=10.0.1.2, mask=255.255.255.0, gw=10.0.1.1 [init -> vm] [ 6.387958] host=10.0.1.2, domain=, nis-domain=(none) [init -> vm] [ 6.394173] bootserver=10.0.1.1, rootserver=10.0.1.1, rootpath= [init -> vm] [ 6.394275] nameserver0=10.0.1.1 [init -> vm] [ 6.441325] Freeing unused kernel memory: 1152K [init -> vm] [ 6.458228] Run /bin/sh as init process [init -> vm] /bin/sh: can't access tty; job control turned off [init -> vm] / # mount /dev/vda /root; cp -r /etc /root; ls /root/etc; umount /root [init -> vm] mount: mounting /dev/vda on /root failed: No such file or directory <--- This seems to failing as there is nothing inside /dev in the VM. I tried an "ls" in my run script and that showed that /dev is empty. [init -> vm] fstab init.d resolv.conf Run script execution successful. I have a few questions here: - Was it ok to remove the libc line from the run script? - I was expecting the VM to hang around with a shell. Is that not the expected behavior? - I should be able to run this scenario of a rpi3, right? Instead of running inside Qemu(where I have effectively 2 level of virtualization from the point of the VM). Best, Sid

2 1

u-boot requirements for genode
by Michael Grunditz 03 Jan '23

03 Jan '23

Hello I would like to know the requirements from u-boot in order to properly start genode. I know you are using bootm command, but that doesn't work at all with rockchip boards. Not sure if it is rockchip specific, but bootm will in the end try to switch to el2 which will surely fail in my case, since it's already there. It also requires dt blob and or atags, if not there - hang. I have tried to drop to el1 from uboot and with genode image as EP. That works a bit better then just jumping to it from el2. But strange things happens. No output from Genode can be seen. I can output characters to uart , but the uart driver or something in between fails. I have tested with adding a crash the last thing it does in enable_mmu , and I get that crash. My guess is that it actually starts, but not sure. One thing that struck me was that it looked a bit like a serial communication error, like a baud rate issue. rockchip insists on running a silly high baud rate. So the first question is what I want to know,, the requirements. I have no problems with adjusting things . Best regards, Michael

3 3

Sculpt OS - A Truly Alternative OS blog post
by Will Senn 03 Jan '23

03 Jan '23

OK. I've wrapped up my week with Sculpt OS by writing up a using sculpt article for posterity, etc, and so on :). Lemme know if you find fault with it. It covers much of the same ground as the getting started tutorial in the docs, just in a different way. Thanks for introducing me to such an amazing effort. I'll be exploring more of the OS in the coming days and look forward to learning more from y'all. Here's the link: https://decuser.github.io/operating-systems/genode/sculpt/2022/12/30/sculpt… Will

2 2

Properly shutting down
by Will Senn 03 Jan '23

03 Jan '23

OK. I give up. After watching videos and reading reams of documentation, I'm not able to get Sculpt to shutdown. I can get it to reset - via: vim config/managed/system <system state="reset"/> which takes effect as soon as I write the file but the corollary: <system state="poweroff"/> doesn't appear to have any effect in either virtual box or the t430. What I've been doing in the meantime, is the reset and then powering off during the reboot. help. Will

4 5

Some questions on bare metal readiness
by Sid Agrawal 03 Jan '23

03 Jan '23

Hi Genodians, I got introduced to Genode as a viable userspace for seL4. But having looked at the code and the abstraction provided by the "core", I feel like I do not really case much about whether I am running sel4 under the hood or not. I plan to use Genode for my research and to that affect, I would like to understand whether I will be able to boot it on the hardware that is available to me and what components of the sw stack will work out of the box. The things which attract me to Genode the most is the components based architecture and the notion of higher level capabilities like: PD, RM etc. Below, I have listed some of things I am looking for. Followed up by understanding of the answers to those questions. If Norman or someone else can clear these up for me, it would be very helpfu. *I would like your opinion on the best combination of Genode+Kernel+arch, which would meet the following requirements:* - It can be booted on real hardware. FWIW I only have access to the following: - Intel x86_64-based PC - Raspberry Pi 4. - Raspberry Pi 3 (can be purchased) - The Toradex Aster carrier board with the iMX8X - Has some drivers that work on bare metal, with some run examples. - Network Driver: I think this exists only for PC, - SD card Driver: I think this exists for both PC and rspi3 - Any other driver will also do, like a USB driver or something. - Has a VMM based on VM_Session, which will also boot on real hardware - I really liked the vmm_arm(full-fledged) and vmm_x86(toy VM guest) examples - The hardware can be flashed and booted with new images easily. I am thinking tftp, usb - Quick dev can be done on Qemu. *Based on my read of the code, the top three contenders are:* - Nova + x86_64: - This will probably give me the best driver support. As it is the version which ships with sculpt and hence most widely tested. - vmm_x86 will give a trivial VMM example - VirtualBox will give me a full-fledged VMM example - Base-HW: I really the idea of not having a separate microkernel, as the base-hw's abstraction seems like the right level to me. So, if I base my work off this kernel, that would be best. - ARM_v8 - Looks like this will boot on rpi3, Is that correct? - I am not sure if there will be networking support - x86_64 - I am not sure if this boot on x86 - Or has the same driver support for networking Thanks again. Sid Grad Student University of British Columbia

1 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

users January 2023