December 2009 - l4-hackers - example.com Site

[ANNOUNCE] NOVA Microhypervisor 0.1 prerelease
by Udo A. Steinberg 08 Mar '10

08 Mar '10

Hi, The NOVA project is happy to announce that there is a 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 Public License version 2. NOVA is based on a modern microhypervisor written in C++ and assembler. It currently supports x86-32 SMP platforms with hardware virtualization features, such as Intel VT-x 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. Like third-generation microkernels, the NOVA microhypervisor uses a capability-based authorization model and provides only basic mechanisms for spatial and temporal isolation, scheduling, communication and delegation of platform resources. Additional services are provided by an unprivileged multi-server user environment running on top of the microhypervisor. In NOVA, we implemented almost all of the virtualization functionality in a deprivileged user-level virtual-machine monitor. This design choice improves the overall security of the system, because exploitation of a bug in the platform virtualization code only compromises the VMM and leaves the remaining components unaffected. Cheers, - Udo

6 9

Re: l4-hackers Digest, Vol 80, Issue 11
by fang zhengshu 30 Dec '09

30 Dec '09

2009/12/29 <l4-hackers-request(a)os.inf.tu-dresden.de> > Send l4-hackers mailing list submissions to > l4-hackers(a)os.inf.tu-dresden.de > > To subscribe or unsubscribe via the World Wide Web, visit > http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers > or, via email, send a message with subject or body 'help' to > l4-hackers-request(a)os.inf.tu-dresden.de > > You can reach the person managing the list at > l4-hackers-owner(a)os.inf.tu-dresden.de > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of l4-hackers digest..." > > > Today's Topics: > > 1. Re: Problems running l4-linux in VMWare with SCSI Discs > (Adam Lackorzynski) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 28 Dec 2009 13:43:28 +0100 > From: Adam Lackorzynski <adam(a)os.inf.tu-dresden.de> > To: l4-hackers(a)os.inf.tu-dresden.de > Subject: Re: Problems running l4-linux in VMWare with SCSI Discs > Message-ID: <20091228124328.GB30342(a)os.inf.tu-dresden.de> > Content-Type: text/plain; charset=iso-8859-1 > > > On Sun Dec 27, 2009 at 12:40:11 +0800, fang zhengshu wrote: > > > scsi disk,and I try to create a ide disk ,then it can dectect the disk. > > so I think there is some problem with the vmware and the scsi. > > because I have enable the scsi disk. > > So do you have the appropriate SCSI driver in Linux enabled, i.e. the > (virtual) disk is detected? no,It can only detect the ide device.when I have a scsi disk and a ide cdrom, It can only test the ide cdrom. and when I create a ide disk,then it can detect the ide disk.but I have enable the scsi disk support. > > > > 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 > > > End of l4-hackers Digest, Vol 80, Issue 11 > ****************************************** > -- fang,

1 0

Re: l4-hackers Digest, Vol 80, Issue 8
by fang zhengshu 28 Dec '09

28 Dec '09

2009/12/26 <l4-hackers-request(a)os.inf.tu-dresden.de> > Send l4-hackers mailing list submissions to > l4-hackers(a)os.inf.tu-dresden.de > > To subscribe or unsubscribe via the World Wide Web, visit > http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers > or, via email, send a message with subject or body 'help' to > l4-hackers-request(a)os.inf.tu-dresden.de > > You can reach the person managing the list at > l4-hackers-owner(a)os.inf.tu-dresden.de > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of l4-hackers digest..." > > > Today's Topics: > > 1. Re: l4-hackers Digest, Vol 80, Issue 6 (Adam Lackorzynski) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 25 Dec 2009 17:24:48 +0100 > From: Adam Lackorzynski <adam(a)os.inf.tu-dresden.de> > To: l4-hackers(a)os.inf.tu-dresden.de > Subject: Re: l4-hackers Digest, Vol 80, Issue 6 > Message-ID: <20091225162448.GA18264(a)os.inf.tu-dresden.de> > Content-Type: text/plain; charset=iso-8859-1 > > > On Fri Dec 25, 2009 at 09:29:58 +0800, fang zhengshu wrote: > > I chage the command line "root=/dev/sda1" instead of "root=/dev/sda" > ,but > > there is still the error as the new attach! please look it. attach. > > > > > > > - the Linux booted only finds a VMware Virtual CDROM as hda, so there's > > > no sda device found, I'm not currently sure wheter VMware supports > > > SATA or not but you should make sure that VMware supplies a disk to > > > the guest, the Linux driver for that is compiled in and that the root= > > > option corresponds to that. > > > > > > > I'm sorry for not very clearly. If the VMware does not support the SATA, > how > > can it find the l4linux kernel and the other l4 modules??If you don't > agree , > > which must I select when configure the l4linux? > > Which type of disk did you configure in your VMware setup? > > scsi disk,and I try to create a ide disk ,then it can dectect the disk. so I think there is some problem with the vmware and the scsi. because I have enable the scsi disk. > > > 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 > > > End of l4-hackers Digest, Vol 80, Issue 8 > ***************************************** > -- fang,

