users September 2023

users@lists.genode.org

11 participants
5 discussions

Beginner questions: Seoul, Rust, DDE, and system composition
by Zachary Zollers 26 Oct '23

26 Oct '23

Hi all, My name is Zach. I am a student at Kansas State University doing research with Dr. Eugene Vasserman (Cc). I have been lurking in the mailing list for some time now and I thought I'd introduce myself and ask a couple of "beginner questions" that I have after reading the Foundations book and playing with Sculpt. [1] Is Seoul still viable for virtualization on Genode? If so, where can I find the documentation for writing a VM configuration? I am partial to Seoul over VirtualBox due to its smaller codebase. I checked the genode-world repository and the original (outdated) source repository, but was unable to find anything. [2] What is the state of rust support for Genode? I have seen a few mentions of it in release notes. Can I make base API calls from rust (e.g., requesting sessions, creating child components, etc.), or is it similar to running applications with the POSIX compatibility layer? [3] Which system calls are provided by the Linux driver environment? Is it viable for running arbitrary Linux applications/services (e.g., a container runtime)? [4] What is the best way to determine the dependencies of a component? How does the Sculpt visual composition system determine which sessions are required? When trying to run a complex component (e.g., a VMM) I often find myself doing a lot of trial and error with including libraries and starting necessary dependencies in the run script. Is there a better, or more consistent, way to determine dependencies? Apologies if any of these questions have obvious answers. If this is the case, I would appreciate a pointer to relevant documentation so I can investigate further. Thanks in advance, Zach

5 5

Virtualvox6 and two raw partitions
by Pirmin Duss 27 Sep '23

27 Sep '23

Hello Genodians I'm do want to sculptify my fleet of devices. For that reason I'm currently trying to run Virtualbox6 with two raw partitions. Because of the sizes of disks, the partitions are located on different disks. I'm using the vbox6-block package archive from alex-ab for my tests on sculpt 23.04. To simplify tinkering around and resetting the changes I created a local copy of the package archive. If I disable the second disk, I can run the virtual machine without problems. When I start the VM with the second disk enabled the following error is printed: [runtime -> work -> vbox] Warning: pthread_attr_setstacksize: requested stack size is 1048576 limiting to 1032192 [runtime -> work -> vbox] Warning: pthread_attr_setstacksize: requested stack size is 1048576 limiting to 1032192 [runtime -> work -> vbox] Error: ioctl operation=33 [runtime -> work -> vbox] Error: void ioctl(SUPCALLVMMR0&) called (/home/alex/genode/sculpt.t460p/depot/alex-ab/src/vbox6/2023-04-26/src/virtualbox6/sup.cc:668), not implemented, eip=0x1a74c77 I have connected the second Block session of the VM to a part_block for the second disk, which I start with the following launcher: <launcher pkg="trimpim/pkg/part_block/2023-04-25"> <config> <policy label="1" partition="1" writeable="yes"/> </config> <route> <service name="Block"> <parent label="ahci-2"/> </service> </route> </launcher> Does someone have an idea what I could change to prevent the error? Regards, Pirmin

2 2

debugging VFS plugins with monitor
by Duss Pirmin 27 Sep '23

27 Sep '23

