l4-hackers

l4-hackers@os.inf.tu-dresden.de

2 participants
2880 discussions

Linux console?
by Richard Clark 14 Apr '25

14 Apr '25

L4Re, I’ve been working with the examples and tweaking them for AMD64 (QEMU), and I’ve managed to get linux up and booting, reading the ramdisk, and even spawning a login process which kicks off /bin/sh and displays a # prompt. And that’s great, but that’s all it does. I can’t get any input to it. That’s using the device hvc0. Of course uvmm complains that there is no virtual console and warns that it might not work, so the software is at least not surprised! 😊 But when I try to use the device ttyS0, linux stops printing even before the login process tries to run. I don’t get any errors, but also no output. And I can’t seem to run the IO server because then linux won’t load at all (something about out-of-memory). I’m sure I’m missing some little piece of magic somewhere, but I can’t find any working examples. None of them have active logins (I had to add my own iniittab to the ramdisk). A little help connecting the cons service to my linux so I can get a real bash shell? Or running IO and connecting through that? Thank you in advance! Richard _______________________________________________ l4-hackers mailing list -- l4-hackers(a)os.inf.tu-dresden.de To unsubscribe send an email to l4-hackers-leave(a)os.inf.tu-dresden.de

2 1

Loading L4 after Uboot on ZynqMP
by mkravchik＠hotmail.com 10 Apr '25

10 Apr '25

Hello, I'm trying to run L4 on a Xilinx ZyncMP board. The board runs Uboot from ROM and then I tried to load L4 as described in https://l4re.org/bsp/zynqmp.html. However, loading a uimage fails, I'm getting an error: ZynqMP> fatload usb 0:1 0x0ffffc0 bootstrap_hello.uimage ZynqMP> bootm 0x0ffffc0 ## Booting kernel from Legacy Image at 00ffffc0 ... Image Name: L4 Image #8 Created: 2025-03-31 14:14:32 UTC Image Type: AArch64 Linux Kernel Image (uncompressed) Data Size: 1530680 Bytes = 1.5 MiB Load Address: 01000000 Entry Point: 01000000 Verifying Checksum ... OK XIP Kernel Image FDT and ATAGS support not compiled in ### ERROR ### Please RESET the board ### I tried to use rawimage, but there I get to the following problem: ZynqMP> fatload usb 0:1 0x1000000 bootstrap_hello-cfg.rawimage 2149176 bytes read in 151 ms (13.6 MiB/s) ZynqMP> go 0x1000000 ## S� L4 Bootstrapper Build: #15 Thu Apr 3 11:39:37 IDT 2025, 9.4.0 Scanning up to 2048 MB RAM, starting at offset 32MB Memory size is 2048MB (00000000 - 7fffffff) RAM: 0000000000000000 - 000000007fffffff: 2097152kB Total RAM: 2048MB Scanning fiasco -serial_esc Scanning sigma0 Scanning moe rom/hello.cfg Compressed modules: cannot decompress at 0x10a8000, try 0x11bc000 Uncompressing modules (modaddr = 0x11bc000 (backwards)): mod06: 0x126c000-0x1296b38: hello mod05: 0x126b000-0x126b080: hello.cfg mod04: 0x11e1000-0x126a118: ned mod03: 0x11bc000-0x11e0c40: l4re Loading fiasco found node 0 kernel info page (via ELF) at 0x3000 L4Re is configured for EL2 mode (virtualization / hypervisor) but got started in EL1 by the boot-loader. Please change your boot-loader to start L4Re in EL2 mode. I'm not sure how to proceed from here. The Uboot is loaded from the board's ROM and is running at EL2. Any help is appreciated, Moshe _______________________________________________ l4-hackers mailing list -- l4-hackers(a)os.inf.tu-dresden.de To unsubscribe send an email to l4-hackers-leave(a)os.inf.tu-dresden.de

3 5

L4re RAM/Flash usage and scheduling timing Info
by Eric Miniere via l4-hackers 28 Mar '25

28 Mar '25

Hello Everyone, I am looking for an estimate of the memory footprint to run the hypervisor L4RE on a quad Core ARM Cortex R52. Does it run directly from flash or it needs to be copied to run in RAM ? same question for Guests OS (ie FreeRtos)? What could be the minimal needed L4RE footprint for code and data ? Also if someone could share a rough idea of scheduling time for an ARM R52 running at 400Mhz ? or nb of cycle it takes to schedule ? Thanks _______________________________________________ l4-hackers mailing list -- l4-hackers(a)os.inf.tu-dresden.de To unsubscribe send an email to l4-hackers-leave(a)os.inf.tu-dresden.de

2 3

Trouble booting L4Re on PC hardware?
by Richard Clark 14 Mar '25

14 Mar '25

