l4-hackers

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

2827 discussions

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

GUI: mag, dope, nitpicker, goos
by Taru Karttunen 09 Aug '10

09 Aug '10

Hello What exactly is the current situation with the various graphics related components? Mag appears to be a nitpicker replacement and dope ran under nitpicker. Goos is a new low level framework that is used by mag? Then there are various fb* like fb-drv and fbterminal. What is the current direction of the graphics and GUI components, how do they stack and what is the preferred way to get them to run? Are they documented somewhere? - Taru Karttunen

2 1

Userland [was] NOVA Microhypervisor 0.2 prerelease
by John van V. 07 Aug '10

07 Aug '10

About Userland: I am supporting a L4 drop-in replacement for Linux where a primary goal is to allow manufacturers to make drivers in the same way they make them for Micro$oft. Another goal is to streamline the creation of L4 development workstations that, for instance, can reside on a cell phone. I am doing this in this way because it makes sense to, and benefits, Userland. John Decade-old Linux Society blog: http://linux-society.blogspot.com/ -- Empathy http://thinman.com/empathy Photography http://thinman.com/photography Technology http://thinman.com

1 0

[ANNOUNCE] NOVA Microhypervisor 0.2 prerelease
by Udo A. Steinberg 06 Aug '10

06 Aug '10

Hi, The NOVA project is happy to announce that there is a new prerelease of the NOVA microhypervisor available for download at http://www.hypervisor.org/ or http://os.inf.tu-dresden.de/~us15/nova/ under the terms of the GNU General Public License version 2. NOVA is based on a modern microhypervisor written in C++ and assembler. The current implementation supports x86-32 SMP platforms with hardware virtualization features such as Intel VT-x/VT-d or AMD-V, and facilitates running multiple unmodified guest operating systems in virtual machines with near-native performance. On machines without VT-x or AMD-V, the functionality is reduced to that of a microkernel. The most prominent new feature is support for I/O virtualization and direct assignment of host devices to guest VMs using the IOMMU. For a list of other changes, please see the change log included with the source code. Cheers, - Udo

2 1

Fiasco support for ARM trustzone extensions
by Rosenberry, Robert D. 05 Aug '10

05 Aug '10

Hello, Which platforms are known to work with the ARM trustzone extensions for virtualization using the Fiasco kernel? Suggestions for preferred development boards would be appreciated. Rob

2 1

L4Re Makefile bug?
by Michael Kirkpatrick 03 Aug '10

03 Aug '10

