- l4-hackers - example.com Site

compile error svn rev 27 on amd64
by lkcl 25 Nov '10

25 Nov '10

folks hi thought i'd give l4re a shot, see how far it is along, and if i can get it compiled on ARM. that failed miserably, with libstdc++v3 errors (using arm-linux-gnueabi-g++ 4.3.2) in Rope and in __is_empty so i thought i'd try amd64, and _that_'s failing too! make[5]: Leaving directory `/home/lkcl/src/l4ka/build-x86/pkg/l4re/util/libs/OBJ-amd64_K8-l4f' make[7]: Leaving directory `/home/lkcl/src/l4ka/build-x86/pkg/bootstrap/server/src/ARCH-amd64/libc32/OBJ-amd64_K8' make[6]: Leaving directory `/home/lkcl/src/l4ka/src/l4/pkg/bootstrap/server/src/ARCH-amd64/libc32' ==> Linking bootstrap32.elf ... Building Makefile.inc /usr/bin/ld: skipping incompatible /usr/lib/gcc/x86_64-linux-gnu/4.4.3/libgcc.a when searching for -lgcc /usr/bin/ld: skipping incompatible /usr/lib/gcc/x86_64-linux-gnu/4.4.3/libgcc.a when searching for -lgcc /usr/bin/ld: cannot find -lgcc collect2: ld returned 1 exit status make[5]: *** [bootstrap32.elf] Error 1 i put this into the Makefile but it's having none of it: LDFLAGS := -nostdinc -m32 yes obviously -lgcc is installed, ld is clearly trying to link with libgcc.a instead of ..../32/libgcc.a - what's the story, here? tia, l. p.s. i really do want to get ARM compiled but whereas gcc 4.4.2 and g++ 4.4.2 seem to not barf on libstdc++-v3, arm-linux-gnueabi-g++-4.3.2 does. what's the story there, as well? -- View this message in context: http://old.nabble.com/compile-error-svn-rev-27-on-amd64-tp30307833p30307833… Sent from the L4 mailing list archive at Nabble.com.

1 0

how to compile l4re with a x86_64 linux?
by Chengqi Song 24 Nov '10

24 Nov '10

hi, I want to try l4re on my own laptop, here is the info from uname -a: Linux lars-x200s 2.6.35-ARCH #1 SMP PREEMPT Sat Oct 30 21:22:26 CEST 2010 x86_64 Intel(R) Core(TM)2 Duo CPU L9300 @ 1.60GHz GenuineIntel GNU/Linux I first checked out src: svn cat http://svn.tudos.org/repos/oc/tudos/trunk/repomgr | perl - init http://svn.tudos.org/repos/oc/tudos fiasco l4re then follow this page to build: http://os.inf.tu-dresden.de/L4Re/build.html with default config, this error is reported before exit: ld: i386:x86-64 architecture of input file `/usr/lib/gcc/x86_64-unknown-linux-gnu/4.5.1//crtbeginS.o' is incompatible with i386 output ld: i386:x86-64 architecture of input file `/usr/lib/gcc/x86_64-unknown-linux-gnu/4.5.1//crtendS.o' is incompatible with i386 output make[5]: *** [libl4sys.so] Error 1 does it mean i need a 32bit system to build L4? thanks lars

2 5

Building L4linux
by Maxime Lastera 15 Nov '10

15 Nov '10

Thank you for your help. The modules.list wasn't set correctly. So now l4linux is running. Which modules I need to add to modules.list file to use xterm on l4linux? -- ------------------------------------------------ Maxime LASTERA Phd Student Dependable Computing and Fault Tolerance group LAAS-CNRS 7 av Colonel Roche 31077 Toulouse E-mail: mlastera(a)laas.fr Phone : +33561336979 ------------------------------------------------

2 2

Building L4linux
by Maxime Lastera 09 Nov '10

09 Nov '10

hi, I try without success to create .elf file with the command 'make image E=l4linux' I have the following message : Building entry "l4linux" Unknown entry "l4linux"! at /home/Maxx/Downloads/l4re-snapshot/src/l4/tool/lib/L4/ModList.pm line 168 the modules.list file contains entry l4linux x86 modaddr 0x002000000 kernel fiasco -serial_esc roottask moe rom/l4lx.cfg module l4re module ned module l4lx.cfg module vmlinuz I think the moduless.list file isn't in the good directory but I try l4re directory and l4linux without success neither. Any ideas ? -- ------------------------------------------------ Maxime LASTERA Phd Student Dependable Computing and Fault Tolerance group LAAS-CNRS 7 av Colonel Roche 31077 Toulouse E-mail: mlastera(a)laas.fr Phone : +33561336979 ------------------------------------------------