Hi! I've had much success building and running my applications in QEMU. No issues there. But now I've got myself some real hardware. Windows boots on it. Debian Linux boots on it. Linux even boots from the USB I create with rufus. No problems there. What I would like to do, is to take the system.iso image that normally runs under QEMU (x86_64), burn that to my USB stick (same way I put linux boot on there), and then boot the USB stick. The hardware will boot from the USB, and the image copy to the USB appears to work, since I've done that and booted linux. But I cannot seem to get the system.iso file to boot. I've tried UEFI boot, Classic boot, copy as UEFI image, and copy as DD image. It seems to ignore the USB drive and (by default) boot windows from the NVME drive. The device has no serial port. Just an HDMI screen with USB mouse and keyboard. It does have ethernet ports and I could try that, but it doesn't appear that the UEFI bios supports TFTP. How do I take my QEMU work and boot it on a real PC? Thanks! Richard _______________________________________________ l4-hackers mailing list -- l4-hackers(a)os.inf.tu-dresden.de To unsubscribe send an email to l4-hackers-leave(a)os.inf.tu-dresden.de

3 2

How to L4Re on the S32G
by qiang xu 27 Feb '25

27 Feb '25

*Hello L4Re experts,* I would like to know how to run L4Re on the S32G. I couldn’t find any related documentation. I’m a beginner in this technical field, so could you provide friendly step-by-step instructions? Regards, Qiang _______________________________________________ l4-hackers mailing list -- l4-hackers(a)os.inf.tu-dresden.de To unsubscribe send an email to l4-hackers-leave(a)os.inf.tu-dresden.de

4 25

saving configuration to version control
by Baruch Burstein 09 Feb '25

09 Feb '25

Hello. After running `make config`, I am trying to save my configuration to git and later restore it. This is for both fiasco and l4. I found that the command `make savedefconfig` works (just like for linux kernel) to create a defconfig file for uploading to git, but the command `make defconfig` for restoring the configuration from this file doesn't work. What file should I be saving/restoring, or what is the process to save/restore my configuration? Either a defconfig or a full configuration would be ok. Thank you _______________________________________________ l4-hackers mailing list -- l4-hackers(a)os.inf.tu-dresden.de To unsubscribe send an email to l4-hackers-leave(a)os.inf.tu-dresden.de

2 2

Use HW random generator to kaslr-seed dtb on uvmm
by Flavio Erlich 04 Feb '25

04 Feb '25

