Re: strance error when running Nova + Genode + Seoul (scenarion : seoul-auto.run)

[Parfait Tokponnon]

Hi Alexander,
That's correct, when I had set the timeout to 600, it ran perfectly.
Concerning the layers of virtualization, I understand well your concerns.
It was just for trying purpose.
Really, I am already considering moving to a real development platform and
let the Linux VM.
Regards,

2015-10-14 18:07 GMT+02:00 Alexander Boettcher <
alexander.boettc...@genode-labs.com>:

> Hi,
>
> On 14.10.2015 12:44, Parfait Tokponnon wrote:
> > Yes, I am running Ubuntu from within a VM (VirtualBox). Is there any
> > problem related to it? I didn't know we cannot test the platform from
> > within a VM...
>
> developing within a VM is no issue, but actually running the result from
> within a VM is adventurous - at least - most the time, based on
> practical experience.
>
> In your case you have 3 level of virtualization/emulation nested - you
> are running Ubuntu in Virtualbox (1), then you run Genode/Nova inside
> Qemu (2) ontop of (1) and finally you run a Linux VM with Seoul VMM (3)
> on top of (2).
>
> Beside the obviously waste of CPU time and increasing your idle time,
> you have to rely on all upper levels to work correctly. Such a
> assumption and in principal such a development setup just leads to
> various types of frustrations - I would try to avoid that.
>
> >
> > And Yes, when I had invoked qemu directly with the provided command in
> the
> > log file it worked too.
> > So what could be the explanation?
>
> Our run tool sets for automatically tested scripts (as seoul-auto.run) a
> timeout until it must have been finished. Since you say it works for you
> when you are calling qemu directly - it could be that the execution time
> in your 3-level nested virtualization setup is too short.
>
> You may try to increase the timeout in seoul-auto.run (search for
> run_genode_until) or try using seoul-net.run instead, which is mainly
> the same setup but without timeout.
>
> Does this change things for you ?
>
> If not, you would have to find out why tcl/expect stops working with a
> eof (in /tool/run/run) error when waiting for qemu output.
>
>
>
> Regards,
>
> Alex.
>
>
> --
> ___
> genode-main mailing list
> genode-main@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/genode-main
>



-- 
Parfait T.
--
___
genode-main mailing list
genode-main@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/genode-main

Re: strance error when running Nova + Genode + Seoul (scenarion : seoul-auto.run)

[Parfait Tokponnon]

Hello,

Thank you for your reply. I had some trouble with my system, that is why i
didn't reply you earlier...

Yes, I am running Ubuntu from within a VM (VirtualBox). Is there any
problem related to it? I didn't know we cannot test the platform from
within a VM...

And Yes, when I had invoked qemu directly with the provided command in the
log file it worked too.

So what could be the explanation?

Regards,


PS: sorry for the duplication, i have used the wrong mail account prevously!

2015-10-12 11:49 GMT+02:00 Alexander Boettcher <
alexander.boettc...@genode-labs.com>:

> Hello,
>
> On 09.10.2015 21:06, Parfait Tokponnon wrote:
> > Hello,
> > Can anyone help out?
>
> may you please try to invoke the resulting iso file with qemu directly
> without using our run tool? Change "spawn qemu-system-x86_64 -cpu ..."
> (see log file) to "qemu-system-x86_64 -cpu ..." and call it from within
> the build directory. What is the (error) output of qemu ?
> Do you are running Ubuntu 12.04 from within a VM ?
>
> Regards,
>
> Alex.
>
>
>
> --
> ___
> genode-main mailing list
> genode-main@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/genode-main
>



-- 
Parfait T.
--
___
genode-main mailing list
genode-main@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/genode-main

strance error when running Nova + Genode + Seoul (scenarion : seoul-auto.run)

[Parfait Tokponnon]

Hello,
Can anyone help out?
I ran the "make run/seoul-auto.run" in my nova_x86_64 build directory and
nearly at the end of the process i got this error: make: ***
[run/seoul-auto] Erreur 253 (please find below a sample of the trace from
the serial output) I also attached the complete trace.
Can anyone help me solve the problem? I work on Ubuntu 12.04.

//error
...
...

