users

users@lists.genode.org

3 participants
2349 discussions

Nova demo with GUI
by Chris Rothrock 03 May '17

03 May '17

In the release notes of Genode version 14.02 there is a screenshot of a GUI environment that has two VirtualBox windows, one running TinyCore, one running Windows 7 (https://genode.org/documentation/release-notes/14.02). How do I reproduce this example? When I run the make run/virtualbox demo there is no GUI (until I get into one guest OS GUI, TinyCore), there is only a text-based boot environment then the hand-off to VirtualBox in that text environment. I need to be able to successfully boot up into that GUI environment and demonstrate two distinct VM's are running. Any assistance in this effort would be greatly appreciated. -- Thank You, Chris Rothrock Senior System Administrator (315) 308-1637

3 3

Re: Re: Genode on i.MX6 (eMMC Flash)
by Kranthi Tej 03 May '17

03 May '17

Hello Stefan, Thank you for the quick response. Yes, I've been following the parallel thread and I've made the necessary changes in the "/repos/base/include/spec/imx6/drivers/board_base.h" file. I've set the following values: *UART_1_IRQ = 57,UART_1_MMIO_BASE = 0x021e8000,* *RAM0_SIZE = 0x20000000,* It turns out I was flashing it the wrong way. I've fixed it by drawing insights from how Android is currently being flashed onto the device. I've followed a similar procedure. After installing the bootloader, I've flashed the Genode uImage (generated using RUN_OPT += --include image/uboot) onto the device as per your advice. Flashing was successfully done. Upon booting up, I got the following: U-Boot 2009.08-dirty (Jul 08 2016 - 12:21:39) CPU: Freescale i.MX6 family TO1.5 at 792 MHz Thermal sensor with ratio = 175 Temperature: 37 C, calibration data 0x5534ce69 mx6q pll1: 792MHz mx6q pll2: 528MHz mx6q pll3: 480MHz mx6q pll8: 50MHz ipg clock : 66000000Hz ipg per clock : 66000000Hz uart clock : 80000000Hz cspi clock : 60000000Hz ahb clock : 132000000Hz axi clock : 264000000Hz emi_slow clock: 132000000Hz ddr clock : 528000000Hz usdhc1 clock : 198000000Hz usdhc2 clock : 198000000Hz usdhc3 clock : 198000000Hz usdhc4 clock : 198000000Hz nfc clock : 24000000Hz Board: i.MX6Q-SABRESD: unknown-board Board: 0x63015 [POR ] Boot Device: MMC HAB Configuration: 0xf0, HAB State: 0x66 --------- HAB Event 1 ----------------- event data: 0xdb 0x00 0x1c 0x41 0x33 0x18 0xc0 0x00 0xca 0x00 0x14 0x00 0x02 0xc5 0x00 0x00 0x00 0x00 0x0d 0x34 0x27 0x80 0x04 0x00 0x00 0x13 0xec 0x00 --------- HAB Event 2 ----------------- event data: 0xdb 0x00 0x14 0x41 0x33 0x0c 0xa0 0x00 0x00 0x00 0x00 0x00 0x27 0x80 0x04 0x00 0x00 0x00 0x00 0x20 --------- HAB Event 3 ----------------- event data: 0xdb 0x00 0x14 0x41 0x33 0x0c 0xa0 0x00 0x00 0x00 0x00 0x00 0x27 0x80 0x04 0x2c 0x00 0x00 0x02 0xa0 --------- HAB Event 4 ----------------- event data: 0xdb 0x00 0x14 0x41 0x33 0x0c 0xa0 0x00 0x00 0x00 0x00 0x00 0x27 0x80 0x04 0x20 0x00 0x00 0x00 0x01 --------- HAB Event 5 ----------------- event data: 0xdb 0x00 0x14 0x41 0x33 0x0c 0xa0 0x00 0x00 0x00 0x00 0x00 0x27 0x80 0x06 0xe0 0x00 0x00 0x00 0x04 I2C: ready DRAM: 1 GB MMC: FSL_USDHC: 0,FSL_USDHC: 1,FSL_USDHC: 2,FSL_USDHC: 3 *** Warning - bad CRC or MMC, using default environment In: serial Out: serial Err: serial Found PFUZE100! deviceid=10,revid=11 Net: got MAC address from IIM: 00:00:00:00:00:00 FEC0 [PRIME] Hit any key to stop autoboot: 0 booti: bad boot image magic fastboot is in init......flash target is MMC:3 wait usb cable into the connector! So, I've tried to write the image at an address and have loaded it from there. I've did the following in the uboot prompt: MX6Q SABRESD U-Boot > ext2load mmc 3:1 0x30000000 uImage Loading file "uImage" from mmc device 3:1 (xxd1) 594591 bytes read MX6Q SABRESD U-Boot > bootm 0x30000000 ## Booting kernel from Legacy Image at 30000000 ... Image Name: Image Type: ARM Linux Kernel Image (gzip compressed) Data Size: 594527 Bytes = 580.6 kB Load Address: 10001000 Entry Point: 10001000 Verifying Checksum ... OK Uncompressing Kernel Image ... OK Starting kernel ... It stops here (even after adjusting the *UART* settings before building the image). I've also tried *UART1* *(0x02020000)*, *UART3* (*0x021ec000*), *UART4* *(**0x021f0000**)* and *UART5 (**0x021F4000**) *with the same interrupt values. I've built the uImage for log (make run/log) and demo (make run/demo). I'm facing the same issue. I'm unable to find the source of the problem. Can you give me any leads on the possible problems? Thanks, Kranthi On Thu, Apr 6, 2017 at 12:07 AM, Kranthi Tej <ee13b037@...484...> wrote: > Hello Stefan, > > Thank you for the quick response. > > Yes, I've been following the parallel thread and I've made the necessary > changes in the "/repos/base/include/spec/imx6/drivers/board_base.h" file. > I've set the following values: > UART_1_IRQ = 57, > UART_1_MMIO_BASE = 0x021e8000, > RAM0_SIZE = 0x20000000. > > It turns out I was flashing it the wrong way. I've fixed it by drawing > insights from how Android is currently being flashed onto the device. I've > followed a similar procedure. After installing the bootloader, I've flashed > the Genode uImage (generated using RUN_OPT += --include image/uboot) onto > the device as per your advice. Flashing was successfully done. Upon booting > up, I got the following: > > U-Boot 2009.08-dirty (Jul 08 2016 - 12:21:39) > > CPU: Freescale i.MX6 family TO1.5 at 792 MHz > Thermal sensor with ratio = 175 > Temperature: 37 C, calibration data 0x5534ce69 > mx6q pll1: 792MHz > mx6q pll2: 528MHz > mx6q pll3: 480MHz > mx6q pll8: 50MHz > ipg clock : 66000000Hz > ipg per clock : 66000000Hz > uart clock : 80000000Hz > cspi clock : 60000000Hz > ahb clock : 132000000Hz > axi clock : 264000000Hz > emi_slow clock: 132000000Hz > ddr clock : 528000000Hz > usdhc1 clock : 198000000Hz > usdhc2 clock : 198000000Hz > usdhc3 clock : 198000000Hz > usdhc4 clock : 198000000Hz > nfc clock : 24000000Hz > Board: i.MX6Q-SABRESD: unknown-board Board: 0x63015 [POR ] > Boot Device: MMC > > HAB Configuration: 0xf0, HAB State: 0x66 > > --------- HAB Event 1 ----------------- > event data: > 0xdb 0x00 0x1c 0x41 0x33 0x18 0xc0 0x00 > 0xca 0x00 0x14 0x00 0x02 0xc5 0x00 0x00 > 0x00 0x00 0x0d 0x34 0x27 0x80 0x04 0x00 > 0x00 0x13 0xec 0x00 > > --------- HAB Event 2 ----------------- > event data: > 0xdb 0x00 0x14 0x41 0x33 0x0c 0xa0 0x00 > 0x00 0x00 0x00 0x00 0x27 0x80 0x04 0x00 > 0x00 0x00 0x00 0x20 > > --------- HAB Event 3 ----------------- > event data: > 0xdb 0x00 0x14 0x41 0x33 0x0c 0xa0 0x00 > 0x00 0x00 0x00 0x00 0x27 0x80 0x04 0x2c > 0x00 0x00 0x02 0xa0 > > --------- HAB Event 4 ----------------- > event data: > 0xdb 0x00 0x14 0x41 0x33 0x0c 0xa0 0x00 > 0x00 0x00 0x00 0x00 0x27 0x80 0x04 0x20 > 0x00 0x00 0x00 0x01 > > --------- HAB Event 5 ----------------- > event data: > 0xdb 0x00 0x14 0x41 0x33 0x0c 0xa0 0x00 > 0x00 0x00 0x00 0x00 0x27 0x80 0x06 0xe0 > 0x00 0x00 0x00 0x04 > I2C: ready > DRAM: 1 GB > MMC: FSL_USDHC: 0,FSL_USDHC: 1,FSL_USDHC: 2,FSL_USDHC: 3 > *** Warning - bad CRC or MMC, using default environment > > In: serial > Out: serial > Err: serial > Found PFUZE100! deviceid=10,revid=11 > Net: got MAC address from IIM: 00:00:00:00:00:00 > FEC0 [PRIME] > Hit any key to stop autoboot: 0 > booti: bad boot image magic > fastboot is in init......flash target is MMC:3 > wait usb cable into the connector! > > So, I've tried to write the image at an address and have loaded it from > there. I've did the following in the uboot prompt: > > MX6Q SABRESD U-Boot > ext2load mmc 3:1 0x30000000 uImage > Loading file "uImage" from mmc device 3:1 (xxd1) > 594591 bytes read > > MX6Q SABRESD U-Boot > bootm 0x30000000 > ## Booting kernel from Legacy Image at 30000000 ... > Image Name: > Image Type: ARM Linux Kernel Image (gzip compressed) > Data Size: 594527 Bytes = 580.6 kB > Load Address: 10001000 > Entry Point: 10001000 > Verifying Checksum ... OK > Uncompressing Kernel Image ... OK > > Starting kernel ... > > It stops here (even after adjusting the UART settings before building the > image). I'm unable to find the source of the problem. Can you give me any > leads on the possible problems? > > Thanks, > Kranthi > > On Wed, Mar 29, 2017 at 6:18 PM, Kranthi Tej <ee13b037@...484...> > wrote: > >> ---------- Forwarded message ---------- >> From: "Stefan Kalkowski" <stefan.kalkowski@...1...> >> Date: Mar 29, 2017 6:03 PM >> Subject: Re: Genode on i.MX6 (eMMC Flash) >> To: "Genode OS Framework Mailing List" <genode-main(a)lists.sourceforge.net >> > >> Cc: >> >> Hi Kranthi Tej, >> >> On 03/28/2017 12:30 PM, Kranthi Tej wrote: >> > Hi Stefan, >> > >> > I've tried using the uboot plugin (RUN_OPT += --include image/uboot). >> > I've been able to generate a uImage successfully. When I tried to flash >> > it on to the board, it stops with following log (was observed in >> > TeraTerm while using the MfgTool): >> > >> > U-Boot 2009.08 (Aug 16 2013 - 14:38:59) >> > >> > CPU: Freescale i.MX6 family TO1.5 at 792 MHz >> > Thermal sensor with ratio = 175 >> > Temperature: 42 C, calibration data 0x5524cd69 >> > mx6q pll1: 792MHz >> > mx6q pll2: 528MHz >> > mx6q pll3: 480MHz >> > mx6q pll8: 50MHz >> > ipg clock : 66000000Hz >> > ipg per clock : 66000000Hz >> > uart clock : 80000000Hz >> > cspi clock : 60000000Hz >> > ahb clock : 132000000Hz >> > axi clock : 264000000Hz >> > emi_slow clock: 132000000Hz >> > ddr clock : 528000000Hz >> > usdhc1 clock : 198000000Hz >> > usdhc2 clock : 198000000Hz >> > usdhc3 clock : 198000000Hz >> > usdhc4 clock : 198000000Hz >> > nfc clock : 24000000Hz >> > Board: i.MX6Q-SABRESD: unknown-board Board: 0x63015 [POR ] >> >> As I can see you are using another board with less memory than the >> Wandboard. Did you adapted the memory settings before building the >> Genode image for that board? >> Like it was discussed in this parallel mail thread: >> >> http://genode-main.narkive.com/nWs1hbc8/genode-on-i-mx6q-sabre-lite >> >> > Boot Device: MMC >> > I2C: ready >> > DRAM: 1 GB >> > MMC: FSL_USDHC: 0,FSL_USDHC: 1,FSL_USDHC: 2,FSL_USDHC: 3 >> > Using default environment >> > >> > In: serial >> > Out: serial >> > Err: serial >> > Net: got MAC address from IIM: 00:00:00:00:00:00 >> > FEC0 [PRIME] >> > Hit any key to stop autoboot: 0 >> > ## Booting kernel from Legacy Image at 10800000 ... >> > Image Name: >> > Image Type: ARM Linux Kernel Image (gzip compressed) >> > Data Size: 2075251 Bytes = 2 MB >> > Load Address: 10001000 >> > Entry Point: 10001000 >> > Verifying Checksum ... OK >> > ## Loading init Ramdisk from Legacy Image at 10c00000 ... >> > Image Name: uboot initramfs rootfs >> > Image Type: ARM Linux RAMDisk Image (gzip compressed) >> > Data Size: 4545326 Bytes = 4.3 MB >> > Load Address: 00000000 >> > Entry Point: 00000000 >> > Verifying Checksum ... OK >> > Uncompressing Kernel Image ... OK >> > >> > Starting kernel ... >> > >> > Also, I'm using the Android RAMDisk Image. Would that be a potential >> > cause for the problem? I've used the following XML script to flash the >> > image on to the board (UCL file for MfgTool): >> >> If you think the Android RAM disk might interfer with your Genode image, >> being in your position I would not load it in the first place. >> >> > >> > <UCL> >> > <CFG> >> > <STATE name="BootStrap" dev="MX6Q" vid="15A2" pid="0054"/> >> > <STATE name="Updater" dev="MSC" vid="066F" pid="37FF"/> >> > </CFG> >> > >> > <LIST name="SabreSD-eMMC" desc="Choose eMMC as media"> >> > <CMD state="BootStrap" type="boot" body="BootStrap" file >> > ="u-boot-mx6q-sabresd.bin" >Loading U-boot</CMD> >> > <CMD state="BootStrap" type="load" file="files/demo/uimage" >> > address="0x10800000" >> > loadSection="OTH" setSection="OTH" HasFlashHeader="FALSE" >> >>Loading Kernel.</CMD> >> > <CMD state="BootStrap" type="load" file="initramfs.cpio.gz.uboot" >> > address="0x10C00000" >> > loadSection="OTH" setSection="OTH" HasFlashHeader="FALSE" >> >>Loading Initramfs.</CMD> >> > <CMD state="BootStrap" type="jump" > Jumping to OS image. </CMD> >> > <CMD state="Updater" type="push" body="$ dd if=/dev/zero of=/dev/mmcblk0 >> > bs=512 seek=1536 count=16">clean up u-boot parameter</CMD> >> >  >> > <CMD state="Updater" type="push" body="$ echo 0 > >> > /sys/block/mmcblk0boot0/force_ro">access boot partition 1</CMD> >> > <CMD state="Updater" type="push" body="send" >> > file="files/demo/mmc_img">Sending U-Boot</CMD> >> > <CMD state="Updater" type="push" body="$ dd if=$FILE of=/dev/mmcblk0 >> > bs=512 seek=2 skip=2">write U-Boot to sd card</CMD> >> >  >> > <CMD state="Updater" type="push" body="$ echo 8 > >> > /sys/devices/platform/sdhci-esdhc-imx.3/mmc_host/mmc0/mmc0:0 >> 001/boot_config">access >> > user partition and enable boot partion 1 to boot</CMD> >> > <CMD state="Updater" type="push" body="send" >> > file="mksdcard-android.sh.tar">Sending partition shell</CMD> >> > <CMD state="Updater" type="push" body="$ tar xf $FILE "> >> > Partitioning...</CMD> >> > <CMD state="Updater" type="push" body="$ sh mksdcard-android.sh >> > /dev/mmcblk0"> Partitioning...</CMD> >> > <CMD state="Updater" type="push" body="$ ls -l /dev/mmc* ">Formatting sd >> > partition</CMD> >> > <CMD state="Updater" type="push" body="pipe dd of=/dev/mmcblk0p5 bs=512" >> > file="files/demo/demo.img">Sending and writting demo.img</CMD> >> > <CMD state="Updater" type="push" body="frf">Finishing rootfs write</CMD> >> > <CMD state="Updater" type="push" body="$ echo Update >> Complete!">Done</CMD> >> > </LIST> >> > </UCL> >> > >> > The script stops executing at "Jumping to OS image". Can you give me any >> > leads as to where I'm going wrong? >> > >> >> As I already told you, I do not have any experiences with that tool, but >> you probably encounter the same problems like when using the uImage above. >> >> > Note: I've generated the "mmc_img" file using the "create_uboot" tool >> > provided in the genode tools. >> >> I see. In contrast to the run-tool, which produces either a disk image >> or uImage, this utility creates a disk image with the u-boot binary >> only. I'm not sure whether you can use the same u-boot binary in between >> Wandboard and your board, probably not! >> >> We do not have a combination tool that combines u-boot and system image >> to provide one final disk image to you. >> >> Best regards >> Stefan >> >> -- >> Stefan Kalkowski >> Genode Labs >> >> https://github.com/skalk · http://genode.org/ >> >> ------------------------------------------------------------ >> ------------------ >> 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(a)lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/genode-main >> > >

3 18

VirtualBox subsystem on reconfigurable init
by Martijn Verschoor 28 Apr '17

28 Apr '17

Dear Genode community, I’m rewriting a scenario that uses a compound virtualbox subsystem that can be dynamically spawned and killed using the new ‘reconfigurable’ init for which we previously used the cli_monitor. The subsystem produces the expected log output for a few seconds, shows the “Press F12 to select boot device” virtualBox message, but ultimately hangs soon after a log message like: “fb resize : [0] 1920x1080 -> 720x400”. Also, the pointer no longer responds, and the intermediate init no longer generates reports. Other parts of the compound system remain functional. I can reproduce this behaviour on the recent vbox{4,5}_win{7,10}_{32,64} scenarios in ports/run at genode/master (f6386c6) with the patch below. I tried vbox4 / vbox5, Linux 32 bit guest, Windows 10 64 bit guest. Probably, I’m missing something trivial like a label prefix, but I fail to see what. Do you have any thoughts? PS: regarding the patch, please note 1) our test system uses partition 1 (not 4) and 2) I increased the readability of the run script by copy-pasting a part of the generated config back in the run script before I added the extra init component. Met vriendelijke groet / kind regards, Martijn Verschoor Cyber Security Labs B.V. | Gooimeer 6-31 | 1411 DD Naarden | The Netherlands +31 35 631 3253 (office) | +31 616 014 087 (mobile)

