headers
Adam Lackorzynski | 1 Dec 19:28
Picon
Favicon

Re: Problem compiling Fiasco Kernel (kip.cc)


On Tue Dec 01, 2009 at 00:15:29 +0100, olivier wrote:
> Hello,
> >>try do Makefile.sub2
> >>... Generating version information
> >>... Making kip.o
> >>cczEXyNz.s: Assembler messages:
> >>cczEXyNz.s: 117: Error: junk at end of line, first unrecognized
> >>character is ','
> >>cczEXyNz.s: 119: 119: unknown pseudo-op: '.previous'
> >>etc.
> >
> >Anyway, the .previous is the interesting information. This should be
> >processed by the assembler. Since this is on Windows maybe the '\n'
> >isn't enough and there must be a \n\r or similar. Could you try to add
> >the \r in kip.cpp and try again?
> 
> No change, I know now problem is in this lines:
> 
> 
> asm(".section .initkip.version, \"a\", %progbits        \n"    \
>    ".string \"" CONFIG_KERNEL_VERSION_STRING "\"       \n"    \
>    ".previous                                          \n");
> 
> asm(".section .initkip.features.fini, \"a\", %progbits  \n"    \
>    ".string \"\"                                       \n"    \
>    ".previous                                          \n");
> 
> 
> And more exactly start for compiler with the character ','  after
(Continue reading)

Permalink | Reply | 2 comments |
headers
olivier | 1 Dec 23:43
Picon
Favicon

Re: Problem compiling Fiasco Kernel (kip.cc)

Adam Lackorzynski a écrit :
> On Tue Dec 01, 2009 at 00:15:29 +0100, olivier wrote:
>   
>> Hello,
>>     
>>>> try do Makefile.sub2
>>>> ... Generating version information
>>>> ... Making kip.o
>>>> cczEXyNz.s: Assembler messages:
>>>> cczEXyNz.s: 117: Error: junk at end of line, first unrecognized
>>>> character is ','
>>>> cczEXyNz.s: 119: 119: unknown pseudo-op: '.previous'
>>>> etc.
>>>>         
>>> Anyway, the .previous is the interesting information. This should be
>>> processed by the assembler. Since this is on Windows maybe the '\n'
>>> isn't enough and there must be a \n\r or similar. Could you try to add
>>> the \r in kip.cpp and try again?
>>>       
>> No change, I know now problem is in this lines:
>>
>>
>> asm(".section .initkip.version, \"a\", %progbits        \n"    \
>>    ".string \"" CONFIG_KERNEL_VERSION_STRING "\"       \n"    \
>>    ".previous                                          \n");
>>
>> asm(".section .initkip.features.fini, \"a\", %progbits  \n"    \
>>    ".string \"\"                                       \n"    \
>>    ".previous                                          \n");
>>
(Continue reading)

Permalink | Reply | 1 comment |
headers
Adam Lackorzynski | 2 Dec 20:28
Picon
Favicon

Re: Problem compiling Fiasco Kernel (kip.cc)


On Tue Dec 01, 2009 at 23:43:19 +0100, olivier wrote:
> Adam Lackorzynski a écrit :
> >On Tue Dec 01, 2009 at 00:15:29 +0100, olivier wrote:
> >>Hello,
> >>>>try do Makefile.sub2
> >>>>... Generating version information
> >>>>... Making kip.o
> >>>>cczEXyNz.s: Assembler messages:
> >>>>cczEXyNz.s: 117: Error: junk at end of line, first unrecognized
> >>>>character is ','
> >>>>cczEXyNz.s: 119: 119: unknown pseudo-op: '.previous'
> >>>>etc.
> >>>Anyway, the .previous is the interesting information. This should be
> >>>processed by the assembler. Since this is on Windows maybe the '\n'
> >>>isn't enough and there must be a \n\r or similar. Could you try to add
> >>>the \r in kip.cpp and try again?
> >>No change, I know now problem is in this lines:
> >>
> >>
> >>asm(".section .initkip.version, \"a\", %progbits        \n"    \
> >>   ".string \"" CONFIG_KERNEL_VERSION_STRING "\"       \n"    \
> >>   ".previous                                          \n");
> >>
> >>asm(".section .initkip.features.fini, \"a\", %progbits  \n"    \
> >>   ".string \"\"                                       \n"    \
> >>   ".previous                                          \n");
> >>
> >>
> >>And more exactly start for compiler with the character ','  after
(Continue reading)