I've downloaded the l4re-core-2010070715.tar.bz2 archive, and I've tried to build the project. I have no problem compiling the Fiasco.OC kernel, but the L4Re core build seems to be entering an infinite loop. After running for a few seconds, I get the following lines repeated forever: All checked ok. scripts/kconfig/conf -s [l4dir]/mk/Kconfig scripts/kconfig/conf -s [l4dir]/mk/Kconfig make[11]: Nothing to be done for `all'. I also noticed that I get this same infinite loop if I do make config (after the menu exits) or make oldconfig. Something about the post-config clean-up seems to be continuously forking new processes and looping. The comment at line 179 of the [l4dir]/Makefile indicates that make is called again for postprocessing, but I don't know make well enough to debug this problem. Any ideas what's causing the problem? I've included the output below for reference. Thanks, Michael Kirkpatrick $ tar xf l4re-core-2010070715.tar $ cd l4re-core-2010070715/src/l4 $ make B=builddir --no-print-directory All checked ok. Creating build directory "builddir"... HOSTCC scripts/basic/fixdep HOSTCC scripts/basic/docproc HOSTCC scripts/basic/hash HOSTCC scripts/kconfig/conf.o [l4dir]/tool/kconfig/scripts/kconfig/conf.c: In function 'conf_askvalue': [l4dir]/tool/kconfig/scripts/kconfig/conf.c:105: warning: ignoring return value of 'fgets', declared with attribute warn_unused_result [l4dir]/tool/kconfig/scripts/kconfig/conf.c: In function 'conf_choice': [l4dir]/tool/kconfig/scripts/kconfig/conf.c:307: warning: ignoring return value of 'fgets', declared with attribute warn_unused_result HOSTCC scripts/kconfig/kxgettext.o SHIPPED scripts/kconfig/zconf.tab.c SHIPPED scripts/kconfig/lex.zconf.c SHIPPED scripts/kconfig/zconf.hash.c HOSTCC scripts/kconfig/zconf.tab.o HOSTLD scripts/kconfig/conf scripts/kconfig/conf -o [l4dir]/mk/Kconfig # # configuration written to .kconfig # scripts/kconfig/conf -s [l4dir]/mk/Kconfig scripts/kconfig/conf -s [l4dir]/mk/Kconfig scripts/kconfig/conf -s [l4dir]/mk/Kconfig scripts/kconfig/conf -s [l4dir]/mk/Kconfig All checked ok. scripts/kconfig/conf -s [l4dir]/mk/Kconfig gcc -fPIC -Wall -pedantic -g -m32 -c [l4dir]/tool/gendep/deptrack.c -o [l4dir]/builddir/tool/gendep/deptrack.32.o gcc -fPIC -Wall -pedantic -g -m32 -c [l4dir]/tool/gendep/syscall.c -o [l4dir]/builddir/tool/gendep/syscall.32.o mkdir -p [l4dir]/builddir/tool/gendep/32 gcc -m32 -shared -Wl,-soname,[l4dir]/builddir/tool/gendep/32/libgendep.so -ldl -o [l4dir]/builddir/tool/gendep/32/libgendep.so [l4dir]/builddir/tool/gendep/deptrack.32.o [l4dir]/builddir/tool/gendep/syscall.32.o scripts/kconfig/conf -s [l4dir]/mk/Kconfig scripts/kconfig/conf -s [l4dir]/mk/Kconfig scripts/kconfig/conf -s [l4dir]/mk/Kconfig All checked ok. scripts/kconfig/conf -s [l4dir]/mk/Kconfig scripts/kconfig/conf -s [l4dir]/mk/Kconfig All checked ok. scripts/kconfig/conf -s [l4dir]/mk/Kconfig make[11]: Nothing to be done for `all'. scripts/kconfig/conf -s [l4dir]/mk/Kconfig scripts/kconfig/conf -s [l4dir]/mk/Kconfig All checked ok. scripts/kconfig/conf -s [l4dir]/mk/Kconfig ^Cmake[12]: *** Deleting file `[l4dir]/builddir/.config.all' make[15]: *** [silentoldconfig] Interrupt make[14]: *** [sub-make] Interrupt make[13]: *** [[l4dir]/builddir/.kconfig.auto] Interrupt make[12]: *** [[l4dir]/builddir/.config.all] Interrupt make[11]: *** [DROPSCONF_CONFIG_MK_POST_HOOK] Interrupt make[10]: *** [[l4dir]/builddir/.config.all] Interrupt make[9]: *** [DROPSCONF_CONFIG_MK_POST_HOOK] Interrupt make[8]: *** [[l4dir]/builddir/.config.all] Interrupt make[7]: *** [DROPSCONF_CONFIG_MK_POST_HOOK] Interrupt make[6]: *** [[l4dir]/builddir/.config.all] Interrupt make[5]: *** [[l4dir]/builddir/.config.all] Interrupt make[4]: *** [DROPSCONF_CONFIG_MK_POST_HOOK] Interrupt make[3]: *** [[l4dir]/builddir/.config.all] Interrupt make[2]: *** [[l4dir]/builddir/.config.all] Interrupt make[1]: *** [oldconfig] Interrupt make: *** [all] Interrupt

3 3

L4Re and Fiasco.OC on amd64
by Taru Karttunen 02 Aug '10

02 Aug '10

Hello I am trying to compile Fiasco.OC and L4Re on amd64, but the kernel fails to boot for some reason. Steps taken: 1) Checked out source from SVN 2) Compiled fiasco, make config, set amd64, make 3) Compiled L4Re (and set to amd64) 4) Created hello.iso with make grub1iso E=hello MODULE_SEARCH_PATH=bin/amd64_K8:~/l4r4/fiasco-build 5) Try to boot it with qemu-system-x86_64 -cdrom images/hello.iso -no-reboot -no-shutdown -cpu phenom 6) Fiasco crashes with http://aoi.yi.org/~taruti/crash.png Here is info on the repository: hydra:fiasco$ svn info Path: . URL: http://svn.tudos.org/repos/oc/tudos/trunk/kernel/fiasco Repository Root: http://svn.tudos.org/repos/oc/tudos Repository UUID: d050ee49-bd90-4346-b210-929a50b99cfc Revision: 11 Node Kind: directory Schedule: normal Depth: empty Last Changed Author: l4check Last Changed Rev: 11 Last Changed Date: 2010-07-07 12:49:37 +0300 (Wed, 07 Jul 2010) How do I debug this further? - Taru Karttunen

2 3

l4vfs and stdin/stdout handles
by Valery V. Sedletski 02 Jul '10

02 Jul '10