Hello Genodians I really like the new monitor component, it is really easy to use. For a first real world application, I'm trying to debug why run/vfs_tresor_init fails after the update of openssl. For this I changed the run script so that I can run it on QEMU. I can connect to the monitor as described in run/monitor_gdb. What doesn't work with run/vfs_tresor_init is stopping the program execution at break-points. As this works in run/monitor_gdb I assume, that I have overlooked something in my configuration. To automate startup of gdb I created the following /data/genode/build/x86_64/debug/.gdbinit: ! set non-stop on ! set style enabled on ! ! set solib-search-path /data/genode/build/x86_64/debug/ ! set debug-file-directory /data/genode/build/x86_64/debug/ ! ! # connect to monitor running inside QEMU ! target extended-remote localhost:5555 ! ! # add libraries/binary as needed (for symbols) ! add-symbol-file ld.lib.so 0x30000 ! add-symbol-file libc.lib.so 0x10d43000 ! add-symbol-file libcrypto.lib.so 0x1038000 ! add-symbol-file vfs.lib.so 0x10f5c000 ! add-symbol-file vfs_jitterentropy.lib.so 0x10f51000 ! add-symbol-file vfs_tresor_trust_anchor.lib.so 0x10f26000 ! ! add-symbol-file vfs ! ! #set breakpoints ! b /data/genode/repos/os/src/server/vfs/main.cc:1000 ! b /data/genode/repos/gems/src/lib/vfs/tresor_trust_anchor/vfs.cc:2022 ! ! # select the first component that is monitored ! inferior 1 The addresses for the libraries I took from the ld_verbose output of a previous run. I execute gdb as follows: ! cd /data/genode/build/x86_64/debug ! /usr/local/genode/tool/23.05/bin/genode-x86-gdb ld.lib.so When I run info breakpoints I get the following output: ! 1 breakpoint keep y <PENDING> /data/.../vfs/main.cc:1000 ! 2 breakpoint keep y <PENDING> /data/.../vfs.cc:2022 With run/monitor_gdb, it reports an address instead of <PENDING>. Does anybody have an idea what I'm doing wrong? Or is there a limitation I'm not aware of? Regards Pirmin

2 3

Mounting iso filesystem using rump fails
by Radu Aron 25 Sep '23

25 Sep '23

