users

users@lists.genode.org

3 participants
2344 discussions

Sculpt 26.04 Release Candidates
by Christian Helmuth 22 Apr '26

22 Apr '26

Hello everybody, just now, I published the first alpha image of Sculpt 26.04 under the following URLs. It’s also available via the Sculpt “System → Update” dialog in entry `https://depot.genode.org/chelmuth` from a running Sculpt installation. https://depot.genode.org/chelmuth/image/sculpt-pc-2026-04-17.img.xz https://depot.genode.org/chelmuth/image/sculpt-pc-2026-04-17.zip Note, the image represents an alpha state and comes with shortcomings we're actively working on. For example, the selection of a preset currently deactivates networking, which must be enabled again to download missing depot archives. I will post here when updated candidates were published. Please report any discovered issues and ask questions on the mailing list or our Discourse forum. Happy sculpting! -- Christian Helmuth Genode Labs https://www.genode-labs.com/ · https://genode.org/ https://floss.social/@genode · https://genodians.org/ https://de.linkedin.com/company/genodelabs Genode Labs GmbH · Amtsgericht Dresden · HRB 28424 · Sitz Dresden Geschäftsführer: Dr.-Ing. Norman Feske, Christian Helmuth

1 1

Async Handling of RPC Entrypoints
by Rumen Mitov 08 Apr '26

08 Apr '26

Hi, During FOSDEM, one of the discussions touched on the components' handling of incoming RPC calls. Currently this is done in a synchronous manner because (if I remember correctly) it was simply easier to implement it that way as opposed to handling it asynchronously. What would be some of the challenges in handling this asynchronously? It was mentioned that the RPC mechanism was tightly integrated with the whole codebase, so it would require a large refactor. I am curious to hear your thoughts on how supporting asynchronous RPC calls could impact the following: - preservation of determinism (in the context of formal verification) - would the capability model need to be reworked to support revoking in-flight RPC requests? If so how could a client component signal to the server that it should drop the request? I don't mean to argue for replacing the current model, I'm just interested learning a bit more about the design trade-offs :) Best, Rumen

2 2

Hack'n'Hike in 2026
by Stefan Kalkowski 16 Mar '26

16 Mar '26

Dear Genode community, the registration deadline for our annual Hack'n'Hike event is approaching! During the 24th - 27th of April we'll be in a cozy accommodation in Saxony Switzerland to enjoy outdoor activities and collaborative hacking. It is a small gathering of around 10 to 20 developers and enthusiasts of Genode. The informal character of the Hack'n'Hike presents a great opportunity for newcomers to get in touch with the community. The event is sponsored by Genode Labs. There is no registration fee. For further information please have a look at the corresponding topic either at our issue tracker [1], or forum [2]. For joining the event, please register not later than Tuesday, March 24th by writing to: hacknhike(a)genode-labs.com Best regards Stefan [1] https://github.com/genodelabs/genode/issues/5791 [2] https://genode.discourse.group/t/hacknhike-2026/254/3

1 0

How to execute Tinycore in VM via Sculpt (25.10) - Seoul?
by Parfait Tokponnon 08 Mar '26

08 Mar '26

Parfait Tokponnon <parfait.tkn(a)gmail.com> jeu. 19 févr. 12:20 (il y a 2 jours) À users Hello, I want to install and use TinyCore - Seoul via Sculpt, but regardless of the configuration I select, the “Add component” button never appears to allow me to start the virtual machine. I followed tutorials [0], [1] -> [4]. However, these guides now seem obsolete: several of the settings mentioned no longer correspond to the current state of the system, while new configuration fields have appeared. Given my limited knowledge, I am not sure what values to assign to them. Could you please advise me on the appropriate procedure for the current version of Genode/Sculpt (25.10) so that I can start TinyCore correctly? In addition, I would like to run TinyCore as a virtual machine on Genode/NOVA for everyday use. In Alex-Ab's current repository, there are about thirty variants available. Could you recommend a TinyCore variant that is likely to be long-lasting and can support everyday tasks (browser, sound, image, network, etc.)? Thank you in advance for your help, and have a great day. [0] : https://www.genodians.org/alex-ab/2019-03-06-disposal-browser-vm [1] : https://lists.genode.org/pipermail/users/2019-March/006633.html [2] : https://genodians.org/alex-ab/2023-05-09-seoul-23-04 [3] : https://genodians.org/topics-vbox6 [4] : https://genodians.org/jschlatow/2022-10-27-fresh-vm-on-sculpt -- Parfait T.