3 2

Re: l4-hackers Digest, Vol 80, Issue 6
by fang zhengshu 25 Dec '09

25 Dec '09

2009/12/24 <l4-hackers-request(a)os.inf.tu-dresden.de> > Send l4-hackers mailing list submissions to > l4-hackers(a)os.inf.tu-dresden.de > > To subscribe or unsubscribe via the World Wide Web, visit > http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers > or, via email, send a message with subject or body 'help' to > l4-hackers-request(a)os.inf.tu-dresden.de > > You can reach the person managing the list at > l4-hackers-owner(a)os.inf.tu-dresden.de > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of l4-hackers digest..." > > > Today's Topics: > > 1. Re: append a correct "root=" boot option. Kernel panic, can > not find sda1 device (Adam Lackorzynski) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 24 Dec 2009 11:37:08 +0100 > From: Adam Lackorzynski <adam(a)os.inf.tu-dresden.de> > To: l4-hackers(a)os.inf.tu-dresden.de > Subject: Re: append a correct "root=" boot option. Kernel panic, can > not find sda1 device > Message-ID: <20091224103708.GA23132(a)os.inf.tu-dresden.de> > Content-Type: text/plain; charset=iso-8859-1 > > > On Thu Dec 24, 2009 at 17:04:11 +0800, fang zhengshu wrote: > > the attach of the last email is the movie of booting l4linux through > serial > > +hardisk > > and I put an attach which is the picture of the error. > > Two things: > - in the video it has 3 kernel command line parameters, one being > root=/dev/sda (without a '1'), check your config file > I chage the command line "root=/dev/sda1" instead of "root=/dev/sda" ,but there is still the error as the new attach! please look it. attach. > - the Linux booted only finds a VMware Virtual CDROM as hda, so there's > no sda device found, I'm not currently sure wheter VMware supports > SATA or not but you should make sure that VMware supplies a disk to > the guest, the Linux driver for that is compiled in and that the root= > option corresponds to that. > I'm sorry for not very clearly. If the VMware does not support the SATA, how can it find the l4linux kernel and the other l4 modules？If you don't agree , which must I select when configure the l4linux? thank you. > > > > > 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 > > > End of l4-hackers Digest, Vol 80, Issue 6 > ***************************************** > -- fang,

2 1

Re: append a correct "root=" boot option. Kernel panic, can not find sda1 device
by fang zhengshu 24 Dec '09

24 Dec '09

the attach of the last email is the movie of booting l4linux through serial +hardisk and I put an attach which is the picture of the error. any one can help me? thank you. 2009/12/24 fang zhengshu <fangzhsh07(a)gmail.com> > hi all, > I download the newest l4linux by using svn and use the x86-native_defconfig > to configure the l4linux > then modify some place: > process and the keyboard,vga > > then I can boot l4linux with the given drops-rd.rd through serial. > but when I use the same l4linux kernel to boot it on the national hardisk > throug serial. > I came across the following problem: > > Please append a correct "root=" boot option. Kernel panic - not syncing: > VFS: Unable to mount root fs on unknown-block(2,0) > I have enable the sata disk support! > I have following someone's step as the google: > > http://www.linuxquestions.org/questions/linux-kernel-70/kernel-panic-not-sy… > ... > but the error still exist! > > I do the things in vmware. > the menu.lst is: > > title l4linux26+serial > #my hardisk is /dev/sda1 > root (hd0,0) > kernel /boot/l4linux/bootstrap -serial -modaddr 0x02000000 > module /boot/l4linux/fiasco -nowait -nokdb -serial_esc \ > -comspeed 115200 -comport 1 > module /boot/l4linux/sigma0 > module /boot/l4linux/roottask task modname "bmodfs" attached 4 modules > module /boot/l4linux/names > module /boot/l4linux/log > module /boot/l4linux/dm_phys --isa=0x00800000 > module /boot/l4linux/simple_ts -t 300 > module /boot/l4linux/rtc > module /boot/l4linux/l4io > module /boot/l4linux/bmodfs > module /boot/l4linux/libld-l4.s.so > module /boot/l4linux/libloader.s.so > module /boot/l4linux/vmlinuzserial > module /boot/l4linux/l4linuxserial.cfg > module /boot/l4linux/loader --fprov=BMODFS l4linuxserial.cfg > > > the l4linuxserial.cfg is: > > modpath "(hd0,0)/boot/L4Linux" > task "vmlinuz" "earlyprintk=yes console=ttyLv0 init=/bin/sh mem=256M > l4ser.vkey_enable=1 root=/dev/sda1 ide_generic.probe_mask=0x3f" > all_sects_writable > allow_vga > > > thank you! > -- > fang, > > -- fang,