Hello, I am looking into booting a virtualbox VM using an external .iso. In order to do that I am currently working on a simple setup where I just have the necessary drivers and the VFS. I am trying to see if everything is working using "fs-query" but I get an error in the <rump> node saying "Mounting 'cd9660' file system failed (22)". I also tried the same setup with a "vfs" node instead of "fs-query", having the same error. I know the configuration contains a lot of redundant information but I am still learning. :) Looking forward if anyone has any advice on how to fix this. Thank you! This is my run file. "test.iso" is a tinycore installer. ################################################## assert_spec x86_64 set use_overlay 0 set use_serial 1 set use_top 0 create_boot_directory set depot_archives { } lappend depot_archives [depot_user]/pkg/[drivers_interactive_pkg] lappend depot_archives [depot_user]/pkg/themed_wm lappend depot_archives [depot_user]/src/[base_src] lappend depot_archives [depot_user]/src/clipboard lappend depot_archives [depot_user]/src/init lappend depot_archives [depot_user]/src/jpeg lappend depot_archives [depot_user]/src/libc lappend depot_archives [depot_user]/src/nitpicker lappend depot_archives [depot_user]/src/report_rom lappend depot_archives [depot_user]/src/vfs_import lappend depot_archives [depot_user]/src/part_block lappend depot_archives [depot_user]/src/vfs_pipe lappend depot_archives [depot_user]/src/vfs_oss lappend depot_archives [depot_user]/src/mesa lappend depot_archives [depot_user]/src/expat lappend depot_archives [depot_user]/src/libdrm lappend depot_archives [depot_user]/src/libyuv lappend depot_archives [depot_user]/src/vfs_gpu lappend depot_archives [depot_user]/src/ipxe_nic_drv lappend depot_archives [depot_user]/src/nic_router import_from_depot $depot_archives set build_components { virtualbox6 drivers/ahci server/vfs_block app/rom_logger server/vfs server/fs_rom lib/vfs_rump server/dynamic_rom app/fs_query server/part_block } lappend_if [expr $use_top] build_components app/top lappend_if [expr $use_serial] build_components server/log_terminal lappend_if [have_spec x86] build_components drivers/rtc lappend build_components drivers/audio build $build_components set config { <config prio_levels="4" verbose="yes"> <parent-provides> <service name="ROM"/> <service name="IRQ"/> <service name="IO_MEM"/> <service name="IO_PORT"/> <service name="PD"/> <service name="RM"/> <service name="CPU"/> <service name="LOG"/> <service name="VM"/> </parent-provides> <default-route> <any-service> <parent/> <any-child/> </any-service> </default-route> <default caps="100"/> <start name="timer" priority="0"> <resource name="RAM" quantum="1M"/> <provides> <service name="Timer"/> </provides> </start>} append config { <start name="platform_reports"> <binary name="report_rom"/> <resource name="RAM" quantum="1M"/> <provides> <service name="Report"/> <service name="ROM"/> </provides> <config> <policy label="pci_decode -> system" report="acpi_drv -> acpi"/> <policy label="platform_drv -> devices" report="pci_decode -> devices"/> </config> </start> <start name="acpi_drv" caps="350"> <resource name="RAM" quantum="4M"/> <route> <service name="Report"> <child name="platform_reports"/> </service> <any-service> <parent/> <any-child/> </any-service> </route> </start> <start name="pci_decode" caps="350"> <resource name="RAM" quantum="2M"/> <route> <service name="ROM" label="system"> <child name="platform_reports"/> </service> <service name="Report"> <child name="platform_reports"/> </service> <any-service> <parent/> <any-child/> </any-service> </route> </start> <start name="platform_drv" caps="400" managing_system="yes"> <resource name="RAM" quantum="4M"/> <provides> <service name="Platform"/> </provides> <config> <policy label_prefix="ahci_drv" info="yes"> <pci class="AHCI"/> </policy> </config> <route> <service name="ROM" label="devices"> <child name="platform_reports"/> </service> <any-service> <parent/> <any-child/> </any-service> </route> </start> <start name="ahci_report_rom"> <binary name="report_rom"/> <resource name="RAM" quantum="1M"/> <provides> <service name="Report"/> <service name="ROM"/> </provides> <config verbose="yes"/> </start> <start name="ahci_drv" > <resource name="RAM" quantum="10M"/> <provides> <service name="Block"/> </provides> <config atapi="yes"> <report ports="yes"/> <policy label_prefix="fs_query" device="1" writeable="no"/> </config> <route> <service name="Report"> <child name="ahci_report_rom"/> </service> <any-service> <parent/> <any-child/> </any-service> </route> </start> <start name="fs_query_report_rom"> <binary name="report_rom"/> <resource name="RAM" quantum="1M"/> <provides> <service name="Report"/> <service name="ROM"/> </provides> <config verbose="yes"/> </start> <start name="fs_query" caps="120" > <resource name="RAM" quantum="400M"/> <config> <vfs> <rump fs="cd9660" ram="300M" writeable="no"/> </vfs> <query path="/" content="yes"/> </config> <route> <service name="Block"> <child name="ahci_drv"/> </service> <service name="Report"> <child name="fs_query_report_rom"/> </service> <any-service> <parent/> <any-child/> </any-service> </route> </start> </config>} install_config $config set boot_modules { rtc_drv virtualbox6 libc.lib.so vfs.lib.so libm.lib.so libiconv.lib.so stdcxx.lib.so qemu-usb.lib.so virtualbox6-shaderlib.lib.so vfs_rump.lib.so vfs part_block fs_rom fb_drv.config virtualbox6.vbox rump.lib.so rump_fs.lib.so rom_logger dynamic_rom fs_query } # platform-specific modules lappend_if [expr $use_top] boot_modules top append_if [expr $use_serial] boot_modules { log_terminal } append_if [expr $use_overlay] boot_modules { overlay.vdi } lappend boot_modules pci_audio_drv lappend boot_modules ahci_drv lappend boot_modules vfs_block lappend boot_modules nic_router lappend boot_modules ipxe_nic_drv build_boot_image $boot_modules append qemu_args " -m 6500 -cpu host " append qemu_args " -device ahci,id=ahci " append qemu_args " -drive id=cd1,file=bin/test.iso,if=none,media=cdrom -device ide-cd,drive=cd1,bus=ahci.1 " run_genode_until forever ################################################## And this is the output received: ################################################## Genode 23.05 <local changes> 6356 MiB RAM and 63253 caps assigned to init [init] parent provides [init] service "ROM" [init] service "IRQ" [init] service "IO_MEM" [init] service "IO_PORT" [init] service "PD" [init] service "RM" [init] service "CPU" [init] service "LOG" [init] service "VM" [init] child "timer" [init] RAM quota: 776K [init] cap quota: 66 [init] ELF binary: timer [init] priority: 0 [init] provides service Timer [init] child "platform_reports" [init] RAM quota: 776K [init] cap quota: 66 [init] ELF binary: report_rom [init] priority: 0 [init] provides service Report [init] provides service ROM [init] child "acpi_drv" [init] RAM quota: 3848K [init] cap quota: 316 [init] ELF binary: acpi_drv [init] priority: 0 [init] child "pci_decode" [init] RAM quota: 1800K [init] cap quota: 316 [init] ELF binary: pci_decode [init] priority: 0 [init] child "platform_drv" [init] RAM quota: 3848K [init] cap quota: 366 [init] ELF binary: platform_drv [init] priority: 0 [init] provides service Platform [init] child "ahci_report_rom" [init] RAM quota: 776K [init] cap quota: 66 [init] ELF binary: report_rom [init] priority: 0 [init] provides service Report [init] provides service ROM [init] child "ahci_drv" [init] RAM quota: 9992K [init] cap quota: 66 [init] ELF binary: ahci_drv [init] priority: 0 [init] provides service Block [init] child "fs_query_report_rom" [init] RAM quota: 776K [init] cap quota: 66 [init] ELF binary: report_rom [init] priority: 0 [init] provides service Report [init] provides service ROM [init] child "fs_query" [init] RAM quota: 409352K [init] cap quota: 86 [init] ELF binary: fs_query [init] priority: 0 [init] child "timer" announces service "Timer" [init] child "platform_reports" announces service "Report" [init] child "platform_reports" announces service "ROM" [init -> acpi_drv] Found MADT [init -> acpi_drv] MADT IRQ 0 -> GSI 2 flags: 0 [init -> acpi_drv] MADT IRQ 5 -> GSI 5 flags: 13 [init -> acpi_drv] MADT IRQ 9 -> GSI 9 flags: 13 [init -> acpi_drv] MADT IRQ 10 -> GSI 10 flags: 13 [init -> acpi_drv] MADT IRQ 11 -> GSI 11 flags: 13 [init -> acpi_drv] Found MCFG [init -> acpi_drv] MCFG BASE 0xb0000000 seg 0x0 bus 0x0-0xff [init] child "ahci_report_rom" announces service "Report" [init] child "ahci_report_rom" announces service "ROM" [init -> ahci_drv] --- Starting AHCI driver --- [init] child "fs_query_report_rom" announces service "Report" [init] child "fs_query_report_rom" announces service "ROM" [init] child "platform_drv" announces service "Platform" [init -> acpi_drv] RSDT OEM 'BOCHS ', table id 'BXPC ', revision 1, creator 'BXPC' (1) [init -> acpi_drv] SMBIOS 3 table (entry point: 0x1559b0 structures: 0xf59d0) [init -> ahci_drv] version: major=0x1 minor=0x0 [init -> ahci_drv] command slots: 32 [init -> ahci_drv] native command queuing: yes [init -> ahci_drv] 64-bit support: yes [init -> ahci_drv] number of ports: 6 [init -> ahci_drv] Warning: CMD.ST bit set during device reset --> unknown behavior [init -> ahci_drv] #0: ATAPI [init -> ahci_drv] Warning: CMD.ST bit set during device reset --> unknown behavior [init -> ahci_drv] #1: ATAPI [init -> ahci_drv] #2: off (unknown device signature) [init -> ahci_drv] #3: off (unknown device signature) [init -> ahci_drv] #4: off (unknown device signature) [init -> ahci_drv] #5: off (unknown device signature) [init -> ahci_report_rom] report 'ahci_drv -> ports' [init -> ahci_report_rom] <ports> [init -> ahci_report_rom] <port num="0" type="ATAPI" block_count="11414" block_size="2048"/> [init -> ahci_report_rom] <port num="1" type="ATAPI" block_count="126976" block_size="2048"/> [init -> ahci_report_rom] </ports> [init] child "ahci_drv" announces service "Block" [init -> fs_query] Error: Mounting 'cd9660' file system failed (22) [init -> fs_query] Error: failed to create <rump> VFS node [init -> fs_query] Error: fs="cd9660" [init -> fs_query] Error: ram="300M" [init -> fs_query] Error: writeable="no" no RM attachment (READ pf_addr=0x0 pf_ip=0x100f1e9 from pager_object: pd='init -> fs_query' thread='ep') page fault, pd='init -> fs_query' thread='ep' cpu=0 ip=0x100f1e9 address=0x0 stack pointer=0x401fe3d0 qualifiers=0x4 irUwp reason=1 ##################################################