[init -> seoul] VMM: #   rtc_cmos rtc_cmos: setting system clock to
2015-10-09 17:16:38 UTC (110998)
[init -> seoul] VMM: #   RAMDISK: ext2 filesystem found at block 0
[init -> seoul] VMM: #   RAMDISK: Loading 20704KiB [1 disk] into ram
disk... /
[init -> seoul] VMM: # |   /
[init -> seoul] VMM: # |   /
[init -> seoul] VMM: # |   /
[init -> seoul] VMM: # |   /
[init -> seoul] VMM: # |   /
[init -> seoul] VMM: # |   /
[init -> seoul] VMM: # |   /
[init -> seoul] VMM: # |   /
[init -> seoul] VMM: # |   /
[init -> seoul] VMM: # |   /
[init -> seoul] VMM: # |   /
[init -> seoul] VMM: # |   /
[init -> seoul] VMM: # |   /
[init -> seoul] VMM: # |   /
[init -> seoul] VMM: # |   /
Booting Core 4.7.7
[init -> seoul] VMM: #   Running Linux Kernel 3.1.0.
[init -> seoul] VMM: #   Checking boot options...Done.
[init -> seoul] VMM: #   Starting udev daemon for hotplug support...|
[init -> seoul] VMM: # |  Done.
[init -> seoul] VMM: #   modprobe: chdir(3.1.0): No such file or directory
[init -> seoul] VMM: #   modprobe: chdir(3.1.0): No such file or directory
Error: Spawned process died unexpectedly
make: *** [run/seoul-auto] Erreur 253


-- 
Parfait T.
$ make run/seoul-auto
including /home/parfait/git/Genode/genode/tool/run/boot_dir/nova
including /home/parfait/git/Genode/genode/tool/run/power_on/qemu
including /home/parfait/git/Genode/genode/tool/run/log/qemu
including /home/parfait/git/Genode/genode/tool/run/image/iso
including /home/parfait/git/Genode/genode/repos/ports/run/seoul-auto.run
building targets: core init drivers/timer drivers/rtc drivers/input app/seoul 
drivers/nic drivers/framebuffer drivers/platform drivers/acpi server/report_rom 
drivers/platform/spec/x86/device_pd
spawn make core init drivers/timer drivers/rtc drivers/input app/seoul 
drivers/nic drivers/framebuffer drivers/platform drivers/acpi server/report_rom 
drivers/platform/spec/x86/device_pd
make[1]: entrant dans le répertoire « 
/home/parfait/git/Genode/genode/build/nova_x86_64 »
checking library dependencies...
Skip target app/seoul/spec/32bit because it requires 32bit
Skip target drivers/framebuffer/spec/exynos because it requires exynos
Skip target drivers/framebuffer/spec/imx53 because it requires imx53
Skip target drivers/framebuffer/spec/omap4 because it requires omap4
Skip target drivers/framebuffer/spec/pl11x/pbxa9 because it requires pl11x pbxa9
Skip target drivers/framebuffer/spec/rpi because it requires rpi
Skip target drivers/framebuffer/spec/sdl because it requires linux sdl
Skip target drivers/input/spec/imx53 because it requires imx53
Skip target drivers/input/spec/ps2/pl050 because it requires pl050
Skip target drivers/nic/spec/lan9118 because it requires lan9118
Skip target drivers/nic/spec/linux because it requires linux
Skip target drivers/platform/spec/arndale because it requires arndale
Skip target drivers/platform/spec/imx53 because it requires imx53
Skip target drivers/platform/spec/odroid_x2 because it requires odroid_x2
Skip target drivers/platform/spec/rpi because it requires rpi
  Library platform
  Library cxx
  Library syscall
  Library startup
  Library base-common
  Library core
  Program core/core
COMPILE  version.o
LINK core
  Library base
  Program drivers/acpi/spec/x86/acpi_drv
  Library blit
  Library x86emu
  Library config
  Program drivers/framebuffer/vesa/fb_drv
  Library server
  Program drivers/input/dummy/dummy_input_drv
  Program drivers/input/spec/ps2/x86/ps2_drv
  Library dde_ipxe_nic
  Program drivers/nic/nic_drv
  Program drivers/platform/spec/x86/device_pd/device_pd
  Program drivers/platform/spec/x86/platform_drv
  Program drivers/rtc/spec/x86/rtc_drv
  Library alarm
  Library timer
  Program drivers/timer/timer
  Library init_pd_args
  Program init/init
  Program server/report_rom/report_rom
  Library seoul_libc_support
  Program app/seoul/spec/64bit/seoul