Hi, According to Linux documentation, if I want to use kASLR I should add on my device tree, on the chosen node a kaslr-seed entry ( https://www.kernel.org/doc/Documentation/devicetree/bindings/chosen.txt). I'm running uvmm and I want to use the dt-modify argument to change the value on dtb to a value that comes from an HW random generator at runtime. I have written an application which reads a random sequence from the HW. How can I pass the random value from that application and pass the u64 value to the ned script which I can use as a seed? I can use the application exit code to read 32-bit and run it twice, but seems to be overkill to do that. I was thinking of sending a newer allocatted Dataspace to the application, it will fill it with random data, but I have no idea if it is possible to read this Dataspace and concatenate the result to the arguments to uvmm. Do you have any other suggestions? Thanks for your help, Flavio _______________________________________________ l4-hackers mailing list -- l4-hackers(a)os.inf.tu-dresden.de To unsubscribe send an email to l4-hackers-leave(a)os.inf.tu-dresden.de

2 2

USB on L4RE
by Flavio Erlich 25 Jan '25

25 Jan '25

I found this thesis defence post. https://tu-dresden.de/ing/informatik/sya/professur-fuer-betriebssysteme/die… Does anyone know if or where the code is available? Is the thesis paper available? Thanks, Flavio _______________________________________________ l4-hackers mailing list -- l4-hackers(a)os.inf.tu-dresden.de To unsubscribe send an email to l4-hackers-leave(a)os.inf.tu-dresden.de

3 2

emmc-driver imx8mp
by Alvaro Gallardo 08 Jan '25

08 Jan '25

Dear L4Re experts, I hope you are doing well and enjoying this time of the year. I would like to ask for your help or insights on how to use the emmc-driver in an imx8mp based board. In this platform, the usdhc nodes are located out of the pci bus, and they require an i2c device to work, as well as gpio and clocks. I am able to start the emmc server, which identifies one usdhc device and starts the server loop. I pass a virtual bus to the emmc driver with all required devices, as they usually work in the Virtual Machine to access the mmc. The driver scans all of them, finding the usdhc node. But, everything stops when I create a client, either using a dynamic way with: create(0, "device=...","ds-max=5); or declaring the client in the argument as: "emmc-drv -v --client cl1 --device=... --ds-max=5". For the second way, it stops when the Virtual Machine starts to configure the related virtio device (I am using a virtio_net node). I will be grateful if you can give me some information about the issue or some of the following questions: 1. how should the node in the device tree of the Virtual Machine be configured to work with the emmc client? 2. is it possible that the board's specific hardware configuration required for the mmc is stopping the emmc client to work? 3. Is there any way to test the driver before linking it to a virtual machine? I found an example with the "virtio-block-chksum-sync" module, but I could not find this module. I attach the configuration files, the output text and the base device tree structure. Thank you in advance for your attention. Kind regards, Alvaro Gallardo _______________________________________________ l4-hackers mailing list -- l4-hackers(a)os.inf.tu-dresden.de To unsubscribe send an email to l4-hackers-leave(a)os.inf.tu-dresden.de

2 2

Network failure when high traffic
by Mohamed Dawod 05 Dec '24

05 Dec '24

Hello, I created a new L4 setup with uvmm module and Linux kernel running on it. I added also virtio-net-device and created new tap devices to be able to communicate with the VM from outside of L4. The setup was done successfully and I could ping from my host machine to the Linux VM and vise versa. The problem appeared when I accelerated the ping using -i option : Ping 192.168.7.2 -i 0.01 It continue pings for a few minutes then it gives (Destination Host Unreachable)! I used the wrapper function vmm.start_virtio_switch() in me demo. Why did this issue happen ? And how can I fix it? Thanks, Mohamed _______________________________________________ l4-hackers mailing list -- l4-hackers(a)os.inf.tu-dresden.de To unsubscribe send an email to l4-hackers-leave(a)os.inf.tu-dresden.de

2 1

Video Error Reasons?
by Lonnie Cumberland via l4-hackers 27 Nov '24

27 Nov '24

Hello All, I have been experimenting with L4Re and was able to compile the latest snapshot that seems to work well for almost all of the examples in QEMU from the "make qemu" menu which is a very good start, I think. Lately, I have also used the "make grub2iso" which gives me the same menu of examples as the "make qemu" but for which it will generate an ISO of the example. I generated ISO's for all of the examples and tested them on 3 different x64 computer systems which are all Intel with 2 being NUC's and 1 being a Dell XPS 8950 but when I boot any of the generated L4Re ISO's, it seems to boot all of the core modules but then gets to an error message that seems to be related to the video mode. ------------------------------------------- error: no suitable video mode found ------------------------------------------- And then the screen shows a bunch of lines. I have been looking around though the L4Re code in the snapshot release, but I do not yet have a clue where how to change things so that these ISO's will boot completely on some hardware although things seem to boot up in QEMU. I am thinking that there might just be some setting somewhere that I need to adjust, or something. Any thoughts, suggestions, or ideas would be greatly appreciated. Have a great evening, Lonnie _______________________________________________ l4-hackers mailing list -- l4-hackers(a)os.inf.tu-dresden.de To unsubscribe send an email to l4-hackers-leave(a)os.inf.tu-dresden.de

4 4

CPU Virtualization in L4
by Mohamed Dawod 25 Nov '24

25 Nov '24

I know that Scheduling proxy in L4 is used to set cores and priority ranges for a dedicated task. For example, The below scheduling proxy makes the task runs on cores 1,2,3 with priority range [52,62]. scheduler = vmm.new_sched(0x50, 0xE) When I switch to debugging mode, I see that this task has priority = 52 in pr column! So why does scheduling proxy set priority range instead of a single value like Linux ? How does L4 use the priority range ? My second question is about the relationship between physical CPUs and virtual CPUs in L4. I know that CPU virtualization should give the ability to virtualize the available physical CPUs so that if we have single physical CPU core, CPU virtualization enables us to provide multiple virtual CPU cores for the VMs running ontop of the hypervisor. Actually I don't see this behaviour in the scheduling proxy in L4! instead, the cores parameter only takes a bitmap of the physical cores. Can I use the scheduling proxy or any other method/workarround to provide CPU Virtualization ? Thanks, Mohamed Dawod _______________________________________________ l4-hackers mailing list -- l4-hackers(a)os.inf.tu-dresden.de To unsubscribe send an email to l4-hackers-leave(a)os.inf.tu-dresden.de

2 1

Porting apps to L4Re?
by Lonnie via l4-hackers 18 Nov '24

18 Nov '24

Hello All, As part of the project effort that I am working on with L4Re, I am considering 2 possible pathways of which both need graphics capabilities to interact with the uvmm for a guest OS: Possible pathways: 1. Use the framebuffer "spectrum" example and port something like FreeRDP, rdesktop or other, so that this will allow for a loabable RDP service VM whose only job is to connect to other VM's. This would be for having a Docker/Podman Container engine running and to be able to connect to a container via a web browser VM that has a graphic console in fullscreen mode. 2. Find a way to have L4Re be able to access the graphic console (VGA) of each uvmm guest directly and then be able to HotKey switch between active VM's. This might be like having multiple guest OS's running (i.e. Ubuntu 24.04 and Windows 10 for example) and then be able to switch the console between them. This is also an idea to allow L4Re to boot all of the OS's that might reside on a dualboot or multiboot system. I actually need something this is really a cross between both of these since in one configuration case will be (1) and in another case will be (2). Wanted to get any thoughts or suggestions that you might have towards this. Thanks and have a great day, Lonnie _______________________________________________ l4-hackers mailing list -- l4-hackers(a)os.inf.tu-dresden.de To unsubscribe send an email to l4-hackers-leave(a)os.inf.tu-dresden.de

3 2

Generating EFI files
by Lonnie Cumberland 13 Nov '24

13 Nov '24

Hello All, While exploring and testing L4Re, I have also been testing some files from the AMD64 downloads: https://l4re.org/download/snapshots/pre-built-images/amd64/ While currently the only the elf32 file do run a bit and the efi files are now known to have some problems, I was wondering how the efi files were generated. I know that in the build for l4re that you can use "make -j24" to build the core as well as "make qemu" to show some available examples that I am trying to also get to work, but I was wondering how these above "pre-built-images" were generated? Also, I am very interested in the "l4re_vm-multi.efi" and "l4re_vm-multi-p2p.efi" in how they can be generated to run under QEMU as well as how to perhaps generate an x64 ISO that can be booted on real hardware. These interest me a great deal and I would really be interested if someone might be able to explain them more to me, especially the "p2p" one since have an interest in p2p networks as well. Thanks in advance and have a great day, Lonnie _______________________________________________ l4-hackers mailing list -- l4-hackers(a)os.inf.tu-dresden.de To unsubscribe send an email to l4-hackers-leave(a)os.inf.tu-dresden.de

3 4

vm-basic-pci demo testing
by Mohamed Dawod 13 Nov '24

13 Nov '24

Hi, I was trying the *vm-basic-pci* demo from l4Re version 24.08.0. The demo works and I could boot the Linux VM and login successfully, but I need to test the passed PCI bus to make sure that it works. I'm trying to test it using a *virtio-blk-pci* device from qemu which is expected to be mounted as a block device in */dev/vda*. but when I found no */dev/vda* file in the filesystem. Please find attached : * my ned scripts : vm-basic-pci.log * arm-virt64.io * the dts file : virt-basic_virt-64_pci.dts * and the full logs : vm-basic-pci.log Thanks in advance, Regards -- Mohamed Dawod *Software Engineer, *Avelabs Egypt *Cell Phone : (+20) 1117311726* -- *Driving Innovation! Visit our website www.avelabs.com <http://www.avelabs.com/>*, to read Avelabs Confidentiality Notice, follow this link: http://www.avelabs.com/email/disclaimer.html <http://www.avelabs.com/email/disclaimer.html> _______________________________________________ l4-hackers mailing list -- l4-hackers(a)os.inf.tu-dresden.de To unsubscribe send an email to l4-hackers-leave(a)os.inf.tu-dresden.de

5 7

Debugging memory allocation in L4Re
by Paul Boddie 11 Nov '24

11 Nov '24

Hello, I thought I might as well ask this since the mailing list has been somewhat active recently. I have been testing some of my software, but after a certain period of time, I experience errors of the following form: l4re_kernel: ERROR: more-mem(1000): Cannot provide more memory. l4re_kernel: ERROR: mmap() called: unimplemented! size=100000 As far as I can tell, uclibc_morecore and mmap in... pkg/l4re-core/l4re_kernel/server/src/mem.cc ...are respectively responsible for these errors, the former being called by __malloc_trim, itself called by free in... pkg/l4re-core/uclibc/lib/contrib/uclibc/libc/stdlib/malloc-standard/free.c Looking at the uclibc_morecore implementation, it seems that the "program break" is defined only once, with a dataspace of 64 pages being allocated, and any subsequent sbrk call will not cause this allocated space to be extended further. Have I understood this situation correctly? As always, I assume that I am making some kind of mistake, in this case probably not deallocating memory when I should be and thus exhausting the available space. Are there any convenient ways of monitoring memory allocation in L4Re? Thanks for any advice offered! Paul _______________________________________________ l4-hackers mailing list -- l4-hackers(a)os.inf.tu-dresden.de To unsubscribe send an email to l4-hackers-leave(a)os.inf.tu-dresden.de

2 2

Qemu Demos
by Lonnie Cumberland 11 Nov '24

11 Nov '24

Hello All, I am on an Intel NUC 13 NHNE (x64) running Ubuntu 23.10 and am working my way through the basic Qemu Demos after following the build instructions https://github.com/kernkonzept/manifest/wiki/BUILDING From there I am in the "~/l4re/build-amd64$" and have added "/l4re/l4/conf/examples" to the "l4/conf/Makeconf.boot" Now I do a "make qemu" and get the list: =============================================== │ │ │ 0 hello │ │ 1 hello-cfg │ │ 2 hello-2 │ │ 3 hello-shared │ │ 4 framebuffer-example │ │ 5 L4Linux-basic │ │ 6 L4Linux-mag │ │ 7 VM-basic │ │ 8 VM-multi │ │ 9 VM-multi-p2p │ │ 10 VM-basic-pci =============================================== For which I have been able to run items 0 - 3, but when I run (4) "framebuffer-example", I get an error about a missing "x86-lagacy.devs" file and I cannot find it anywhere in the sources or builds. =============================================== Could not find 'x86-legacy.devs' within paths /home/lonnie/l4re/build-amd64/assets /home/lonnie/l4re/build-amd64/bin/amd64_gen/l4f /home/lonnie/l4re/build-amd64/bin/amd64_gen/plain /home/lonnie/l4re/build-amd64/lib/amd64_gen/std/l4f /home/lonnie/l4re/build-amd64/lib/amd64_gen/std/plain /home/lonnie/l4re/build-fiasco-amd64 /home/lonnie/l4re/l4/conf/examples make[1]: *** [Makefile:693: qemu] Error 1 make[1]: Leaving directory '/home/lonnie/l4re/l4' make: *** [Makefile:6: do-all-make-goals] Error 2 =============================================== I then restarted "make qemu" and tried (7) VM-basic, but it seems to abort with the messages: =============================================== MOE: Starting: rom/ned rom/vm-basic.cfg MOE: loading 'rom/ned' Ned says: Hi World! Ned: loading file: 'rom/vm-basic.cfg' VMM[]: Created VCPU 0 @ 18000 VMM[]: >>> CAUTION: Support for AMD SVM is experimental, use at your own risk! <<< terminate called after throwing an instance of 'N2L413Runtime_errorE' what: Invalid request: SVM does not support next_rip save. Aborting! =============================================== In trying to run the other VM-????? choices, I also get similar messages: =============================================== vm-1 | VMM[]: Created VCPU 0 @ 18000 vm-1 | VMM[]: >>> CAUTION: Support for AMD SVM is experimental, use at your own risk! <<< vm-1 | terminate called after throwing an instance of 'N2L413Runtime_errorE' vm-2 | VMM[]: Created VCPU 0 @ 18000 vm-2 | VMM[]: >>> CAUTION: Support for AMD SVM is experimental, use at your own risk! <<< vm-3 | VMM[]: Created VCPU 0 @ 18000 vm-3 | VMM[]: >>> CAUTION: Support for AMD SVM is experimental, use at your own risk! <<< vm-2 | terminate called after throwing an instance of 'N2L413Runtime_errorE' vm-1 | what: Invalid request: SVM does not support next_rip save. Aborting! vm-3 | terminate called after throwing an instance of 'N2L413Runtime_errorE' vm-1 | vm-2 | what: Invalid request: SVM does not support next_rip save. Aborting! vm-2 | vm-3 | what: Invalid request: SVM does not support next_rip save. Aborting! vm-3 | ========================================================= Has anyone been able to get all of these to run? I am still exploring but would like to get the be able to compile and run the VM-multi examples on the x64 hardware like in the video. https://l4re.org/cast-multi-vm-qemu.html Any thoughts on how to test out some of these? Best and have a great weekend, Lonnie _______________________________________________ l4-hackers mailing list -- l4-hackers(a)os.inf.tu-dresden.de To unsubscribe send an email to l4-hackers-leave(a)os.inf.tu-dresden.de

3 2

Building Screenshots and examples
by Lonnie Cumberland 10 Nov '24

10 Nov '24

Hello All, I hope that your day is going well. Recently, I have decided to explore L4Re as a microhypervisor and capabilities as a possible minimalist component-based microkernel OS. I have just set up Ubuntu 23.10 (x64) in an Intel NUC13 and would am reviewing as much documentation as I can find as well as am building the core L4Re according to the Github Wiki just to see how the process goes. https://github.com/kernkonzept/manifest/wiki/BUILDING As I am in the learning curve at the moment, I also would like to build some examples such as the "Screenshots" (https://l4re.org/screens.html) and demos from the Pre-Built section (https://l4re.org/download/snapshots/pre-built-images/amd64/). I did try to follow the direction on the pre-built sections and grabbed the "l4image" and all of the AMD64 EFI files to try and test, but when I launch them they just seem to hang and do nothing. I do have qemu (x64) installed as well, but still nothing seems to boot. What I would like to ask the mailinglist members is where can I get the source code to the "screenshots" examples as well as the AMD64 "pre-built" examples noted above so that I cam do a fresh compile to see them in action? Any help would be greatly appreciated. Thanks in advance and have a great day, Lonnie _______________________________________________ l4-hackers mailing list -- l4-hackers(a)os.inf.tu-dresden.de To unsubscribe send an email to l4-hackers-leave(a)os.inf.tu-dresden.de

4 8

Multiple CPU support for uvmm on virt-arm64 qemu machine
by Mohamed Dawod 06 Nov '24

06 Nov '24

Hello, I'm trying to provide multiple CPUs for a linux VM on top of L4. I'm using the qemu virt machine and building for aarch64. so I used *-smp* option to provide more CPUs. > $ qemu-system-aarch64 -M virt,virtualization=true -cpu cortex-a57 -smp 4 > -m 1024 -kernel ....etc.... Unfortunately, This didn't work. I tried to add more CPU device nodes to the dts file *virt-arm_virt-64.dts *but it also didn't work. I think that it's because of the provided interrupt-controller with *virt-arm_virt-64.dts* in *l4/pkg/uvmm/conf/dts* which mentioned that it supports only one CPU. > icsoc { > compatible = "simple-bus"; > #address-cells = <2>; > #size-cells = <2>; > ranges; > > /* Uvmm will adapt the compatible string depending on the present > gic > * version. It expects reg entries that provide enough space for > the > * Cpu/Dist interface for gicv2 (at least 0x1000, 0x1000) or the > * Dist/Redist interface for gicv3 (0x10000, 0x20000 * number of > cpus). > * > *The entries provided here support any gicv2 setup or a gicv3 setup > * with one Cpu.* > */ > gic: interrupt-controller { > compatible = "arm,gic-400", "arm,cortex-a15-gic", > "arm,cortex-a9-gic"; > #interrupt-cells = <3>; > #address-cells = <0>; > interrupt-controller; > reg = <0 0x40000 0 0x10000>, > <0 0x50000 0 0x20000>; > }; > }; > My question now, is there any workaround to support multiple CPUs for virt machine on arm64 ? Thanks, Regards -- Mohamed Dawod *Software Engineer, *Cairo Egypt -- *Driving Innovation! Visit our website www.avelabs.com <http://www.avelabs.com/>*, to read Avelabs Confidentiality Notice, follow this link: http://www.avelabs.com/email/disclaimer.html <http://www.avelabs.com/email/disclaimer.html> _______________________________________________ l4-hackers mailing list -- l4-hackers(a)os.inf.tu-dresden.de To unsubscribe send an email to l4-hackers-leave(a)os.inf.tu-dresden.de

2 9

[FOSDEM 2025] Call for Participation: Microkernel and Component-Based OS Devroom
by Udo Steinberg 30 Oct '24

30 Oct '24

Hi all, below is the official CfP for the microkernel devroom at FOSDEM 2025. I am looking forward to a strong participation from all microkernel/unikernel research groups and companies, not only in the form of attendance, but also in the form of great talks :) Cheers, Udo We are happy to announce the CfP for the "Microkernel and Component-Based OS" devroom at the upcoming FOSDEM 2025. Developers and users of various free and open-source microkernel-based, unikernel-based and component-based operating systems will meet again at FOSDEM (https://fosdem.org) during the weekend of February 1/2, 2025 and will share a developer room. The microkernel and component-based OS devroom is currently looking for your participation in the form of proposals for talks, demos and other related activities. Possible topics for the devroom include, but are not limited to: * introduction of a specific OS or framework * design of subsystems and the general architecture of an OS * languages, tools and toolchains used * enabling support for hardware architectures, devices and programming languages * development processes, debugging * maintenance, testing and release engineering * safety, security and robustness * trends and challenges * research and open questions * community and governance * use cases, experiences and status updates * best practices and lessons learned * live demos Important Dates The deadline for submitting proposals is December 1, 2024 (23:55 CET). Please use the FOSDEM website at https://fosdem.org/submit, select the track "Microkernel and Component-Based OS" and include at least the following information: * title of your proposal * short abstract (one or two paragraphs) * duration (20 - 40 minutes, including demos and Q&A) * your full name * your short bio The devroom schedule (with accepted talks) will be announced on the devroom website at https://fosdem.org/2025/schedule/track/microkernel by December 15, 2024. The schedule will also be posted to the devroom mailing list and the speakers will be notified via email. Like previous years, the devroom will take place as an in-person event at the ULB Campus Solbosch in Brussels, Belgium during the second half of February 1, 2025 (Saturday). Due to the high number of submissions that FOSDEM received this year, our devroom has only been allocated half a day. Therefore, the final decision on the duration of the talks will be made by the devroom organizers based on the number of accepted proposals. Requirements The communication language of the devroom is English. All content must relate to free and open-source software. By participating in the event, you agree to the publication of your talk recordings, slides and other content provided under the same CC-BY license as all other FOSDEM content. All participants are expected to adhere to the Code of Conduct: https://fosdem.org/2025/practical/conduct/ Contact For the 2025 edition, the organizers of the devroom are * Udo Steinberg (udo [at] hypervisor.org) * Alexander van der Grinten (alexander.vandergrinten [at] gmail.com) For any comments, questions and suggestions, please do not hesitate to contact us directly or via microkernel-devroom-manager(a)fosdem.org. About the Devroom Since the first Microkernel OS Devroom at FOSDEM 2012, this devroom has been a part of each subsequent FOSDEM (with slight variations of the name). The focus gradually widened to include component-based, unikernel-based and other operating systems. It has now become a somewhat institutionalized tradition for the open-source operating systems community, a kind of "extended family meeting" and it is one of the places where microkernel and unikernel enthusiasts meet regularly. To date, over two dozen projects have participated in one way or another. Many of the projects face similar challenges but come up with partially different solutions. Therefore, the goal of the devroom is to bring the various projects together, let them exchange ideas, cross-pollinate and socialize. As in the past, the devroom will offer the stage both to established community members and to newcomers. Our goal is to select talks in an inclusive manner and to create a balanced and unbiased schedule, while keeping the quality of the devroom as high as in previous years. About FOSDEM FOSDEM is a two-day conference organized by volunteers to promote the widespread use of free and open-source software. FOSDEM is widely recognized as one of the largest and best such events worldwide. FOSDEM covers a wide spectrum of free and open-source software and hardware projects and offers a platform for people to collaborate. To this end, FOSDEM has set up developer rooms (devrooms) where teams can meet and showcase their projects. Devrooms are a place for teams to discuss, hack and publicly present new ideas, latest results, lightning talks, news and proposals. Besides developer rooms, FOSDEM also offers main tracks, lightning talks, certification exams and project stands. In recent years, FOSDEM has been hosting more than 8000 developers annually at the ULB Solbosch Campus in Brussels, Belgium. The participation in FOSDEM is totally free and requires no registration, although the organizers gratefully accept donations and sponsorship. Devroom Dinner Over the years, it has become a tradition that devroom speakers and enthusiasts meet for dinner somewhere in Brussels on Saturday evening to continue discussions, socialize and meet old and new friends. We plan to follow that tradition in 2025 and will inform you about the exact arrangements later. Hope to see all of you in Brussels! _______________________________________________ l4-hackers mailing list -- l4-hackers(a)os.inf.tu-dresden.de To unsubscribe send an email to l4-hackers-leave(a)os.inf.tu-dresden.de

1 0

vm-basic-pci demo is not working for arm64
by Mohamed Dawod 29 Oct '24

29 Oct '24

Hi, I was trying to run the L4 demo *vm-basic-pci* for *arm64* using the command $ make qemu E=vm-basic-pci but It didn't work because of the missing 2 files : * virt-arm_virt-64_pci.dtb : which is requested by the *modules.list* file in the line : > module[arch=arm64,fname=virt-pci.dtb] dtb/virt-arm_virt-64_pci.dtb * virt-pci.dtbo : which is requested by the *vm-basic-pci.cfg* by the configuration > if (L4.Info.arch() == "arm64") then > dt = "-drom/.fdt" > overlay = "*-drom/virt-pci.dtbo*" > else > dt = "-drom/virt-pci.dtb" > overlay = "" > end I searched for both files in the whole *l4re-snapshot-23.10.1* directory but I couldn't find them Where can I find those necessary files to run *vm-basic-pc*i demo? Thanks in advance, Regards -- Mohamed Dawod *Software Engineer,* Cairo Egypt -- *Driving Innovation! Visit our website www.avelabs.com <http://www.avelabs.com/>*, to read Avelabs Confidentiality Notice, follow this link: http://www.avelabs.com/email/disclaimer.html <http://www.avelabs.com/email/disclaimer.html> _______________________________________________ l4-hackers mailing list -- l4-hackers(a)os.inf.tu-dresden.de To unsubscribe send an email to l4-hackers-leave(a)os.inf.tu-dresden.de

3 11

PCIe handling in virt arm64
by Mohamed Dawod 20 Oct '24

20 Oct '24

Hello, I need to pass through the PCIe bus to Linux VM via io and uvmm servers. First, I generated the corresponding dtb file from qemu for *virt* machine to get the exact pcie device node. $ qemu-system-aarch64 -nographic -machine > virt,virtualization=true,dumpdtb=conf/arm_virt-64-full.dtb > $ dtc -I dtb -O dts conf/arm_virt-64-full.dtb Secondly, I copied the following nodes to my dts file (*pcie@10000000*, *intc@8000000* and *v2m@8020000*) exactly as they are in the original dts file. Finally, I modified the ned scripts as mentioned in the comments of the *pcie_ecam.cc* file. The issue is that there is no IO driver for the device *v2m@8020000 *which is responsible for msi-controller. This device is needed for the PCIe. The error logs : > VMM[PCIe ctl]: PCIe host bridge pcie@10000000 refers to invalid MSI > controller: MSI parent is not an MSI controller > VMM[HW PCI dev]: No MSI-X controller available for MSI-X device pci_bus[1] > (devid=1) > VMM[HW PCI dev]: No MSI-X controller available for MSI-X device pci_bus[2] > (devid=2). > VMM[ioproxy]: No corresponding IO resource for 'v2m@8020000'.reg[0] > (0x8020000-0x8020fff). > VMM[vm]: Device creation for v2m@8020000 failed. Disabling device. How can I pass through the PCIe device if there is no IO driver for the needed msi-controller ? Thanks in advance, Regards -- Mohamed Dawod *Software Engineer, *Cairo Egypt -- *Driving Innovation! Visit our website www.avelabs.com <http://www.avelabs.com/>*, to read Avelabs Confidentiality Notice, follow this link: http://www.avelabs.com/email/disclaimer.html <http://www.avelabs.com/email/disclaimer.html> _______________________________________________ l4-hackers mailing list -- l4-hackers(a)os.inf.tu-dresden.de To unsubscribe send an email to l4-hackers-leave(a)os.inf.tu-dresden.de

1 0

virtio disk handling
by Mohamed Dawod 09 Oct '24

09 Oct '24

Hello, I was reading this tutorial <https://github.com/kernkonzept/manifest/wiki/NVMeWithLinux> about using NVMe server with Linux guest and it works fine. Now I'm trying to apply the same tutorial but for arm64 instead of AMD64/X86_64. As expected, it didn't work because arm64 device tree blob/source doesn't contain the same *PCI* bus with the attached *virtio_disk* device node. Instead, virt-arm_virt-64.dts file contains only 2 VMM virtual devices for ARM guests : *virtio_uart* and *virtio_net*. I need a way to apply the same Tutorial (using NVMe server with Linux guests) for ARM64 instead of AMD64/X86_64. Any suggestions? Thank you, Regards -- -- *Driving Innovation! Visit our website www.avelabs.com <http://www.avelabs.com/>*, to read Avelabs Confidentiality Notice, follow this link: http://www.avelabs.com/email/disclaimer.html <http://www.avelabs.com/email/disclaimer.html> _______________________________________________ l4-hackers mailing list -- l4-hackers(a)os.inf.tu-dresden.de To unsubscribe send an email to l4-hackers-leave(a)os.inf.tu-dresden.de

3 2

sharing RTC device between 2 linux VMs
by Mohamed Dawod 03 Sep '24

03 Sep '24

Hi, I was trying to pass the RTC device from the host machine (qemu-arm46) to the guest machine linux VM on top of L4. and it was done successfully. Now I'm trying to share the same device between 2 linux VMs on top of L4. by duplicating the virtual device that describes the same physical device and also duplicating the virtual bus and passing one for each new vm. The issue if that one of the VMs is terminated because of the disability of binding the same IRQ as described in the screenshot below : [image: image.png] Please find attached all ned scripts I'm using for this experiment. Thank you, Regards -- Mohamed Dawod *Software Engineer, *Avelabs Egypt *Cell Phone : (+20) 1117311726* -- *Driving Innovation! Visit our website www.avelabs.com <http://www.avelabs.com/>*, to read Avelabs Confidentiality Notice, follow this link: http://www.avelabs.com/email/disclaimer.html <http://www.avelabs.com/email/disclaimer.html> _______________________________________________ l4-hackers mailing list -- l4-hackers(a)os.inf.tu-dresden.de To unsubscribe send an email to l4-hackers-leave(a)os.inf.tu-dresden.de

2 3

Fwd: Systems Meetup ("Mikrokernstammtisch") 16.05 (Do.) @ Cyberus Office
by Jan Bierbaum 02 May '24

02 May '24

FYI -------- Forwarded Message -------- Subject: Systems Meetup ("Mikrokernstammtisch") 16.05 (Do.) @ Cyberus Office Date: Thu, 11 Apr 2024 09:05:22 +0000 From: Philipp Schuster <philipp.schuster(a)cyberus-technology.de> Hallo alle zusammen, Wir von Cyberus würden gerne den "Mikrokernstammtisch" in Dresden wieder neues Leben einhauchen und ein gemeinsames Treffen mit der Systems Community in Dresden organisieren. Dafür möchten wir gerne unser Büro am 16.05 (Do.) von 18:00 bis 22:00 zur Verfügung stellen. Leitet diese Einladung gerne auch an einige Freunde oder Kolleg:innen weiter, wenn sie daran Interesse hätten. Wir stellen für das Meetup diverse Getränke bereit sowie einen Meeting-Raum. Hier die Fakten: - Donnerstag, 16.05, 18:00 - 22:00 - Systems Meetup, nicht nur Mikrokerne 🙂 - If necessary, we are happy to switch to english - 10-30 Leute (grobe Schätzung) - 2-4 Lightning Talks für Gesprächsstoff Lightning Talks: - 5 bis 10 Minuten - Mögliche Themen - Entwickler-Produktivität im Alltag - Testing setups - Coole Produkte/Projekte - knifflige gelöste Probleme - Demos - ... TODOs: - Bitte meldet euch ob ihr dabei seid + wie viele weitere Gäste kommen - Bitte meldet euch ob ihr Interesse habt einen kurzen Lightningtalk zu halten Hoffentlich bis bald! PS: Ich möchte euch noch darüber informieren, dass die ukvly Mailingliste die früher von Julian Stecklina betrieben wurde leider endgültig tot ist. Bei regem Interesse und Teilnahme, können wir gerne einen neuen Kommunikationschannel beim Meetup etablieren. -------------------------------------------------------- Philipp Schuster Software Engineer E-Mail: philipp.schuster(a)cyberus-technology.de Cyberus Technology GmbH Zwickauer Str. 46 01069 Dresden Deutschland/Germany Telefon: +49 175 431 6677 (Tor Lund-Larsen) Web: https://www.cyberus-technology.de/ Geschäftsführer: Tor Lund-Larsen Sitz der Gesellschaft: Dresden Amtsgericht Dresden, HRB 36573 _______________________________________________ l4-hackers mailing list -- l4-hackers(a)os.inf.tu-dresden.de To unsubscribe send an email to l4-hackers-leave(a)os.inf.tu-dresden.de

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

l4-hackers