Re: Running Heeselicht scenario on qemu

2016-07-28 Thread Parfait Tokponnon 
Hello Stefan,

Le 27 juil. 2016 08:10, "Stefan Kalkowski" 
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

Re: Running Heeselicht scenario on qemu

2016-07-27 Thread Stefan Kalkowski 
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.

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

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

Running Heeselicht scenario on qemu

2016-07-26 Thread 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