make[1]: quittant le répertoire « 
/home/parfait/git/Genode/genode/build/nova_x86_64 »
genode build completed
building targets:  kernel 
spawn make kernel
make[1]: entrant dans le répertoire « 
/home/parfait/git/Genode/genode/build/nova_x86_64 »
checking library dependencies...
  Program kernel/hypervisor
make[1]: quittant le répertoire « 
/home/parfait/git/Genode/genode/build/nova_x86_64 »
genode build completed
using NOVA kernel at 
/home/parfait/git/Genode/genode/build/nova_x86_64/kernel/hypervisor
install bootloader
creating ISO image...
Warning: -follow-links does not always work correctly; be careful.
Size of boot image is 4 sectors -> No emulation
 71.69% done, estimate finish Fri Oct  9 19:16:10 2015
Total translation table size: 2048
Total 

Re: Running Heeselicht scenario on qemu

[Parfait Tokponnon]

Hello Stefan,

Le 27 juil. 2016 08:10, "Stefan Kalkowski" <stefan.kalkow...@genode-labs.com>
a écrit :

> Hello Parfait,
>
> On 07/26/2016 01:07 PM, Parfait Tokponnon wrote:
> > Hello everybody;
> > I has been fed up with restarting my computer after every compilation
> > so, I have decided to try running the Heeselicht scenarion on qemu
> > (not very wise but just to speed the development process).
> > But I got some errors concerning  acpi table parsing, resulting in the
> > intel framebuffer not well detected.
> > So because I am very poor in qemu mastering, may someone tell me
> > whether it would take a lot of work to port the heeselicht scenario on
> > qemu? Or join me on doing this?
> > Any help is welcome (Here is the log file for those who are interested)
> >
>
> I can understand that rebooting after every change is frustrating, but
> at least if you do not touch components that are started during the
> first boot stage, it is enough to copy them to the USB stick (e.g. from
> the guest OS via shared folders). Everything that is started dynamically
> by the cli_monitor is read on demand from the USB sticks filesystem.
>
> What I am doing reside essentially in the kernel. Basically, I am trying
to introduce support for user-space thread redundancy (to achieve fault
tolerance against transient error) in the kernel and analyzing the latency
induced in the whole system as complete OS. So i really need to restart the
machine.


> Anyway, trying to run the Heeselicht scenario within QEMU in my eye
> indeed is not recommendable. All the driver configuration is different
> (no WIFI, other graphics card), using hardware-assisted virtualization
> within QEMU is *slow* and not actively used by us - with other words not
> tested. In the end you have to change different drivers within your
> configuration, with the result of a different setup. So you won't test
> whast is not working on your hardware, but what is not working in tour
> QEMU setup ;-).
>
>

Good to know it. Ok, thanks


> Best regards
> Stefan
>
> >
> >
> >
> --
> > What NetFlow Analyzer can do for you? Monitors network bandwidth and
> traffic
> > patterns at an interface-level. Reveals which users, apps, and protocols
> are
> > consuming the most bandwidth. Provides multi-vendor support for NetFlow,
> > J-Flow, sFlow and other flows. Make informed decisions using capacity
> planning
> > reports.http://sdm.link/zohodev2dev
> >
> >
> >
> > ___
> > genode-main mailing list
> > genode-main@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/genode-main
> >
>
> --
> Stefan Kalkowski
> Genode Labs
>
> https://github.com/skalk · http://genode.org/
>
>
> --
> What NetFlow Analyzer can do for you? Monitors network bandwidth and
> traffic
> patterns at an interface-level. Reveals which users, apps, and protocols
> are
> consuming the most bandwidth. Provides multi-vendor support for NetFlow,
> J-Flow, sFlow and other flows. Make informed decisions using capacity
> planning
> reports.http://sdm.link/zohodev2dev
> ___
> genode-main mailing list
> genode-main@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/genode-main
>
--
___
genode-main mailing list
genode-main@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/genode-main