2 1

running l4linux on PB11mpcore
by Rahul Ramasubramanian 08 Nov '10

08 Nov '10

Hi , I am running into a few issues while trying to run the l4linux image on the realview board. when i execute the command on the boot monitor prompt M> run l4linux.elf i get some garbled output on the screen and then system goes unresponsive ( a blinking cursor) . I had assumed that i will get some kind of a shell prompt after booting.Is this assumption correct? I have the minicom configured correctly ( used the values suggested on the realview user guide) ,so i think the error is not on that side. Has anyone run into this issue before. I will appreciate any pointers on resolving this issue. Thanks Rahul On Sun, Nov 7, 2010 at 3:39 PM, Adam Lackorzynski <adam(a)os.inf.tu-dresden.de > wrote: > > On Sun Nov 07, 2010 at 15:08:25 -0500, Rahul Ramasubramanian wrote: > > Now after the build , i have a bootstrap_L4Linux_ARM.elf file.Can i run > this > > on the realview board using the boot monitor command run or is there > > anything else which needs to be done ? > > Yes, you can run the image using the boot monitor. > > > Adam > -- > Adam adam(a)os.inf.tu-dresden.de > Lackorzynski http://os.inf.tu-dresden.de/~adam/ > > _______________________________________________ > l4-hackers mailing list > l4-hackers(a)os.inf.tu-dresden.de > http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers >

2 2

Building L4linux
by Maxime Lastera 07 Nov '10

07 Nov '10

Hi, I have built succefully L4linux. I have used the snapshot version. So now I want to run it, but I don't have tftboot directory in l4linux tree. I can't follow the example because I don't have many modules like names l4io a vmlinuz file is in l4linux tree. what are the steps to boot on L4linux from harddrive ? -- ------------------------------------------------ Maxime LASTERA Phd Student Dependable Computing and Fault Tolerance group LAAS-CNRS 7 av Colonel Roche 31077 Toulouse E-mail: mlastera(a)laas.fr Phone : +33561336979 ------------------------------------------------

3 3

l4linux on arm11mpcore (build error)
by Rahul Ramasubramanian 07 Nov '10

07 Nov '10

Hi I am trying to build l4linux for arm. I have already built and tested l4re and the fiasco kernel (generated a simple image using the hello.lua script) After pulling the l4linux sources from svn , i used the following steps (as described in the wiki) 1> l4linux-2.6$ make O=/tmp/buildpath L4ARCH=arm CROSS_COMPILE=arm-linux- arm_defconfig 2>l4linux-2.6$ make O=/tmp/buildpath L4ARCH=arm CROSS_COMPILE=arm-linux- menuconfig In menuconfig , i gave the correct path for l4 build dirctory ( in my case it is /home/syslab1/l4fiasco/src/l4/build). This is the directory which hosuses the images folder etc after the l4re and the simple hello image was built. I also selected the arm architecture 3>l4linux-2.6$ make O=/tmp/buildpath L4ARCH=arm CROSS_COMPILE=arm-linux- I get the following error when i run the last command syslab1@syslab1-desktop:~/l4fiasco/l4linux$ make O=/tmp/l4linuxbuild/ L4ARCH=arm CROSS_COMPILE=arm-linux- L4 source directory: /home/syslab1/l4fiasco/src/l4 PWD=/home/syslab1/l4fiasco/src/l4 make -C /home/syslab1/l4fiasco/src/l4 -f /home/syslab1/l4fiasco/l4linux/arch/l4/Makefile.l4conf O=/home/syslab1/l4fiasco/src/l4/build L4X_LOOP_CHECK=1 OUTPUT=/tmp/l4linuxbuild/Makeconf.l4conf GEN /tmp/l4linuxbuild/Makeconf.l4conf GEN /tmp/l4linuxbuild/Makefile scripts/kconfig/conf -s arch/l4/Kconfig include/config/auto.conf:486:warning: symbol value 'elf32-i386' invalid for OUTPUT_FORMAT include/config/auto.conf:690:warning: symbol value 'arch/x86/configs/i386_defconfig' invalid for ARCH_DEFCONFIG include/config/auto.conf:896:warning: symbol value '' invalid for ACPI_CUSTOM_DSDT_FILE include/config/auto.conf:1692:warning: symbol value '-fcall-saved-ecx -fcall-saved-edx' invalid for ARCH_HWEIGHT_CFLAGS Getting required compilation flags failed. L4OBJ: /home/syslab1/l4fiasco/src/l4/build L4_REQUIRED_MODS: stdlibs log l4re_c-util libio shmc /home/syslab1/l4fiasco/l4linux/arch/l4/Makefile:287: *** Aborting.. Stop. make: *** [sub-make] Error 2 Can anyone tell me where I am going wrong. This thing seems simple enough but i am sure i am making a simple mistake which i am unable to resolve. Will appreciate if someone can tell me how to make this error go away. Thanks Rahul