Permalink | Reply | 0 comments |
headers
Bahadir Balban | 7 Dec 13:52
Favicon

Codezero Microkernel v0.2 Released

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
(Continue reading)

Permalink | Reply | 0 comments |
headers
Udo A. Steinberg | 23 Dec 16:04
Favicon

[ANNOUNCE] NOVA Microhypervisor 0.1 prerelease

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
(Continue reading)

Permalink | Reply | 11 comments |
headers
fang zhengshu | 24 Dec 10:04
Picon

Re: append a correct "root=" boot option. Kernel panic, can not find sda1 device

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 <at> 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:
...
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,
_______________________________________________
l4-hackers mailing list
l4-hackers <at> os.inf.tu-dresden.de
http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
Permalink | Reply | 2 comments |
headers
fang zhengshu | 24 Dec 10:08
Picon

Re: append a correct "root=" boot option. Kernel panic, can not find sda1 device



2009/12/24 fang zhengshu <fangzhsh07 <at> gmail.com>
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.
sorry not for put the attach!
any one can help me?
thank you.


 
2009/12/24 fang zhengshu <fangzhsh07 <at> 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:
...
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,



--
fang,
_______________________________________________
l4-hackers mailing list
l4-hackers <at> os.inf.tu-dresden.de
http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
Permalink | Reply | 0 comments |
headers
Adam Lackorzynski | 24 Dec 11:37
Picon
Favicon

Re: append a correct "root=" boot option. Kernel panic, can not find sda1 device


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
- 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.

Adam
--

-- 
Adam                 adam <at> os.inf.tu-dresden.de
  Lackorzynski         http://os.inf.tu-dresden.de/~adam/
Permalink | Reply | 0 comments |
headers
Bernhard Kauer | 24 Dec 17:38
Picon
Favicon

[ANNOUNCE] NOVA Userland 0.1

The NOVA project is happy to announce that there is a prerelease of
NUL, the NOVA userland, available for download at

    http://os.inf.tu-dresden.de/~kauer/nova/ 

under the terms of GPLv2.

NUL is the multi-server user environment designed for NOVA.  It is
componentized into host-drivers, device models and virtual executors.
>From these components applications are build.  The most prominent apps
are the Partition Manager, called sigma0, and the x86 VMM
(Virtual-Machine Monitor) called Vancouver.

The VMM allows to run unmodified guest operating systems on top of the
microhypervisor.  It contains the virtual device models to give an OS
the illusion of running on bare hardware.  Furthermore it emulates
realmode and MMIO instructions and provides a virtual BIOS.

Furthermore, we prepared a Demo CD that shows NOVA in action, with
multiple VMs running Linux, L4/Fiasco and L4Ka::Pistachio.  The demo
runs on platforms that support Intel VT-x or AMD-V NPT. It can be
downloaded from

    http://os.inf.tu-dresden.de/~jsteckli/nova/NOVA-Xmas-Alpha.iso

Merry Christmas and happy hacking,

      Bernhard Kauer
Permalink | Reply | 2 comments |
headers
fang zhengshu | 25 Dec 02:29
Picon

Re: l4-hackers Digest, Vol 80, Issue 6



2009/12/24 <l4-hackers-request <at> os.inf.tu-dresden.de>
Send l4-hackers mailing list submissions to
       l4-hackers <at> 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 <at> os.inf.tu-dresden.de

You can reach the person managing the list at
       l4-hackers-owner <at> 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 <at> os.inf.tu-dresden.de>
To: l4-hackers <at> os.inf.tu-dresden.de
Subject: Re: append a correct "root=" boot option. Kernel panic, can
       not     find sda1 device
Message-ID: <20091224103708.GA23132 <at> 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 <at> os.inf.tu-dresden.de
 Lackorzynski         http://os.inf.tu-dresden.de/~adam/



------------------------------

_______________________________________________
l4-hackers mailing list
l4-hackers <at> 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,
_______________________________________________
l4-hackers mailing list
l4-hackers <at> os.inf.tu-dresden.de
http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
Permalink | Reply | 1 comment |

Gmane