2 2

Announcement: Genode OS Framework version 26.02 released
by Norman Feske 26 Feb '26

26 Feb '26

Hello everyone, it's my pleasure to announce that Genode 26.02 has just been released today. https://genode.org/news/genode-os-framework-release-26.02 This release is special to me personally as it switches the framework to our custom configuration format originally sketched more than two years ago, then proposed in December 2024, intensely evaluated over the course of the past 18 months, and eventually finalized during the current release cycle. This transition has been no small feat, and I'm more than happy that we have arrived at our final destination without any unforeseeable disruption. Thanks to everyone who participated! Speaking of transitions, our move from GitHub to Codeberg has proceeded according to the plan laid out on our road map. As detailed by the release documentation linked below, all repositories except for the main repository are now officially hosted at https://codeberg.org/genodelabs/ and the main repository will follow soon. On the technical side, the release features the update of all DDE-Linux-based protocol stacks to kernel version 6.18, which is the foundational work for updating the all the device drivers in May. It also comes with usability improvements of the Goa SDK, the port of Git, revised TCP/IP error handling, and a variety of API-safety improvements. The most prominent topics at a glance: - Human-inclined data (HID) format by default - First half of the migration from GitHub to Codeberg - Linux device-driver environment using kernel version 6.18 - Event-filter support for global key combinations - Ports of Git and FIO benchmark - Goa SDK usability enhancements Please find those topics covered in detail by our release documentation: https://genode.org/documentation/release-notes/26.02 Best regards Norman -- Dr.-Ing. Norman Feske Genode Labs https://www.genode-labs.com · https://genode.org Genode Labs GmbH · Amtsgericht Dresden · HRB 28424 · Sitz Dresden Geschäftsführer: Dr.-Ing. Norman Feske, Christian Helmuth

1 0

How To Add Address Sanitization
by Rumen Mitov 24 Feb '26

24 Feb '26

Hi, In my project I am encountering a segfault when trying to allocate with `Genode::Heap` (GDB output is from base-linux): ``` Thread 19 "ld.lib.so" received signal SIGSEGV, Segmentation fault. [Switching to LWP 13744] 0x0000000050019fc8 in Genode::Allocator_avl_base::Block::find_best_fit (this=0x7ffff43efd78, size=8128, align=3, range=...) at /phantomuserland/genode/repos/base/src/lib/base/allocator_avl.cc:28 28 { ``` According to the backtrace (see backtrace.log, if interested), I suspect the `find_best_fit` method is being called in an infinite loop. I was not able to recreate this SEGFAULT in a fresh Genode project, so the issue must be from my project's code. What's interesting is that the SEGFAULT occurs during a `push %rbx` instruction, so perhaps this is due to stack corruption? I tried adding `-fsanitize=address` to my compile flags, however during `goa build` I get errors stating that the linker cannot find any references to asan symbols (see build.log). I checked, and I have libasan8 installed. Is address sanitization supported in Genode projects? If so, how can I compile my project with it? Best, Rumen

2 2

Migration from GitHub to Codeberg
by Johannes Schlatow 18 Feb '26

18 Feb '26