Running Heeselicht scenario on qemu

[Parfait Tokponnon]

Hello everybody;
I has been fed up with restarting my computer after every compilation
so, I have decided to try running the Heeselicht scenarion on qemu
(not very wise but just to speed the development process).
But I got some errors concerning  acpi table parsing, resulting in the
intel framebuffer not well detected.
So because I am very poor in qemu mastering, may someone tell me
whether it would take a lot of work to port the heeselicht scenario on
qemu? Or join me on doing this?
Any help is welcome (Here is the log file for those who are interested)
-- 
Parfait T.
$ qemu-system-x86_64 -boot d -hdb var/run/heeselicht.img -drive 
id=disk,file=/home/parfait/VirtualBox\ VMs/ubuntu14_64/ubuntu14_64.vdi,if=none 
-device ahci,id=ahci -device ide-drive,drive=disk,bus=ahci.0 -m 8192 -serial 
mon:stdio
WARNING: Image format was not specified for 'var/run/heeselicht.img' and 
probing guessed raw.
 Automatically detecting the format is dangerous for raw images, write 
operations on block 0 will be restricted.
 Specify the 'raw' format explicitly to remove the restrictions.
Bender: Hello World.
Need 023b8000 bytes to relocate modules.
Relocating to 7dc48000: 
Copying 2351636 bytes...
Copying 1384500 bytes...
Copying 1180356 bytes...
Copying 1049284 bytes...
Copying 679436 bytes...
Copying 677296 bytes...
Copying 454608 bytes...
Copying 90776 bytes...
Copying 461000 bytes...
Copying 451072 bytes...
Copying 210128 bytes...
Copying 504464 bytes...
Copying 1710488 bytes...
Copying 65328 bytes...
Copying 33824 bytes...
Copying 465016 bytes...
Copying 1281392 bytes...
Copying 450464 bytes...
Copying 421632 bytes...
Copying 151040 bytes...
Copying 412312 bytes...
Copying 534808 bytes...
Copying 1878064 bytes...
Copying 1228152 bytes...
Copying 130504 bytes...
Copying 425832 bytes...
Copying 433168 bytes...
Copying 443312 bytes...
Copying 454760 bytes...
Copying 470568 bytes...
Copying 440472 bytes...
Copying 572184 bytes...
Copying 452528 bytes...
Copying 575280 bytes...
Copying 457400 bytes...
Copying 582312 bytes...
Copying 448480 bytes...
Copying 452544 bytes...
Copying 171112 bytes...
Copying 165360 bytes...
Copying 66000 bytes...
Copying 1957520 bytes...
Copying 28904 bytes...
Copying 1125976 bytes...
Copying 703200 bytes...
Copying 1587808 bytes...
Copying 432256 bytes...
Copying 483248 bytes...
Copying 442336 bytes...
Copying 479160 bytes...
Copying 79720 bytes...
Copying 402904 bytes...
Copying 533400 bytes...
Copying 358192 bytes...
Copying 88464 bytes...
Copying 676688 bytes...
Copying 541936 bytes...
Copying 434104 bytes...
Copying 954112 bytes...
Copying 28595 bytes...
Copying 997480 bytes...
Copying 138776 bytes...


NOVA Microhypervisor v7-a1dc2f7 (x86_64): Jul 23 2016 11:26:11 [gcc 4.9.2]

