users March 2024

users@lists.genode.org

13 participants
9 discussions

driver_manager being phased away ? (#5150)
by ttcoder＠netcourrier.com 20 Mar '24

20 Mar '24

Fellow Genodians, regarding ticket 5150 : Consolidation of the driver manager into the sculpt manager ( https://github.com/genodelabs/genode/issues/5150 ) I'm in the process of integrating driver_manager into my h/o/g project, to give it basic dynamic drivers ability (it previously hardcoded Vesa video etc). After peeking at ticket 5150, I looked into sculpt_manager, wondering if I could make a bigger "jump" and migrate directly to that component, but that does not seem compatible with my goals (sculpt_manager embodies much of the SculptOS "feel" and would conflict with my h/o/g goals). So it seems like I'll need to preserve a copy of driver_manager before it is deprecated/retired, make it an (ex)Genode component in the h/o/g repository. Still, thought I'd better post my reasoning here in case someone finds fault with it : from where I stand, that seems to be the natural way to go, and it seems to have few dependancies so I assume the (verbatim "forked") driver_manager will keep working in future Genode releases. I'll just need to mirror changes that occur in Genode when a driver (intel_fb etc) is modified in terms of how it's ran, what arguments are passed to it. Cedric

2 2

Another complex Rust package
by Roman Iten 19 Mar '24

19 Mar '24

Hello Genodians Benjamin Lamowskis great article "A first complex Rust package" [1] and the attention Rust on Genode received recently on this mailing list motivated me to explore the latest achievements regarding Goa and Rust myself :) I went straight down experimenting with Rocket, a web framework for Rust and setup a corresponding Goa project [2]. Compiling the "Hello World" example [3] with Goa was a very pleasing experience and at link stage, only two symbols were missing: kqueue and kevent. I added dummy implementations for both calls [4] (and by the way learned about the compat-libc API). Building succeeds now, but obviously fails at runtime: ``` Genode 24.02 <local changes> 17592186044415 MiB RAM and 18997 caps assigned to init [init -> hello_rocket] Warning: Libc RNG not configured [init -> hello_rocket] Warning: __sys_kqueue: kqueue not implemented [init -> hello_rocket] thread 'main' panicked at /home/wonko/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rocket-0.5.0/src/lib.rs:245:10: [init -> hello_rocket] create tokio runtime: Os { code: 78, kind: Unsupported, message: "Function not implemented" } [init -> hello_rocket] note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace [init -> hello_rocket] Error: raise(ABRT) [init] child "hello_rocket" exited with exit value -1 ``` I'm aware that most certainly, there are other roadblocks ahead. However, I'd like to pursue the topic regarding kqueue()/kevent() a bit more since I assume this might be (or has been) a roadblock for porting other applications or runtimes. - Is it reasonable to add those calls to Genodes libc? - Or can Rust be instructed not to use those calls but select() instead? I stumbled over the MIO flags `mio_unsupported_force_poll_poll` and `mio_unsupported_force_waker_pipe` [5]. But I'm not versed in Rust and setting `mio_unsupported_force_poll_poll` by naively applying the following patch to Goa leads to `error[E0252]: the name `Waker` is defined multiple times`: ``` diff --git a/share/goa/lib/build/cargo.tcl b/share/goa/lib/build/cargo.tcl index 7c0c52b..78e7e26 100644 --- a/share/goa/lib/build/cargo.tcl +++ b/share/goa/lib/build/cargo.tcl @@ -43,6 +43,8 @@ proc build { } { lappend rustflags -C link-arg=$x } + lappend rustflags --cfg mio_unsupported_force_poll_poll + set ::env(RUSTFLAGS) $rustflags set ::env(RUST_STD_FREEBSD_12_ABI) 1 ``` - [1] https://genodians.org/atopia/2023-10-26-a-first-complex-rust-package - [2] https://github.com/rite/goa-projects/tree/hello_rocket - [3] https://rocket.rs/guide/v0.5/getting-started - [4] https://github.com/rite/genode/commit/0219d0543cedd180b082e1ef13dd5d779d7e5… - [5] https://github.com/tokio-rs/mio?tab=readme-ov-file#unsupported-flags -- Roman Iten Gapfruit AG Baarerstrasse 135 CH-6300 Zug roman.iten(a)gapfruit.com

2 1

Questions About VMs and Hardware Access
by Zachary Zollers 19 Mar '24

19 Mar '24

Hello Genodians, The last few days, I have been focused on creating my first Linux VM using Seoul. I am happy to report I was largely successful, but have a few questions after completing the exercise. The answers I get from this list have been very helpful in getting through the initial learning curve, so thank you in advance for your responses. [1] While referencing the example Seoul runscripts in the genode-world repository, I did not see an obvious way to facilitate direct PCI passthrough to a VM. Is this supported by the current version of Seoul? If not, is it supported by the VirtualBox port? [2] Is there a good way to support a situation where only one client needs to display and capture input. For example, in my VM scenario, I only care about the visual output of the VM. I was able to accomplish the desired graphical result by configuring a single nitpicker domain that had the entire screen area and no labels. The only issue here is that the single client does not immediately get input focus (I had to click to be able to type in the VM). Am I on the right track here, or is there a better way? [3] What purpose does the platform driver (os/src/drivers/platform) serve? It appears that device discovery is done by either the ACPI driver or pci_decode (possibly others). Is it responsible for delegating access? I assume access to these is granted through an IO_MEM and/or IO_PORT session, but these seem to be provided by core (not the platform driver). Any clarification here would be helpful. Once again, I appreciate your very helpful responses! Thanks, Zachary Zollers

4 3

Running lighttpd.run
by Pirmin Duss 18 Mar '24

18 Mar '24

Hello Genodians After the update to Genode 24.02 one of our more complex run scripts got stuck when trying to download the test-results from the googletest that it did run before. To narrow down the problem, I tried to run the libports/run/lighttpd.run both on 23.11 and 24.02 releases without any of our patches applied. Unfortunately I can't download index.html on both releases. The output is as follows: !% wget http://10.0.2.55/index.html !--2024-03-18 09:49:24-- http://10.0.2.55/index.html !Connecting to 10.0.2.55:80... failed: No route to host. Now I'm thinking, that my setup for the TAP device might not be correct, and would like to ask, if someone can give me a hint what might be wrong? My distribution is Debian 12, and I currently use the following script, to set up the TAP device (commands taken from libports/run/fetchurl.inc and libports/run/lwip_lx.run): !#!/bin/bash ! !set pipefail -e ! !user=pirmin !netdev=enp1s0 !tapdev=tap0 ! !sudo ip tuntap add dev $tapdev mode tap user $user !sudo ip address flush dev $tapdev !sudo ip address add 10.0.2.1/24 brd 10.0.2.255 dev $tapdev !sudo ip link set dev $tapdev addr 02:00:00:ca:fe:01 !sudo ip link set dev $tapdev up ! !sudo iptables -t nat -A POSTROUTING -o $netdev -j MASQUERADE !sudo iptables -A FORWARD -i tap0 -o $netdev -j ACCEPT !sudo iptables -A FORWARD -i $netdev -o tap0 -m state --state !RELATED,ESTABLISHED -j ACCEPT ! !sudo sysctl -w net.ipv4.ip_forward=1 The output from ip address, regarding the TAP device is as follows: !2: enp1s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000 ! link/ether 58:47:ca:73:7b:fc brd ff:ff:ff:ff:ff:ff ! inet <ip-addr> brd <brd> scope global dynamic noprefixroute enp1s0 ! valid_lft 5956sec preferred_lft 5956sec !6: tap0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000 ! link/ether 02:00:00:ca:fe:01 brd ff:ff:ff:ff:ff:ff ! inet 10.0.2.1/24 brd 10.0.2.255 scope global tap0 ! valid_lft forever preferred_lft forever ! inet6 fe80::ff:feca:fe01/64 scope link ! valid_lft forever preferred_lft forever Regards, Pirmin

2 2

Question about Core's Ability to Delegate Errors
by nsf＠ksu.edu 18 Mar '24

18 Mar '24

Hello Genodians, I was working on a project and noticed that the only kernel fault core allows a component to handle is a page fault. Is there a particular reason that core only allows page faults to be handled and not all kernel faults? If there is a problem with receiving all faults I would love to know the issue! thanks in advance for all your help. Sincerely, Nathan

4 5

Questions about Genode on seL4
by Zachary Zollers 14 Mar '24

14 Mar '24

Hello Genodians, I have been playing around with Genode on seL4 for the last few days and have a couple of questions. [1] Did any modifications need to be made to the seL4 source code for Genode to work properly? [2] I encountered a couple of strange warnings when running the "Hello world" scenario from the Genode foundations book. Below is the clipped console log showing the exact messages. . . . Booting all finished, dropped to user space Warning: device memory in range [0000000400000000,0000000800000000) is unavailable (due to limited untyped cnode range) // To which device is this referring? Warning: device memory in range [0000000800000000,0000001000000000) is unavailable (due to limited untyped cnode range) Warning: device memory in range [0000001000000000,0000002000000000) is unavailable (due to limited untyped cnode range) . . . boot module 'config' (469 bytes) boot module 'init' (456304 bytes) Warning: need physical memory, but Platform object not constructed yet // I'm assuming this is a non-issue, but wanted to check Warning: need physical memory, but Platform object not constructed yet . . . Genode 24.02 183 MiB RAM and 523285 caps assigned to init Warning: void Core::Rpc_cap_factory::free(Genode::Native_capability) not implemented - resources leaked: 0x1 // What are the implications of this? Warning: void Core::Rpc_cap_factory::free(Genode::Native_capability) not implemented - resources leaked: 0x2 Warning: void Core::Rpc_cap_factory::free(Genode::Native_capability) not implemented - resources leaked: 0x4 [init -> hello] Hello world I am not yet familiar (still learning) the internals of seL4 and core, so apologies if these questions have obvious answers. Thanks in advance, Zachary Zollers

2 1

enabling iMX.8M Plus based board
by Alice 14 Mar '24

14 Mar '24

Dear Genodians, I started to work on enabling CompuLab's iot-gate-imx8mplus [1]. As the name suggests, this device is based on the i.MX8MP SoC. So far, I have the following things currently working: - u-boot - Linux (6.1) - run/log on top of base-hw This line of work is available on GitHub [2]. I still want to replace the manufacturer's defconfig with tinyconfig, and reduce the size of the Linux kernel. I keep this task for later. Next, I want to draw attention to my work regarding the FEC network driver, eMMC storage, and the USB-host drivers based on the source of the Linux 6.1 port. If someone is already working on these drivers, we could join efforts. [1] https://www.compulab.com/products/iot-gateways/iot-gate-imx8plus-industrial… [2] https://github.com/a-dmg/genode-imx/tree/imx8mp_iot_gate Cheers, Alice

1 0

Mailing List Migration on Thursday, February 8, 2024
by Christian Helmuth 12 Mar '24

12 Mar '24

Hello Genodians, after thorough planning, we finally migrate this mailing list to Mailman 3. Consequently, the list will not be operational tomorrow Thursday, February 8, 2024, all day All current list subscribers stay subscribed and will receive list postings latest starting Friday. Other changes coming with Mailman 3 are as follows. - Registration URL for new list members https://lists.genode.org/mailman3/postorius/lists/users@lists.genode.org - Account Management URL https://lists.genode.org/mailman3/accounts/login/ - Mailing list archive https://lists.genode.org/mailman3/hyperkitty/list/users@lists.genode.org The old archive at https://lists.genode.org/pipermail/users/ will be frozen and preserved. All previous and future postings are available in the new archive. See you on Friday after the migration -- Christian Helmuth Genode Labs https://www.genode-labs.com/ · https://genode.org/ https://floss.social/@genode · https://genodians.org/ Genode Labs GmbH · Amtsgericht Dresden · HRB 28424 · Sitz Dresden Geschäftsführer: Dr.-Ing. Norman Feske, Christian Helmuth

1 2

Sculpt 23.10 .ova file broken with VMware Workstation 17.5.1
by Justin Clift 01 Mar '24

01 Mar '24

Hiyas, Trying out Sculpt 23.10 in VMware Workstation (17.5.1) today, and found some initial hurdles that seem like they should get fixed. :) When looking at options on the Sculpt download page: https://genode.org/download/sculpt ... it seems like a choice of either a .img file, or a .ova file. --- Problem 1: The .img file doesn't seem to work with VMware Workstation, as it just shows "GRUB" (in the top left) like its partially loading... then just hangs there. --- Problem 2: Trying the .OVA file instead (File -> Open -> choose the .ova file), the import process throws up a warning message that the .ova "did not pass OVF specification conformance". (screenshot attached) That warning can be ignored though, in which case VMware keeps going for a few seconds then throws a hard error about "Capacity mismatch for disk2.vmdk". (screenshot for this attached as well) --- It looks like the .ova file format is just a renamed .tar file though. So untarring it works, revealing two VMware disk images (.vmdk). Manually creating a new VM (2 cpu cores, 2GB ram) and assigning those disks to it gets things working. --- Problem 3: VMware doesn't seem totally happy with those disk images. In disk info window (after importing) the "Current Size" for the disk is 16,777,216 TB. Very much not correct. ;) It's also reporting the same figure for "System Free" (also very much not correct), which seems like a VMware bug to me. (screenshot attached too) The field instead has the correct "System Free" value when I check the disks of other VMs on my system. --- Anyway, I thought the above might be useful to mention in case someone wants to look into them. Regards and best wishes, Justin Clift

2 3

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

users March 2024