l4-hackers

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

2827 discussions

startstop test case of the NOVA-NUL microhypervisor
by Mehdi AICHOUCH 07 Dec '12

07 Dec '12

Hello everyone, I am trying to test the NOVA+NUL microhypervisor. I played with the test application "nul/michal/apps/tests/startstop". So, I modified this test to try a new a new test case, by modifying the "hello" program that is started by the "startstop" program. I added to the Hello program the following code : ... TimerHelper * timer; timer = new TimerHelper(this); while(1) { Logging::printf("Hello ... \n", now); timer->msleep(1000); } ... This simple code will print a message and suspend the Hello program for 1 second. The problem is that when I tested this program alone, it worked perfectly but when this same program is started by the "startstop" program using start_config(), it does not suspend on the msleep(1000). Is my test correct or allowed by the NOVA-NUL microhypervisor? If it is the case, could anyone please help to debug this issue. Many thanks in advance. Mehdi PS: this is my configuration script. #!/usr/bin/env novaboot # -*-sh-*- HYPERVISOR_PARAMS=serial QEMU_FLAGS=-cpu phenom -smp 1 -serial stdio bin/apps/sigma0.nul tracebuffer_verbose S0_DEFAULT hostserial hostvga hostkeyb:0,0x60,1,12,2 \ script_start:1 script_waitchild service_config bin/apps/startstop.nul bin/apps/startstop.nulconfig <<EOF sigma0::cpu:1 sigma0::mem:16 name::/s0/log name::/s0/config name::/s0/timer name::/s0/fs/rom name::/s0/admission || rom://bin/apps/startstop.nul rom://test.nulconfig EOF bin/apps/hello.nul test.nulconfig <<EOF sigma0::cpu:1 sigma0::mem:16 name::/s0/log name::/s0/admission || rom://bin/apps/hello.nul EOF

1 0

how to use initramfs with l4linux
by Ryan Brown 06 Dec '12

06 Dec '12

How do I use an initramfs with l4linux? I tried using "l4x_rd=rom/initrd.cpio.gz" but it doesn't work. I see linux trying to use it: INITRD: 15000000 - 15114e00 ... Unpacking initramfs... INITRD: Freeing memory. ... But then I get Failed to execute /init Kernel panic - not syncing: No init found. Try passing init= option to kernel. See Linux Documentation/init.txt for guidance. I'm able to use the same initramfs file to boot normal linux kernel. I tried various combinations of cpio formats and compression but it doesn't seem to help. The only thing that works is compiling the initramfs into the kernel which I want to avoid.

1 0

error of building fiasco.OC
by FU_LONG 04 Dec '12

04 Dec '12

2 1

apic
by Ryan Brown 03 Dec '12

03 Dec '12

Is it possible to configure x86 fiasco to avoid using the apic? If so, would this have a bad effect on performance? Thanks, Ryan Brown

2 1

Re: FOSDEM 2013 - Microkernels / Component-based OSes devroom
by Stefan Kalkowski 03 Dec '12

03 Dec '12

Hi folks, sorry for bothering you again with this. I just want to remind you, there are only 12 days left until the deadline for the microkernel devroom proposals. On 10/29/2012 01:01 PM, Stefan Kalkowski wrote: > FOSDEM 2013 - Microkernels / Component-based OSes devroom > *CALL FOR PARTICIPATION* > http://fosdem.org/2013 > > The developers of several free and open-source component- and/or > microkernel-based operating systems will meet at FOSDEM 2013 in > Brussels, Belgium and will share a developer room. > > The devroom is currently looking for content in the form of talks > related to the area of component- and/or microkernel-based operating > systems. Possible topics include, but are not limited to: > > * OS introduction to developers of other OS > * Subsystems and architecture > * Hardware and device drivers > * Tools and languages > * Release engineering and testing > * Experience and learning from mistakes > * Technical challenges > * Community and life with an OS-project > * Academia and education > > Please send your talk proposal(s) no later than by 2012-12-15 to: > > microkernel-devroom at lists.fosdem.org > > Make sure to include the following in your proposal: > > * title of your talk (will be printed in the FOSDEM booklet) > * your full name (will be printed in the FOSDEM booklet) > * a short abstract > * duration of your talk (please, no longer than 45 minutes) > > The final devroom schedule (along with accepted talks) will be announced > on the above mailing list on 2012-12-22. Moreover, the speakers will be > notified via e-mail. The schedule will be also published on the FOSDEM > web and in the FOSDEM booklet after 2013-01-10. > > If you do not want to give a talk yourself, you may still send > suggestions for what else you would like to see, or do in the devroom. > Please send your suggestions to the above mailing list. > > The devroom is scheduled for Saturday of February 2. The seating > capacity of the room is 74 seats. Any changes will be announced in the > above mailing list. > -- Stefan Kalkowski Genode Labs http://www.genode-labs.com/ · http://genode.org/

1 0

App on L4Re
by OSDepend 30 Nov '12

30 Nov '12