2 1

Building L4linux
by Maxime Lastera 05 Nov '10

05 Nov '10

Hi, A 'make' in /home/Maxx/Downloads/l4re/src/l4/mybuild come with successful end. In the directory /home/Maxx/Downloads/l4re/src/l4/mybuild/pc/ there are stdlibs.pc libio.pc l4re_c-util.pc and many more. -- ------------------------------------------------ Maxime LASTERA Phd Student Dependable Computing and Fault Tolerance group LAAS-CNRS 7 av Colonel Roche 31077 Toulouse E-mail: mlastera(a)laas.fr Phone : +33561336979 ------------------------------------------------

1 0

Building L4linux
by Maxime Lastera 04 Nov '10

04 Nov '10

Hi, The result of make in l4linux directory is : Getting required compilation flags failed. L4OBJ: /home/Maxx/Downloads/l4re/src/l4/mybuild L4_REQUIRED_MODS: stdlibs log l4re_c-util libio shmc rtc /home/Maxx/Downloads/l4linux/arch/l4/Makefile:287: *** Aborting.. Stop. I understand these packages are not found, but when I check manually they are in L4tree directory, more precisely in l4re/src/l4/mybuild/pkg -- ------------------------------------------------ Maxime LASTERA Phd Student Dependable Computing and Fault Tolerance group LAAS-CNRS 7 av Colonel Roche 31077 Toulouse E-mail: mlastera(a)laas.fr Phone : +33561336979 ------------------------------------------------

2 1

Booting Fiasco with U-Boot (or: what is 0x002000000?)
by Thomas DuBuisson 03 Nov '10

03 Nov '10

All, Thanks for the previous help with building Fiasco/L4Re. Now that its built I have given a couple stabs at booting it on my beagleboard like device (I'll document all this in a blog and or wiki when/if I finish). Unfortunately I can't seem to get any sign of life on the screen (perhaps I should solder up a serial line for debugging purposes). What I've done: 1) Cross compiled L4Re and Fiasco for the beagleboard. 2) Copied l4re, lua, moe, fiasco, and created hello.lua to the SDs first partition (the fat boot partition). 3) Rebuilt/copied over u-boot.bin using: #define CONFIG_EXTRA_ENV_SETTINGS \ "bootargs=tbr=x console=tty1 omapfb.mode=dvi:1024x600MR-16@60 omapfb.vrfb=1 omapfb.vram=0:8M,1:4M,2:8M root=/dev/mmcblk0p2 rootdelay=1 rootfstype=ext3\0" #define CONFIG_BOOTCOMMAND \ "mmc init; fatload mmc 0 0x02000000 fiasco; bootm 0x02000000" Though I have tried different addresses including what I think is a typo on the "Getting Started" page of 0x002000000. So some questions are: 1) I'm pretty sure the bootargs need changed. For example, does u-boot need to load ned, moe, and hello? Where should they be loaded? Any other comments on what fiasco expects the bootloader to do? (this is different than what the wiki provides of "how to do those unspecified things using GRUB") 2) To what address should I load fiasco? I assume it matters. 3) If these questions are already answered somewhere then I'd be more than happy with a link. Cheers, Thomas

3 2

Building L4linux
by Maxime Lastera 03 Nov '10

03 Nov '10