2 1

Re: Trying to understand how capabilities are implemented
by Albin Otterhäll 05 Sep '23

05 Sep '23

Hi Martin! Sorry for the late reply, toke some time to get a mail client up and running with my mail provider. Didn't want to send a reply using their web client. On 8/21/23 11:24, Martin Stein wrote: > On 19.08.23 03:35, Albin Otterhäll wrote: >> 1. The RPC object A is created inside the protection domain 1, which >> result in the object identity A being created by the kernel. >> >> 2. A has a name, which is a natural number. >> Q1: Is the RPC object's name the value of a class variable of type >> int? > > In short: Yes, you can consider it a simple integer that is known to > both the kernel and the affected user-land program. The name references > this object only within this one program (respectively protection domain). > > Just in case you're interested in some code background: > > In header [1] you can find the classes Rpc_object and Rpc_entrypoint - a > thread that is used for handling RPCs on RPC objects. An RPC object > initially comes without a capability (the objects name), but a > capability is created and returned when linking the object via > Rpc_entrypoint::manage to an entrypoint. At this point the object > becomes ready to be called from outside the program. > > As you can see in header [2], Capability has no members but inherits > from Untyped_capability, AKA Native_capability, which contains a pointer > _data. Now, this is where it becomes platform-specific. However, a very > simple case is the "base-hw" kernel. There, the _data pointer itself (as > long value) is used as local name of the object [4]. This long value is > the name that is registered in the domain's cap space inside the kernel > for that particular RPC object. Thanks for the code references and the explanation! >> 3. Protection domain 1 has a capability space insied the kernel. >> Q2: Is the protection domain seperate from the capability space in >> the kernel, and they're "connected" with some map somewhere? > > In general, this is very kernel-specific. However, I know the internals > only for the "base-hw" kernel. In this kernel, the cap space is not > separate from its protection domain. Each domain object [5] contains a > tree _cap_tree of all RPC object names known to this domain (see [6] for > more details). Okey! Didn't know that it could be different between the different kernels. Thought that they were abstracted out, but apparently not. :) >> Q3: Is the capability space a map between natural numbers and some >> form of address to the object identity? I.e. the map work similar to a >> set of OO references, there the keys are variable names; and the >> values are the memory addresses of object identities. > > Again very kernel-specific and, again, my knowledge about "base-hw": In > this kernel your depiction is very accurate. Each RPC object name is an > Object_identity_reference in the kernel and contains a pointer > Object_identity *_identity. Thanks for confirming! >> Q4: If the answer to Q3 is yes, does that mean that delegagion is >> some form of mechanism to share the adress of the object identity with >> other protection domains? > > If I understand you correctly, yes and no. To the user it looks like > sharing an address in OO but you might better think of it as sharing the > _ability_ to access the object. In contrast to address sharing, > delegation creates a new local name/reference for the object identity in > the target domain/cap space. In my domain the object might be referenced > by the name "3" while in a domain I have delegated to, the object might > be referenced by the name "987". However, even if delegation would > result in the same name "3", the link between this name and the object > is unique to the target domain as is that between my "3" and the object. > This is well illustrated by § 3.1 Figure 3 in the book. Is there a semantic difference between "sharing an address" and "sharing the ability to access the object"? I've looked at base/include/base/rpc_server.h and base/include/base/capability.h, but I couldn't see any parts about delegation (I don't have any experience with C++, so it's possible I've missed something obvious). > I hope that was helpful!? It was very helpful! Thank you! -- Albin Otterhäll

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

users September 2023