Hi, all! I'm newbie on L4 microkernel, and have been confused by some questions of the L4 constructions! Are there any avaliable Applications or Projects directly on the L4Re but not depending On L4Linux? Like gcc or other app? If existed, can we can directly bulild some application or tools after boot L4 microkernel? Every feedbacks or documention links are appreciated! :> Best, Chen 2012-11-23 zhengc

7 14

Qusestion about building L4Re
by FU_LONG 30 Nov '12

30 Nov '12

3 2

Start Linux inside a Vancouver VM using a virtual disk.
by Mehdi AICHOUCH 27 Nov '12

27 Nov '12

Hello, I was trying to run Linux inside a Vancouver virtual machine and using a virtual disk. But, I got an error when Linux kernel try to mount the root file system. I tested the Linux kernel and the virtual disk image using Qemu and it worked well. I was also able to start the same Linux kernel on Vancouver but by providing an initrd ramfs file. Please see below the trace of the linux boot: (5) # [ 23.652175] VFS: Cannot open root device "(null)" or unknown-block(0,0) (5) # [ 23.652175] Please append a correct "root=" boot option; here are the availa (5) # | ble partitions: (5) # [ 23.652175] Kernel panic - not syncing: VFS: Unable to mount root fs on unkn (5) # | own-block(0,0) (5) # [ 23.652175] Pid: 1, comm: swapper/0 Tainted: G W 3.2.16-rt27 #3 (5) # [ 23.652175] Call Trace: (5) # [ 23.652175] [<c05f5299>] panic+0x66/0x173 (5) # [ 23.652175] [<c0849ca1>] mount_block_root+0x1d3/0x26c (5) # [ 23.652175] [<c02311bc>] ? sys_mknod+0x2c/0x30 (5) # [ 23.656100] [<c0849d93>] mount_root+0x59/0x5f (5) # [ 23.656100] [<c0849ee7>] prepare_namespace+0x14e/0x192 (5) # [ 23.656100] [<c0221665>] ? sys_access+0x25/0x30 (5) # [ 23.656100] [<c0849344>] kernel_init+0x13f/0x14e (5) # [ 23.656100] [<c0849205>] ? parse_early_options+0x25/0x25 (5) # [ 23.656100] [<c05fe6c2>] kernel_thread_helper+0x6/0x10 and this is the script I used to run Vancouver and Linux : #!/usr/bin/env novaboot # -*-sh-*- HYPERVISOR_PARAMS=serial WVDESC=Kernel compile inside VM (on virtual disk, EPT + VPID) WVTEST_TIMEOUT=1200 QEMU_FLAGS=-cpu phenom -m 2048M bin/apps/sigma0.nul tracebuffer_verbose S0_DEFAULT hostserial hostvga hostkeyb:0,0x60,1,12 script_start:1,1 \ service_config vdisk_empty:736870912 service_disk bin/apps/vancouver.nul bin/boot/munich imgs/bzImage imgs/mdisk.img vancuver.nulconfig <<EOF sigma0::mem:512 sigma0::dma name::/s0/log name::/s0/timer name::/s0/fs/rom name::/s0/admission name::/s0/disk disk::0 || rom://bin/apps/vancouver.nul PC_PS2 ahci:0xe0800000,14,0x30 drive:0,0,0 || rom://bin/boot/munich || rom://imgs/bzImage clocksource=tsc console=ttyS0 || rom://imgs/mdisk.img EOF Could someone tell me how to correct this error. Or give me some hints to another solution to build a disk image. I need a disk image in order to add some executable that I already compiled on my host machine and to run these executable on the Linux guest OS once it will start on Vancouver VM. Thank you very much in advance for your help. Mehdi

2 2

Our experience with Fiasco.OC + Genode on the Pandaboard
by Norman Feske 26 Nov '12

26 Nov '12

Dear L4 hackers, for those of you who enjoy reading experience reports, we have put together an article that describes our work with enabling the Genode OS Framework on the Pandaboard using the Fiasco.OC kernel: http://genode.org/documentation/articles/pandaboard With the new developed driver support for SD-card, USB, networking, and HDMI in place, we have become able to run a wide variety of Genode system scenarios including the GNU userland, Qt4, GDB, and L4Linux on this nice platform. In addition to creating and porting device drivers, we conducted extensive performance optimizations in order to reach an I/O performance that is roughly on par with native Linux. The article describes those steps in detail. Best regards Norman -- Dr.-Ing. Norman Feske Genode Labs http://www.genode-labs.com · http://genode.org Genode Labs GmbH · Amtsgericht Dresden · HRB 28424 · Sitz Dresden Geschäftsführer: Dr.-Ing. Norman Feske, Christian Helmuth

2 2

Question about L4Linux
by OSDepend 26 Nov '12

26 Nov '12

Hi, I want to know why we build L4Linux here on L4? Is there any benefit comparing to pure Linux? Best, Chen 2012-11-23 郑晨

3 3

Jump to page:

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