When I set the L4 source directory to L4re build directory it's works, but some required L4 modules are required stdlibs log l4re_c-util libio shmc rtc. I have found this modules in the l4re-snapshot/src/l4/pkg but there are not found by the program. I need to copy the modules in an other directory ? -- ------------------------------------------------ Maxime LASTERA Phd Student Dependable Computing and Fault Tolerance group LAAS-CNRS 7 av Colonel Roche 31077 Toulouse E-mail: mlastera(a)laas.fr Phone : +33561336979 ------------------------------------------------

2 1

Building L4linux
by Maxime Lastera 03 Nov '10

03 Nov '10

Hi, I have compiled fiasco and L4re with success. The Hello World exemple is running using qemu. Now I want to try L4linux on top of fiasco. When I try to comiple L4linux the following error occur: "cannot determine L4 source directory" The L4 source directory is the directory where I have built L4re or is a reference to an other directory ? -- ------------------------------------------------ Maxime LASTERA Phd Student

1 0

Information about buildingl4re
by Maxime Lastera 02 Nov '10

02 Nov '10

Hi, I try to add -fno-stack-protector-all to to GCCNOSTACKPROTOPT_f in l4/mk/ but I have always the same error. In a previou message "Fiasco / L4Re compilation issues" it said Fedora builds GCC with stack protection enabled. So if I understand, I have 2 solutions 1- build from source gcc on Fedora 2- install an other OS Do you have an other idea ? -- ------------------------------------------------ Maxime LASTERA Phd Student Dependable Computing and Fault Tolerance group LAAS-CNRS 7 av Colonel Roche 31077 Toulouse E-mail: mlastera(a)laas.fr Phone : +33561336979 ------------------------------------------------

2 1

Information about buildingl4re
by Maxime Lastera 02 Nov '10

02 Nov '10

Hi, I want to test L4linux on top of L4/fisco I follow the building page of Fiasco, for this one all be done without error. So I start to follow the instructions to build L4re. I use the default configuration file. The results of the command "make O=path/to/builddir" failed because of an undefined reference to _stack_chk_fail_local. After some research I understand this "undefined reference" is add by gcc which is in version 4.4.4 on my fedora 13 OS. One soultion is to add CFLAGS= -fno-stack-protector in gcc command but I don't find gcc command in Makefile...! Do you have a solution ? Thanks in advance. -- ------------------------------------------------ Maxime LASTERA Phd Student Dependable Computing and Fault Tolerance group LAAS-CNRS 7 av Colonel Roche 31077 Toulouse E-mail: mlastera(a)laas.fr Phone : +33561336979 ------------------------------------------------

1 0

Fiasco / L4Re compilation issues
by Thomas DuBuisson 01 Nov '10

01 Nov '10

All, I've never had success with Fiasco but decided to give it another go so I could run some benchmarks. In short, I had one success and two failures. Any help would be appreciated. 1) I can build Fiasco for x86 on the host (32 bit x86 system). Yay 2) Can't build Fiasco for ARM on an x86 host due to... an old arm-linux-gcc version? 3) Can't build L4Re due to linker error. 1) Successful build of Fiasco x86 This and other builds are using a recent pull from the repo [1] on a Fedora based 32bit x86 system running gcc 4.4.4 on Linux 2.6.34. 2) Failure to build Fiasco ARM This early failure seems to be a simple problem with gcc changing the arguments - can anyone tell me the version of the "official" arm compiler in use? I'm running arm-linux-gcc 3.4.4. ------------ make[1]: Entering directory `/home/tommd/dev/L4/L4Re/build_arm' ... Generating version information ... Making kip.o cc1plus: error: invalid option `abi=apcs-gnu' make[1]: *** [kip.o] Error 1 ------------- 3) Failure to build L4Re due to linker error The symbol "__stack_chk_fail_local" is missing when building "libl4util.so" (see below). A quick objdump/grep doesn't show this symbol in any object file in the build directory - is the build system slightly broken? I see the source definition but don't really want to hack around in the build system. $ ld --version GNU ld version 2.20.51.0.2-20.fc13 20091009 ------------- make[5]: Entering directory `/home/tommd/dev/L4/L4Re/build/pkg/l4util/lib/src/OBJ-x86_core2-l4f' ==> Linking to shared libl4util.so /usr/lib/gcc/i686-redhat-linux/4.4.4/libgcc_eh.a(unwind-dw2.o): In function `.L107': (.text+0xb79): undefined reference to `__stack_chk_fail_local' /usr/lib/gcc/i686-redhat-linux/4.4.4/libgcc_eh.a(unwind-dw2.o): In function `.L358': (.text+0x1a85): undefined reference to `__stack_chk_fail_local' /usr/lib/gcc/i686-redhat-linux/4.4.4/libgcc_eh.a(unwind-dw2.o): In function `_Unwind_Backtrace': (.text+0x24bf): undefined reference to `__stack_chk_fail_local' /usr/lib/gcc/i686-redhat-linux/4.4.4/libgcc_eh.a(unwind-dw2.o): In function `_Unwind_ForcedUnwind': (.text+0x26ad): undefined reference to `__stack_chk_fail_local' /usr/lib/gcc/i686-redhat-linux/4.4.4/libgcc_eh.a(unwind-dw2.o): In function `__frame_state_for': (.text+0x29e8): undefined reference to `__stack_chk_fail_local' /usr/lib/gcc/i686-redhat-linux/4.4.4/libgcc_eh.a(unwind-dw2.o):(.text+0x2b78): more undefined references to `__stack_chk_fail_local' follow ld: libl4util.so: hidden symbol `__stack_chk_fail_local' isn't defined ld: final link failed: Nonrepresentable section on output make[5]: *** [libl4util.so] Error 1 ---------------- Cheers, Thomas [1] http://os.inf.tu-dresden.de/L4Re/download.html