Hello everyone, as outlined in our road map, we planned the migration of all but the main (genode.git) repository from GitHub to Codeberg for the upcoming 26.02 release. I'm happy to announce that we just completed this migration step. From now on, you'll find all genode-* repositories as well as the Goa repository at https://codeberg.org/genodelabs Along with the git repositories, all issues, pull requests and comments have been migrated as well. The repositories at GitHub have been made read-only and therefore will not receive any updates. In the course of the migration, we have also changed the name of the default branch from "master" to "main". In order to adapt to these changes on your side, we advise you to switch to the current master branch in your clone of https://github.com/genodelabs/genode.git and follow the instructions that are printed by any build command. For Goa, you can trigger the migration with the following commands: goa update-goa master goa versions Note that the migration to Codeberg implies a few more changes for contributors: Contributors must create an account at codeberg.org. It is possible to link the new account to your GitHub account. This enables Codeberg to associate your former comments (entered on GitHub) to your new account on Codeberg (i.e. you may use different user names on both platforms). In case you forked any repository on GitHub you should consider creating a new fork on Codeberg and manually pushing your branches and tags to the new fork to restore the state of the forked repository as it was on GitHub. The following instruction serve as a guideline: git clone --bare https://github.com/<user>/<repo> bare_clone cd bare_clone git branch -m master main git remote set-url origin ssh://git@codeberg.com/<user>/<repo> git push --mirror Codeberg uses Forgejo and has a very similar UI compared to GitHub. However, there are a few changes when it comes to referencing issues and commits. On Github, you are able to push a commit referencing an issue via #<issue-number> to your fork and this commit will be shown in the corresponding issue of the original repository from which you forked. On Codeberg, however, you must explicitly mention the repository where the issue resides via, e.g., genodelabs/goa#<issue-number>. Similarly, if you want to reference a commit from a fork in an issue comment, you must name the fork explicitly, e.g. jschlatow/goa@<commit-hash>. Cheers Johannes

3 2

Trouble Running Vbox on SculptOS
by Rumen Mitov 16 Feb '26

16 Feb '26

Hi, I am trying out SculptOS and I was trying to follow along with the first part of this article: https://genodians.org/jschlatow/2022-10-27-fresh-vm-on-sculpt. I could not find `vm_fs` so I just saved the debian archive into ramfs. I then tried the vbox6 archive from the Genodelabs, however the logs indicated an error. I then tried with cnuke's vbox6 archive. I do not see an error in the logs, however the virtual machine is still not starting in my wm component. There do seem to be some warnings regarding bogus values for '/shared' and '//machin...' (see screenshot). Does this issue have something to do with the file-system configuration, or perhaps the vbox6 component is running out of RAM? Regarding the RAM, the component says it is using 4.059 GiB / 4.199 GiB, so I don't think I am running out. I am stuck on how I can debug this issue, as it seems I am not able to scroll up in the Log window. Best, Rumen P.S. When configuring the vbox6 component I tried setting the file-system to the following (none worked): - ramfs - recallfs - used file system - ramfs/recall/debian-<debian-version> - ramfs/recall/debian-<debian-version>/vm

2 8

Disk encryption
by Mikhail Voronin 05 Feb '26

05 Feb '26

Hello, I am Mikhail Voronin from Innopolis University. I am part of a team working on porting Phantom OS to Genode. As part of our work, we plan to add disk encryption. Could you, please, advise which Genode mechanism we can use for this? Kind Regards, Mikhail Voronin

1 0

Building the toolchain on nixos
by alice.domage＠gapfruit.com 02 Feb '26

02 Feb '26

Dear Genodians, Has anyone already built the toolchain for nixos? and happens to have a `flake.nix` or a `.nix` source file that can build it, I think those are called 'derivation'. I am currently down that rabbit hole, and have the following error: ``` $ ./tool/tool_chain x86 <...> The directory (BUILD_SYSTEM_HEADER_DIR) that should contain system headers does not exist: /usr/include ``` I haven't modified the `tool/tool_chain` tool or patched configure to adjusted standard paths, to point to their respective 'stores' yet. I only have adjusted the shebangs to `#!/usr/bin/env -S ...` where needed. Cheers, alice

3 3

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

users