2 2

Codezero Microkernel v0.2 Released
by Bahadir Balban 07 Dec '09

07 Dec '09

I would like to announce that Codezero Microkernel v0.2 is released. On this release, the microkernel is now fully capability checked, and we introduced the notion of containers to provide isolated execution environments. Please see below for a brief description. 1.) Containers In Codezero containers provide the architectural infrastructure for isolation of execution environments. Each container is allocated with a set of address spaces, threads, and any other resource that would otherwise be globally available on the platform, such as virtual and physical memory. Using the simple notion of containers, it is possible to build any type of software design hierarchy. A hierarchical client/server design, or multi-threaded standalone applications are both possible scenarios. 2.) Capabilities Capabilities protect all resources maintained by the kernel. Currently, all system calls are protected by capabilities, except a few trivial ones that have been left out. Physical and virtual memory, typed memory pools, and inter-process communication are among other resources that are protected by capability checking. Capabilities build upon the foundation of containers, providing a fine-grained security architecture, inside and among container boundaries. We also introduced a capability control system call, by which the capabilities may be shared, granted and modified in different ways, enabling a highly flexible and configurable security architecture. 3.) Configuration We attempted to present the above two notions in an easily manageable kernel configuration system. Containers, their parameters and capabilities may be adjusted easily at configuration time, using our CML2-based kernel configuration system. We are aiming to evolve the L4 API into the future by feedback, hence this email post. Codezero Project is open with a GPLv3 license. If you are interested to learn more, download by: git-clone git://git.l4dev.org/codezero.git A useful jump-start guide: http://www.l4dev.org/doku.php?id=getting_started_quick API reference man pages: man -M codezero/docs/man pagename Thanks, -- Bahadir Balban

1 0

Problem compiling Fiasco Kernel (kip.cc)
by olivier 02 Dec '09

02 Dec '09

Hello all I'm currently trying compil current Fiasco Kernel under Cygwin, unfortunatly I have a problem of compilation. when compiler try compil kip.cc I have an assembler message that said: Error: junk at the end of line, first unrecognized character is ',' Any Idea? Thanks Olivier PS: my kip.cc // AUTOMATICALLY GENERATED -- DO NOT EDIT! -*- c++ -*- #include "kip.h" #include "kip_i.h" #line 47 "/tudos/kernel/fiasco/src/abi/kip.cpp" //============================================================================ #line 182 "/tudos/kernel/fiasco/src/abi/kip.cpp" //---------------------------------------------------------------------------- #line 188 "/tudos/kernel/fiasco/src/abi/kip.cpp" Kip *Kip::global_kip; #line 192 "/tudos/kernel/fiasco/src/abi/kip.cpp" asm(".section .initkip.version, \"a\", %progbits \n" \ ".string \"" CONFIG_KERNEL_VERSION_STRING "\" \n" \ ".previous \n"); #line 196 "/tudos/kernel/fiasco/src/abi/kip.cpp" asm(".section .initkip.features.fini, \"a\", %progbits \n" \ ".string \"\" \n" \ ".previous \n"); #line 110 "/tudos/kernel/fiasco/src/abi/kip.cpp" bool Kip::add_mem_region(Mem_desc const &md) { Mem_desc *m = mem_descs(); Mem_desc *end = m + num_mem_descs(); for (;m<end;++m) { if (m->type() == Mem_desc::Undefined) { *m = md; return true; } } // Add mem region failed -- must be a Fiasco startup problem. Bail out. assert (0); return false; } #line 130 "/tudos/kernel/fiasco/src/abi/kip.cpp" Mem_region Kip::last_free() const { Mem_desc const *m = mem_descs(); Mem_desc const *const end = m + num_mem_descs(); Mem_region r; r.start = 0; r.end = 0; for (;m<end;++m) { Address s = m->start(); Address e = m->end(); // Speep out stupid descriptors (that have the end before the start) if (s>=e) { const_cast<Mem_desc*>(m)->type(Mem_desc::Undefined); continue; } if (m->is_virtual()) // skip virtual memory descriptors continue; switch (m->type()) { case Mem_desc::Conventional: if (e>r.end) r.end = e; if (s>r.start) r.start = s; break; case Mem_desc::Reserved: case Mem_desc::Dedicated: case Mem_desc::Shared: case Mem_desc::Arch: case Mem_desc::Bootloader: if (e>=r.start && e<r.end) { r.start = e + 1; } if (s>=r.start && s<r.end) { r.end = s - 1; } break; default: break; } } return r; }

2 7