Hi all. I am trying to make a test using l4vfs libc backends so the three predefined file descriptors 0, 1, 2 work for stdin, stdout and stderr correspondingly. It appears that these file descriptors are already predefined for some purpose: when I am trying to open files like this: // open initial file descriptors // stdin fd = open("/vc/vc0", O_RDONLY); LOG("stdin: fd=%d, errno=%d", fd, errno); // strout fd = open("/vc/vc0", O_WRONLY); LOG("stdout: fd=%d, errno=%d", fd, errno); // stderr fd = open("/vc/vc0", O_WRONLY); LOG("stderr: fd=%d, errno=%d", fd, errno); -- like in term_con_test example for term_con server, the 3, 4, 5 descriptors are returned from open(). If I not use term_con at all, and not open vc0 three times as above, read(0, ....); and write(1,....); works but strangely. For example, read() returns immediately with no error and returns a single symbol (EOF, I think). But as I tested in Linux and OS/2 operating systems, when stdin is a console, read(0,...); must block until '\n' is returned (user pressed an Enter key). So, it seems that the file descriptors 0, 1, 2 are reserved, but they are not working as expected. Maybe, my setup is incorrect or something is not yet implemented? I have a menu.lst entry like this: title The "Hello, world!" program kernel $(A)/bootstrap -serial modaddr 0x02000000 module $(B)/fiasco $(FIASCOARGS) module $(B)/sigma0 module $(B)/roottask \ task modname 'simple_file_server' attached 6 modules module $(B)/log module $(B)/names module $(B)/dm_phys module $(B)/l4io module $(B)/rtc module $(B)/l4con module $(B)/simple_ts -t 300 module $(B)/name_server module $(B)/term_con module $(B)/simple_file_server -v 14 module $(B)/os2/config.sys module $(B)/os2/mini33.exe module $(B)/os2/minicmd.exe module $(B)/os2/msg.dll module $(B)/os2/doscalls.dll module $(B)/os2/sub32.dll module $(B)/fstab \ -c /file \ -c /file/system -v 14 -b / -m /file/system \ -c /vc -v 132 -b / -m /vc module $(B)/os2/os2server -d c: -m /file/system vbeset $(VBE_MODE) I needed to relink a term_con server to an address 0x01450000 instead of the default one of 0x01400000 because the latter was the same as with simple_ts server (0x01400000 too). I was not able to use loader server to load at other address because I needed to launch two l4vfs servers, term_con and simple_file_server where simple_file_server serves all files through fprov_proxy file provider (I don't want to use an extra bmodfs server to serve files for loader -- it would be an ugly decision, I think). The 'os2server' server uses the files that were served by simple_file_server and it tries to use l4vfs servers for reading from stdin. My makefile looks like this: PKGDIR ?= ../.. L4DIR ?= $(PKGDIR)/../.. TARGET = os2server # the default relocation address. This may be superseded by a STATIC file. DEFAULT_RELOC = 0x01800000 # list your .c files here # os2server.c SRC_C = main.c utility.c io.c MountReg.c globals.c native_dynlink.c l4_alloc_mem.c \ Shared/token.c \ Shared/modmgr.c \ Shared/ixfmgr.c \ Shared/ixfmgr_lx.c \ Shared/ixfmgr_lx_load.c \ Shared/ixfmgr_ne.c \ Shared/ixfmgr_lx_fixuplx.c \ Shared/ixfmgr_lx_loadobjlx.c \ Shared/ixfmgr_lx_modlx.c \ Shared/ixfmgr_lx_execlx.c \ Shared/ixfmgr_lx_debuglx.c \ Shared/memmgr.c \ Shared/api/apistub.c \ Shared/cfgparser.c \ Shared/processmgr.c #Shared/ow_dlfcn.c \ # if your server implements the server side of an idl defined in an idl-file # of your package, list the idl file name(s) here (no path needed) SERVERIDL = os2server.idl # list additional library paths and libraries here LIBS = -los2server -lparsecmdline -lthread -lcon -lcontxt -lconstream-server CFLAGS = -I$(PKGDIR)/include MODE=l4env_base include $(L4DIR)/mk/prog.mk Maybe some libs are interfere with l4vfs ones or something like this? I suspect the l4con server libs interfere with l4vfs libs. For example, l4con has its own getchar() implementation but in uCLibc this function is implemented through l4vfs backends. When I am trying to use getchar() or scanf() functions, I see that read() function is called behind the scenes, and it don't get blocked until Enter is pressed. So, any help is appreciated. WBR, valery

2 5

l4vfs and opendir()/readdir()
by Valery V. Sedletski 20 Jun '10

20 Jun '10

Hi all. I am trying to mount a flat file system by simple_file_server in l4vfs tree and then navigating over the file systen, i.e. opening/reading the root directory by opendir()/readdir(), searching the files in the directory and then opening them by open(). Doing this, I found that opendir() sometimes fails, trying to allocate a big (almost 2 gigabytes) dataspace at dm_phys. When I tried to compile my program and l4vfs servers with debug output, I had seen that this is done by calloc() function in opendir() function in l4\pkg\uclibc\lib\contrib\uclibc\libc\misc\dirent\opendir.c: if (!(ptr->dd_buf = calloc(1, ptr->dd_max))) { free(ptr); nomem_close_and_ret: close(fd); __set_errno(ENOMEM); return NULL; } before that, it makes fstat() and assigns ptr->dd_max to a FS block size from the stat buffer. After looking into l4vfs backends and simple_file_server, I had seen that the FS block size is left undefined, so it tried to use a big random value which appeared to be in a stat buffer. So, the fix can be simple -- set FS blksize to something (I set it to 512 bytes). And also, I added copying of that size from the stat buffer in stat() and fstat() functions in libc l4vfs io backend. So, my patch is attached to this letter WBR, valery

1 0

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