4 5

How to compile DDekit in l4re-snapshot-2010080920?
by 方明伟 25 Oct '10

25 Oct '10

Hi : Everyone! I am a new one to use fiasco.OC. Now, I am compiling L4Linux for X86 and arm. But I didn't know how to configure the DDekit. In "l4/pkg/dde/Makefile", three senteces are being commented. "# $(VERBOSE)PWD=$(PWD)/linux26/include $(MAKE) -C linux26/include # $(VERBOSE)PWD=$(PWD)/linux26/contrib/include $(MAKE) -C linux26/contrib/include" "# $(VERBOSE)PWD=$(PWD)/linux26/lib $(MAKE) -C linux26/lib" Does that mean I can't use the DDekit now? So I wondered can DDekit be used in L4Re? If yes, how can I configure and compile the dde in /l4/pkg?

2 1

L4Re multiple Linux instances communication
by Michael Weiß 27 Sep '10

27 Sep '10

Hi, I'm trying to establish a communication between several L4Linux instances on fiasco.oc kernel with L4Re on the beagle board, preferable through a virtual network. I found out that the outdated L4env provided a virtual netwok switch, ORe and the l4ore driver in L4Linux for that purpose. Is there something similar available for L4Re and how can I setup a connection between two L4Linux instances? Thanks, Michael

2 8

Re: L4 and ARM Cortex-A8 (OMAP3)
by Brett Mahar 22 Sep '10

22 Sep '10

> Fiasco.OC/L4Re supports the beagleboard out of the box now, at least the > older versions. I'm not sure about the XM, I hope it's not completely > different to the previous ones. > Adam That is good news. The xM uses DM3730 main chip, which is supposedly "compatible with OMAP-3 architecture." Both chips built around cortex-A8 core, so hopefully all will be well. Brett.

1 0

Re: L4 and ARM Cortex-A8 (OMAP3) Thomas DuBuisson
by Brett Mahar 22 Sep '10

22 Sep '10

On Thu Apr 22, 2010 at 15:37:55 -0700, Thomas DuBuisson wrote: > I'm wanting to experiment with L4 on a OMAP3 (beagleboard based) > system but am having difficulting finding a suitable L4 microkernel. > Does anyone on this list have comments/suggestions wrt which kernel to > use, building, u-boot configuration, etc? >>I don't want to promise too much but I have a Fiasco version for the BB >>sitting on my disk. I'm currently trying to get all this in a reasonable >>state. >>Adam Just wondering if anyone has got any new info since these posts earlier in the year? I am waiting on a beagleboard xm to arrive in the mail.... Brett.

2 1

how to run Fiasco.OC
by 方明伟 16 Sep '10

16 Sep '10

2 1

Hello World!
by Marc Mauri Alloza 10 Sep '10

10 Sep '10

Hello I'm new to L4, L4re and all this stuff and i'm trying to find the jdb manual, most links I found in internet are broken. Someone knows how to find it? Thanks.

2 1

Debugging applications on Fiasco.OC. and questions about L4re
by Pablo Montesinos 01 Sep '10

01 Sep '10