2 2

compiling genode with Virtual box tiny core Linux
by Janardhan 27 Apr '17

27 Apr '17

Hi, I am trying to compile genode with the support of virtual box and tiny core Linux .While compiling i am getting below error library dependencies... Library cxx Library alarm Library timed_semaphore Library config Library startup-nova Library base-nova-common Library base-nova Library ldso-startup Library ld-nova Program lib/ld/nova/ld-nova Program kernel/nova/hypervisor make[1]: Leaving directory `/home/janardhan/genode/build/nova_x86_64' genode build completed using 'ld-nova.lib.so' as 'ld.lib.so' using 'nova_timer_drv' as 'timer' cp: cannot stat ‘bin/virtualbox-nova’: No such file or directory while executing "exec cp bin/[kernel_specific_binary $binary] [run_dir]/genode/$binary" (procedure "copy_and_strip_genode_binaries_to_run_dir" line 4) invoked from within "copy_and_strip_genode_binaries_to_run_dir $modules" (procedure "build_core_image" line 8) invoked from within "build_core_image $binaries" (procedure "run_boot_dir" line 12) invoked from within "run_boot_dir $binaries" (procedure "build_boot_image" line 2) invoked from within "build_boot_image $boot_modules" (file "/home/janardhan/genode/repos/ports/run/virtualbox.run" line 181) invoked from within "source $include_name" ("foreach" body line 6) invoked from within "foreach include_name [get_cmd_arg --include ""] { # first check if the include name is absolute if {[string first "/" $include_name] == 0} { puts ..." (file "/home/janardhan/genode/tool/run/run" line 809) make: *** [run/virtualbox] Error 1 Can any one help?

6 19

base-hw Bootstrap implementation: 16.05 version vs. 17.02 version
by Vasan VS 22 Apr '17

22 Apr '17

Hi all, We are trying to build and run Genode on a custom board with iMX6 processor. As part of this process, we are trying to understand the implementation of base-hw in the 17.02 version release. In trying to understand the implementation of base-hw in the 16.05 implementation and in the current 17.02 version, we find that the bootstrap portion of the implementation is present in 17.02 source base @ base-hw/src/bootstrap which is NOT present in 16.05 code base. We had a look at the detailed release notes of all the intermediate releases between these two versions (16.05->16.08, 16.08->16.11, 16.11->17.02) but we could not find any documentation of the changes that has been done on this particular portion of base-hw between these two releases. If we use the 16.05 version on our board, we get the "Kernel initialized" message after init is started but on the 17.02 version, the board is hanging and refusing to boot up after "Starting kernel" message(from uboot). Can someone help us with the following: a) Provide the details of the changes that has been done between the two versions in the bootstrap portion b) Point us to any clues on why we are facing this hang problem after the log service is initialized and while enabling the MMU and caches. Thanks in advance, Vasan

2 2

Re: Ideas about interactive GUI
by Boris Mulder 21 Apr '17

21 Apr '17

Hi, Good to hear that you are also going to do this! For us, there is a clear need for a GUI system that is both dynamic and simple in use. > This is actually very similar to what the existing menu_view already > gives you. This configurablility would indeed be similar to menu_view. Another main difference is that it does not aim to replace menu_view, but is an overlapping component that could also handle input, and take actions, such as collapsing and expanding submenus. It could still use menu_view, fading_dialog and such parts. So instead it aims to replace the menu part of launcher, except that it is dynamic and generic. What we would like is such a menu component that could be used at many places; not only for a desktop environment, but also inside any application, or settings menu, or subsystem. It would be complete with elements such as buttons, submenus and dialogs, and the notion of clicking on these elements. These events could somehow be communicated to other elements such that the corresponding actions are taken. > I'd advise not to use the report/ROM interface to propagate events, but > only state. Even though one (myself included) is sometimes intuitively > tempted to mix up events and states, it calls for trouble. > [...] Makes sense, you are right. However, for clicking buttons in this context, it makes sense to communicate events instead of states. Perhaps using another way than reports could be useful here, such as some list of events like in Input, or a packet-stream like functionality. > This raises the question of where does the responsibility of the menu > end, and where do the responsibilities of the subsystem manager start? > If we need a subsystem manager anyway, couldn't it use the menu_view(s) > directly to implement menus? We would like to separate the menu with all its buttons from the subsystem state logic. Whenever we want an application that uses the GUI that does different things, we would have to import the menu management code into these applications. This could be done as a library with functions for creating buttons and menus, or as a separate component that can be configured and uses some IPC mechanism. In the latter case, more than one component can talk with the same menu, depending on the application programmer's needs. This can be made as complex or simple as is desirable. However now it is already quite complicated to create only a basic menu as all the features are very intertwined, which makes the code a bit hard to read and modify. > The answer may depend on the complexity of the subsystem manager, which > is obviously critical. Does the separation of the menu from the > subsystem manager contribute to significantly lower the TCB of the > subsystem manager? It does not necessarily change the TCB, but it is done for the sake of reusability and code readability/ease of programming. From that perspective we think it would be nice if these things were separated, and for instance the menu part could be used in another application as well. > This leaves the question about the input focus. When using the wm, the > focus is already defined by the window layouter via the 'focus' ROM. The > window layouter, in turn, already consumes a 'focus_request' ROM to > respond to externally triggered focus changes. This would be the right > hook for the menu / subsystem manager. I've been looking into this mechanism, but so far it's not entirely clear to me. Do you mean that the subsystem manager could write to this focus_request report and the layouter would for example show/hide the appropriate windows automatically? If so, what about the focus_requests that come from the window manager? In short: how would that work? > The state report generated by init already contains a 'state' attribute > for each child. Right now, the attribute is present only if the child is > "incomplete". We could add a value "exited" that would be presented as > soon as the child issued a 'Parent::exit' call. Also the exit code could > be added to the report, if needed. The subsystem manager could then > inspect the state reports for children with this attribute value and > remove them from the init config. This is exactly what I'm looking for in that case. Thanks, -- Met vriendelijke groet / kind regards, Boris Mulder Cyber Security Labs B.V. | Gooimeer 6-31 | 1411 DD Naarden | The Netherlands +31 35 631 3253 (office)

3 3

Genode compilation with virtual box and tiny core Linux
by janardhan 20 Apr '17

20 Apr '17

Hi, I am compiling Genode with Virtual box and tiny core Linux.Linux .While compiling i am getting below error's make[1]: Leaving directory `/home/janardhan/genode/build/nova_x86_64' genode build completed using 'ld-nova.lib.so' as 'ld.lib.so' using 'nova_timer_drv' as 'timer' cp: cannot stat ‘bin/virtualbox-nova’: No such file or directory while executing "exec cp bin/[kernel_specific_binary $binary] [run_dir]/genode/$binary" (procedure "copy_and_strip_genode_binaries_to_run_dir" line 4) invoked from within "copy_and_strip_genode_binaries_to_run_dir $modules" (procedure "build_core_image" line 8) invoked from within "build_core_image $binaries" (procedure "run_boot_dir" line 12) invoked from within "run_boot_dir $binaries" (procedure "build_boot_image" line 2) invoked from within "build_boot_image $boot_modules" (file "/home/janardhan/genode/repos/ports/run/virtualbox.run" line 181) invoked from within "source $include_name" ("foreach" body line 6) invoked from within "foreach include_name [get_cmd_arg --include ""] { # first check if the include name is absolute if {[string first "/" $include_name] == 0} { puts ..." (file "/home/janardhan/genode/tool/run/run" line 809) make: *** [run/virtualbox] Error 1 Can any one help?