[ 0] CORE:0:0:0 6:6:3:0 [0] QEMU Virtual CPU version 2.4.0
core
config
acpica
acpi_drv
ahci_drv
audio_drv
backdrop
cli_monitor
decorator
device_pd
file_terminal
floating_window_layouter
fs_rom
init
input_merger
intel_fb_drv
ld.lib.so
libc.lib.so
libc_pipe.lib.so
libcrypto.lib.so
libc_terminal.lib.so
libm.lib.so
libpng.lib.so
libssl.lib.so
mixer
nic_drv
nit_fb
nitpicker
part_blk
platform_drv
pointer
ps2_drv
ram_fs
report_rom
rom_filter
rtc_drv
rump_fs
rump_fs.lib.so
rump.lib.so
terminal
terminal_log
themed_decorator
timer
trace_subject_reporter
usb_drv
vbox_pointer
vfs_jitterentropy.lib.so
wifi_drv
wifi.lib.so
wm
wpa_driver_nl80211.lib.so
wpa_supplicant.lib.so
xray_trigger
zlib.lib.so
iwlwifi-6000-4.ucode
iwlwifi-6000g2a-6.ucode
iwlwifi-6000g2b-6.ucode
iwlwifi-7260-16.ucode
iwlwifi-7265-16.ucode
iwlwifi-7265D-16.ucode
iwlwifi-8000C-16.ucode
Genode 16.05-70-gcd1076a 
int main(): --- create local services ---
int main(): --- start init ---
int main(): transferred 8118 MB to init
Quota exceeded! amount=135168, size=4096, consumed=135168
Quota exceeded! amount=151552, size=8192, consumed=147456
Quota exceeded! amount=151552, size=8192, consumed=147456
[init] upgrading quota donation for Env::PD (8192 bytes)
Quota exceeded! amount=159744, size=4096, consumed=159744
Quota exceeded! amount=176128, size=4096, consumed=176128
Quota exceeded! amount=192512, size=4096, consumed=192512
Quota exceeded! amount=208896, size=4096, consumed=208896
Quota exceeded! amount=225280, size=4096, consumed=225280
Quota exceeded! amount=241664, size=4096, consumed=241664
[init -> acpica] wait for platform drv
[init -> acpi_drv] void Acpi_table::_parse_tables(T*, Genode::uint32_t) [with T 
= unsigned int; Genode::uint32_t = unsigned int]: Found MADT
[init -> acpi_drv] MADT IRQ 0 -> GSI 2 flags: 0
[init -> acpi_drv] MADT IRQ 5 -> GSI 5 flags: d
[init -> acpi_drv] MADT IRQ 9 -> GSI 9 flags: d
[init -> acpi_drv] MADT IRQ 10 -> GSI 10 flags: d
[init -> acpi_drv] MADT IRQ 11 -> GSI 11 flags: d
[init -> ahci_drv] --- Starting AHCI driver -> done right .-) --
[init -> wm_report_rom] parsing legacy  policies
[init -> wm_report_rom] parsing legacy  policies
[init -> cli_terminal] int main(int, char**): --- terminal service started ---
[init 

Heeselicht scenarion, cannot launch linux vm

[Parfait Tokponnon]

Hello Genode world,
I'm having this issue when trying to launch linux virtual machine in the
Heeselicht scenario. My machine is a Lenovo X230.

unresolvable exception 3, pd 'init -> cli_monitor -> linux -> vbox', thread
'EMT-1', cpu 0, ip=0x1103ca5, no signal handler
unresolvable exception 3, pd 'init -> cli_munresolvable exceptiononitor ->
linux -> vbox', thread 'EMT-2', cpu 0, ip=0x1103ca5, no signal handler
unresolvable exception 3, pd 'init -> cli_monitor -> linux -> vbox', thread
'EMT-3', cpu 0, ip=0x1103ca5, no signal handler
unresolvable exception 3, pd 'init -> cli_monitor -> linux -> vbox', thread
'VMPwrUp', cpu 0, ip=0x1103cdd, no signal handler
unresolvable exception 3, pd 'init -> cli_monitor -> linux -> vbox', thread
'EMT-0', cpu 0, ip=0x1103cdd, no signal handler

The complete output is attached hereby.
Can someone help me figure out what is going on?


-- 
Parfait T.
--
Attend Shape: An AT Tech Expo July 15-16. Meet us at AT Park in San
Francisco, CA to explore cutting-edge tech and listen to tech luminaries
present their vision of the future. This family event has something for
everyone, including kids. Get more information and register today.
http://sdm.link/attshape___
genode-main mailing list
genode-main@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/genode-main

Re: [Genode] Suggestion about mailing list subject

[Parfait Tokponnon]

Hello,
Personally, I think this is very useful,
I receive mails from various mailing lists and this is the best way I can
distinguish at a glance the origin of the mail.
cheers

2017-02-07 11:08 GMT+01:00 Christian Helmuth <
christian.helm...@genode-labs.com>:

> Hello Martín,
>
> On Mon, Jan 30, 2017 at 07:57:33AM -0500, Martin Iturbide wrote:
> > I was wondering if it can be useful to configure the mailing list to
> > include on the subject (before the text) something like [Genode] or
> > [Genode-Main] . I know that it is easy to set a rule and folder for the
> > mailing list messages on the mail client, but in some other cases I like
> to
> > identify visually and fast the messages that are from this mailing list
> in
> > a group of mails.
> >
> > This is just a thought, I don't know how hard or easy will be to
> configure
> > this on the sourceforge mailing lists.
>
> Technically this is pretty simple by means of the Mailman
> subject_prefix feature. I personally do not like all subject lines
> written by users of the list cluttered with some prefix text. But, if
> other members of the list also express their demand for this feature
> and there's no overly resistance voiced I would enable it
> nevertheless.
>
> Greets
> --
> Christian Helmuth
> Genode Labs
>
> https://www.genode-labs.com/ · https://genode.org/
> https://twitter.com/GenodeLabs · /ˈdʒiː.nəʊd/
>
> Genode Labs GmbH · Amtsgericht Dresden · HRB 28424 · Sitz Dresden
> Geschäftsführer: Dr.-Ing. Norman Feske, Christian Helmuth
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
> ___
> genode-main mailing list
> genode-main@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/genode-main
>



-- 
Parfait T.
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot___
genode-main mailing list
genode-main@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/genode-main

performance benchmark

[Parfait Tokponnon]

Hello all,
Is there any benchmark (performance) tool ready to run in Genode?
I am trying to introduce some redundant execution scheme into the Nova
kernel and I would like to have a hint of the performance impact (on Genode
components). Since it is an unfinished work, the demo is the only scenario
I can run now.
I have read about the trace session in 13.08 release which may help but I
failed to build the trace example scenario (to get some insight of the
feature)

*Here are the outputs*
In the master branch:
make run/trace
...
cp: cannot stat ‘bin/rpc_name’: No such file or directory
while executing
"exec cp bin/$binary [run_dir]/genode"
(procedure "copy_and_strip_genode_binaries_to_run_dir" line 4)
invoked from within
...

In the 13.08 release
make run/trace
Makefile:91: /mk/global.mk: No such file or directory
make: *** No rule to make target `/mk/global.mk'.  Stop.

I also read about the* TCP/IP Automated benchmarking* in 13.05 release.
In the master branch:
make run/network_test_nic_raw
Error: No run script for network_test_nic_raw

In the 13.05 release
Makefile:91: /mk/global.mk: No such file or directory
make: *** No rule to make target `/mk/global.mk'.  Stop.

Any suggestion is welcom.
-- 
Parfait T.
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot___
genode-main mailing list
genode-main@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/genode-main

Linking genode processes at different address space

[Parfait Tokponnon]

Dear Genode community,
I would like to know if there is a way to link Genode process (or
components) at different address spaces especially when building Heeselicht
scenario.
When playing with the kernel (Nova), I encounter some weird values from a
userland process, but which component exactly it is, i don't really know
since almost all of them are linked to the same virtual adress.
According to me, one way to deal with it would be to name each PD
(protection domain) in the kernel according to the Genode component they
belong to, but I think this would be a bit tedious.
So what I am projecting to do is to guess the component name from the
adress space they are executing in  (if they have different address space,
right?).
Any other idea is welcome.
Thanks

-- 
Parfait T.
--
Check out the vibrant tech community on one of the world's most 
engaging tech sites, SlashDot.org! http://sdm.link/slashdot___
genode-main mailing list
genode-main@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/genode-main

Re: Linking genode processes at different address space

[Parfait Tokponnon]

2016-10-18 16:31 GMT+01:00 Alexander Boettcher <
alexander.boettc...@genode-labs.com>:

> On 18.10.2016 11:16, Parfait Tokponnon wrote:
> > My real problem is this :
> > When an EC (Execution Context) traps into the kernel, how the kernel can
> > know which component it belongs to or which component originates this
> trap,
> > and when the kernel, returning to userspace, elects an EC, which
> component
> > this EC belongs to. I would like to get from the kernel at runtime the
> > component an Ec belongs to. Is it Possible?
>
> You will need to add your own support code in the kernel and Genode/NOVA
> to correlate things.
>
> If you haven't yet a fully high dynamic setup, I would advise to enable
> in the kernel the debug output in the beginning of
>
> sys_create_ec
> sys_create_pd
>
> and accordingly in Genode add debug output of the names of the process
> and thread before all occurrences of
>
> create_ec
> create_pd
>
> in repos/base-nova.
>
> With the information you are able to correlate EC and PD pointers in the
> kernel with Genode names for the process and threads.
>
> It works fine,
Thanks


> Hope it helps,
>
> Alex.
> --
> Alexander Boettcher
> 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
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
> ___
> genode-main mailing list
> genode-main@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/genode-main
>



-- 
Parfait T.
--
Check out the vibrant tech community on one of the world's most 
engaging tech sites, SlashDot.org! http://sdm.link/slashdot___
genode-main mailing list
genode-main@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/genode-main

Re: Beginner : VMM with genode

[Parfait Tokponnon]

The demo scenario does not include VMM execution.
Instead, start one of the seoul scenarios (seoul-fancy for example)

make run/seoul-fancy
>

To be able to run this command, priorly add (or uncomment) this line in
your build.conf

REPOSITORIES += $(GENODE_DIR)/repos/ports
>
May-be you will have to prepare some additional ports (depending on the
current state of your platform).
Cheers,


2018-02-19 11:51 GMT+01:00 jony jony :

> Actually , theres no init button , only a testinit
> i think i started the basic genode demo , i copied hypervisor and image
> files under /genode/var/run/demo to / folder and edited the file in grub.d
> as follow
> > root@ubuntu:/# cat /etc/grub.d/49_genode1
> > #!/bin/sh -e
> > echo "Genode@NOVA"
> > cat << EOF
> > menuentry "Genode@NOVA" {
> > insmod ext2
> > multiboot /hypervisor
> module image /image.elf
>
> and it started the genode demo that shows launchpad ; i have testinit,
> scout , launchpad, nitlog, liquid fb , nitpicker
>
> 2018-02-16 12:08 GMT+00:00 Alexander Boettcher <
> alexander.boettc...@genode-labs.com>:
>
>> Hi,
>> On 15.02.2018 15:08, jony jony wrote:
>> > i'm using an ubuntu virtual machine, and booted through dual boot
>> genode on
>> > a nova kernel , the interface that shows is very basic and only has
>> > launchpad ,
>>
>> you probably started the seoul-fancy run scenario. As soon as you click
>> on the blue entry called "init", a Seoul VMM + a VM will be started.
>>
>> > i want to use a virtual machine monitor on top of genode to run
>> > virtual machines , i copied the files ob repos/ports/run/*run  on the /
>> > folder and the following changes were made
>> > root@ubuntu:/#
>> > root@ubuntu:/# cat /etc/grub.d/49_genode1
>> > #!/bin/sh -e
>> > echo "Genode@NOVA"
>> > cat << EOF
>> > menuentry "Genode@NOVA" {
>> > insmod ext2
>> > multiboot /hypervisor
>> > module /seoul-auto.run
>> > module /seoul-disc.run
>> > module /seoul-fancy.run
>> > module /seoul-genode.run
>> > module /seoul-kernelbuild.run
>> > module /seoul-net.run
>>
>> This is not going to work. The *.run files are just scripts runnable on
>> your ubuntu machine - nothing you can boot directly.
>>
>> Again, as I suggested already some emails before:
>>
>>  Please consult the Genode Foundations book, which describes the
>>  framework and also _run_ mechanism in more detail.
>>
>> Cheers,
>>
>> --
>> Alexander Boettcher
>> Genode Labs
>>
>> http://www.genode-labs.com - http://www.genode.org
>>
>> Genode Labs GmbH - Amtsgericht Dresden - HRB 28424 - Sitz Dresden
>> Geschäftsführer: Dr.-Ing. Norman Feske, Christian Helmuth
>>
>> 
>> --
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>> ___
>> genode-main mailing list
>> genode-main@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/genode-main
>>
>
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> genode-main mailing list
> genode-main@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/genode-main
>
>


-- 
Parfait T.
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
genode-main mailing list
genode-main@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/genode-main