(sorry if it's a duplicate, I sent the previous one from an account outside the mailing list and I did not know whether it would go through) Hi, I need to debug an application that I've ported to Fiasco.OC and I was wondering what is the preferred way to do it. (The application works fine in Linux, but there must be something wrong with the libraries I ported). Jdb seems not very friendly if all you want to do is debugging an application. My second question is about L4re. So far, all the applications running on my Fiasco.OC are console-based. However, I would like to run more complex apps that might require a graphical environment. I noticed that, with L4env, it was possible to have it. Is it possible to do it with L4re? Any plans to add it in the near future. I would use Genode, but I've been told at the Genode list that Fiasco.OC is not supported by Genode. Is there an alternative to Genode on L4re? Thanks, Pablo

2 3

Fiasco.OC hangs in Intel Core 2 duo
by Karthik Vadambacheri Manian 29 Aug '10

29 Aug '10

Hi all, I compiled the new Fiasco.OC microkernel and L4RE in my Core 2 Duo PC with gcc 4.4.3. While configuring the Fiasco.OC microkernel I selected PC architecture as AMD64 and CPU type as Intel Core 2. But while configuring L4RE when I selected the PC architecture as AMD64 there is no option for CPU type as Intel Core 2. Hence I selected PC type as K8 which is one of the options. I created the cd image using *make grub2iso E=hello. *But when I run the virtual machine in qemu-system-x86_64 it hangs. I have tested the same with different PC type as K10/Barcelona, opteron, but got the same result. I have pasted the output below: ========================================================= $ qemu-system-x86_64 -m 1024m -cdrom hello.iso -boot d -serial stdio Welcome to Fiasco.OC (amd64)! L4/Fiasco.OC amd64 microkernel (C) 1998-2010 TU Dresden Rev: r16 compiled with gcc 4.4.3 for Intel Core2 [] Build: #1 Tue Aug 17 12:12:24 EDT 2010 Performance-critical config option(s) detected: CONFIG_NDEBUG is off Superpages: yes Kmem:: cpu page at 3fde6000 (4096Bytes) ACPI-Init ACPI: RSDP = 0xf8960 pRSDT = 3fffde30 pXSDT = 0 ACPI: OEM: BOCHS MADT = 0x201fdeb0 IO-APIC: struct: 0x201fdee4 adr=fec00000 IO-APIC: dual 8259: yes IO-APIC: ovr[ 0] 00 -> 2 IO-APIC: ovr[ 1] 05 -> 5 IO-APIC: ovr[ 2] 09 -> 9 IO-APIC: ovr[ 3] 0a -> a IO-APIC: ovr[ 4] 0b -> b IO-APIC: NOTE IRQ overrides are ignored! IO-APIC: pins 23 PIN[ 0m]: vector=20, del=0, dm=physical, dest=0 (high, edge) PIN[ 1m]: vector=21, del=0, dm=physical, dest=0 (high, edge) PIN[ 2m]: vector=22, del=0, dm=physical, dest=0 (high, edge) PIN[ 3m]: vector=23, del=0, dm=physical, dest=0 (high, edge) PIN[ 4m]: vector=24, del=0, dm=physical, dest=0 (high, edge) PIN[ 5m]: vector=25, del=0, dm=physical, dest=0 (high, edge) PIN[ 6m]: vector=26, del=0, dm=physical, dest=0 (high, edge) PIN[ 7m]: vector=27, del=0, dm=physical, dest=0 (high, edge) PIN[ 8m]: vector=28, del=0, dm=physical, dest=0 (high, edge) PIN[ 9m]: vector=29, del=0, dm=physical, dest=0 (high, edge) PIN[10m]: vector=2a, del=0, dm=physical, dest=0 (high, edge) PIN[11m]: vector=2b, del=0, dm=physical, dest=0 (high, edge) PIN[12m]: vector=2c, del=0, dm=physical, dest=0 (high, edge) PIN[13m]: vector=2d, del=0, dm=physical, dest=0 (high, edge) PIN[14m]: vector=2e, del=0, dm=physical, dest=0 (high, edge) PIN[15m]: vector=2f, del=0, dm=physical, dest=0 (high, edge) PIN[16m]: vector=30, del=0, dm=physical, dest=0 (high, edge) PIN[17m]: vector=31, del=0, dm=physical, dest=0 (high, edge) PIN[18m]: vector=32, del=0, dm=physical, dest=0 (high, edge) PIN[19m]: vector=33, del=0, dm=physical, dest=0 (high, edge) PIN[20m]: vector=34, del=0, dm=physical, dest=0 (high, edge) PIN[21m]: vector=35, del=0, dm=physical, dest=0 (high, edge) PIN[22m]: vector=36, del=0, dm=physical, dest=0 (high, edge) PIN[23m]: vector=37, del=0, dm=physical, dest=0 (high, edge) Allocate cpu_mem @ 0xfffffffffffe9000 Local APIC[00]: version=14 max_lvt=5 APIC ESR value before/after enabling: 00000000/00000000 Using the PIT (i8254) on IRQ 2 for scheduling CPU[0]: GenuineIntel (6:2:3:0) Model: Unknown CPU at 2397 MHz 32 KB L1 I Cache (8-way associative, 64 bytes per line) 32 KB L1 D Cache (8-way associative, 64 bytes per line) 2048 KB L2 U Cache (8-way associative, 64 bytes per line) Freeing init code/data: 32768 bytes (8 pages) Calibrating timer loop... ======================================================== Also while creating image using *make grub2iso E=hello*, the fiasco microkernel could not be located by the make script. It said the following error. $ make grub2iso E=hello make[1]: Entering directory `/home/karthik/Research/tudos/src/l4' Processing entry 'hello' Could not find 'fiasco' with path ':/home/karthik/Research/tudos/src/ubuild/bin/amd64_K8:/home/karthik/Research/tudos/src/ubuild/bin/amd64_K8/l4f:/home/karthik/Research/tudos/src/ubuild/lib/amd64_K8:/home/karthik/Research/tudos/src/ubuild/lib/amd64_K8/l4f' at tool/lib/L4/ModList.pm line 271. But when I made a symbolic link to the fiasco microkernel built previously to one of the directories in the above path, it got resolved. It would be great if it could find the microkernel by itself. Please let me know how to overcome the above issues. Thanks a lot for your time, karthik

3 3

loading "dpci" module from vancouver fails.
by Shyamali Mukherjee 24 Aug '10

24 Aug '10

My grub menu entry looks like below: SARGS="S0_DEFAULT hostserial hostvga:0x40000,0x40000 hostkeyb:0,0x60,1,12 startlate:0xfffffffd" VMMARGS="PC_PS2 kbmodifier:0x40000" LABEL novaiommu MENU LABEL NOVA (IOMMU) KERNEL mboot.c32 APPEND /nul/hypervisor serial dmar --- \ /nul/sigma0.nul $SARGS --- \ /nul/vancouver.nul $VMMARGS dpci:2,0,0 82576vf:0xf7ce0000,0xf7cc0000 sigma0::dma sigma0::mem:64 --- \ /tools/munich sigma0::attach --- \ /demo/linux/bzImage root=/dev/ram0 clocksource=tsc sigma0::attach --- \ /demo/linux/initrd sigma0::attach --- \ /nul/tutor.nul TEXT HELP This setup has DMA remapping. The first Linux VM has direct access to your first network card and creates a bridge to the virtual network. You need Intel VT-d support for this. ENDTEXT Observation: -------------------- 1. I can not have "hypervisor serial dmar".. Can ONLY use "hypervisor dmar" or "serial". 2. I figured that it fails to load "dpci" module. I have looked at pcidirect.cc available under: nova-userland-0.2/vancouver/model/pcidirect.cc It says: "Example: Use 'dpci:2,,0,0x21' to attach the first network controller to 00:04.1.", Then from build_cd.sh I see "dcpi:2,0,0" But boot fails: Please see screenshot attached. 3. where can I find "sigma0" and "munich" sources. It seems in "NUL release 0.2" has these prebuilt. Only sources I see are like for vancouver.nul. --thanks

3 2

Using L4Linux on Fiasco.OC - How?
by Andreas Speier 10 Aug '10

10 Aug '10

Hi, I just started porting some Projects running on L4Linux on the "old" Fiasco to Fiasco.OC with the current L4Linux version. Starting with the "hello" example of the documentation was no problem, but I could not find out how things have to be configured when using L4Linux. Which dependencies must be regarded to make it run properly? Is there any documentation I could use, or can anyone publish some example documentation and configuration to run L4Linux on Fiasco.OC? Regards, Andreas

2 1