1 0

Now: Nova not maintained [Earlier]: Understanding Muen [Earlier] Re: Problem with make run/demo ....
by Shahbaz khan 19 Apr '17

19 Apr '17

Hi Nobody, Please don't mind my changing the subject title. On Tue, Apr 18, 2017 at 11:44 PM, Nobody III <hungryninja101@...9...> wrote: > By the way, NOVA doesn't seem to be maintained anymore, except a bit by > Genode developers. Is this observation correct? > My observation is that most of the innovations were achieved by 2012 in microkernel research so stable work is what we see in Fiasco.oc and Nova. The only problem was that these OSes could not be formally verified. Muen answers the problem by hardcore simplicity, while I believe SEL4 has practicality issues. Formal verification is not interesting for developers so somehow funds went somewhere else. Just a thought. Rest is driver development which is not a research and showcase problem and handed by industry rather than universities, TUD Genode people are the pioneers and can answer better. Regards, Shahbaz

2 2

Re: Now: Understanding Muen and base_hw kernel from docs, [Earlier] Re: Problem with make run/demo ....
by Shahbaz khan 19 Apr '17

19 Apr '17

Dear Norman, On 17.04.2017 19:53, Shahbaz khan wrote: > > VirtualBox closely interacts with the virtualization hardware. On > Muen, > > this interaction naturally has to go through the Muen SK. By using > > Genode as runtime for VirtualBox, Muen is able to leverage Genode's > > existing solution of the interaction of VirtualBox with a > > microkernel-based virtualization mechanism. > > > > > > Similar to karma-vmm, fiasco.oc and l4linux. > > I don't see the connection. My email was not related to Fiasco.OC, > Karma, or L4Linux. > I think I got the problem. Muen subject is not a subject like that of an OS. > > > Conceptually, a Muen partition is a hardware platform, similar to a > > board. Like on any board, you can run software directly (in > supervisor > > mode). But for running a complex software stack, or more than one > > application, one has to use an operating system (OS). Genode/base-hw > > plays this role. > > > > > > Simply put a build time think. Base-hw kernel means muen sk for genode > > runtime. > > Muen can be used without base-hw. > Base-hw can be used without Muen. > Second problem in my mind would be imagining the spartan environment provided by Muen to be fulfilled with Genode runtime minus microkernel. This would be as follows. Base-HW is a microkernel as you mentioned earlier. Like a layman I ask the name of this microkernel. Is it Nova? Again to my preliminary question ... we run a micro-kernel on microkernel to run virtualbox rather than virtualbox on Muen SK. > > But when combined, Genode's version of VirtualBox can run on top of Muen. > Muen is a micro-hypervisor. What is the nature of inter-subject communication? Considering we don't like pure hypervisor approach. I liked Nova's architecture much more and I would opt for Nova if formal verification could be as simple for it as in Muen. And the luxury of C++ too. Regards, Shahbaz

3 2

Genode, seL4 and VirtualBox
by Chris Rothrock 18 Apr '17

18 Apr '17

I'm working with the team at Critical Technologies and I am trying to get this combination to work - Genode with seL4 microkernel and the VirtualBox module (using TinyCore Linux). Let me first start off with saying that Genode, Nova and VirtualBox works flawlessly - I can boot (an Intel-based machine) and go into either a command line or GUI environment. The problem is when I try using seL4. I can compile this without any errors. The ISO image is made perfectly, it boots to this image on the same hardware - but that's where it stops. One time only I was able to see the loading screen of TinyCore Linux within VirtualBox but the boot time for this took about 45 minutes and I was unable to reproduce this boot. I guess my first question is this - does seL4 have the necessary virtualization support for this module? If so, how can I make this work reliably? -- Thank You, Chris Rothrock Senior System Administrator (315) 308-1637

3 3

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

users