from:"Vincent Digital"

Re: Turmvilla scenario

2015-11-08 Thread Vincent Digital

Hi, everyone,

Thanks for sharing your experiences on Wi Fi driver and NIC driver with NIC
Bridge. With renewed confidence, I've persisted with a new GIT version of
Genode and now I am happy to share that I'm able to get NIC Bridge working
with Wi Fi driver as well for 2 x sessions of Virtualbox, one with an
Ubuntu Linux guest and the other with a Windows 7 guest. The funny thing is
that I used the same configuration file as previous so I am not sure why it
works now while previously it could not.

As I proceed to use Turmvilla as regular, I would like to share 2 issues
and see if there are any suggestions to improve.

a. Shutdown of VMM - Fixes #1687. I would attempt to shutdown my Windows or
Linux session and the VMM window would hang. I thought it was fixed by
Fixes #1687 but it seems the problem is still there. I have checked and
double-checked that Fixes #1687 is in. Any idea ? I've not manage to
capture the logs for this issue.

b. Memory leak or stability issue. I have encountered a couple of times
leaving the Turmvilla scenario with both sessions running (just web
browsers) for 1-2 hours. When I returned to the machine, the entire
computer hanged up. I could not even access CLI terminal to terminate
anything. As usual, besides the logs, any suggestions to troubleshoot the
issue.

Thanks.

On Fri, Nov 6, 2015 at 6:41 PM, Christian Helmuth <
christian.helm...@genode-labs.com> wrote:

> Hello Vincent,
>
> On Thu, Nov 05, 2015 at 06:18:36PM +0800, Vincent Digital wrote:
> > Can I clarify with you that the nic_bridge can both support Wifi_Driver
> as
> > well as the Nic_Driver. In my tests, I could only get the nic_bridge to
> > work with the Nic_Driver to support 2 clients (Windows + Drivers).
>
> We had a short offline discussion this morning and after that it's
> unclear if the ProxyARP approach could work with WiFi as it is
> currently used with the wifi_drv. So, if anybody on the list has some
> experience with bridging and Wifi, please speak up.
>
> Greets
> --
> Christian Helmuth
> Genode Labs
>
> http://www.genode-labs.com/ · http://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
>
>
> --
> ___
> genode-main mailing list
> genode-main@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/genode-main
>
--
Presto, an open source distributed SQL query engine for big data, initially
developed by Facebook, enables you to easily query your data on Hadoop in a 
more interactive manner. Teradata is also now providing full enterprise
support for Presto. Download a free open source copy now.
http://pubads.g.doubleclick.net/gampad/clk?id=250295911=/4140___
genode-main mailing list
genode-main@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/genode-main

Re: Turmvilla scenario

2015-11-05 Thread Vincent Digital

Hi, Alex,

Can I clarify with you that the nic_bridge can both support Wifi_Driver as
well as the Nic_Driver. In my tests, I could only get the nic_bridge to
work with the Nic_Driver to support 2 clients (Windows + Drivers).

Thanks.



On Fri, Oct 30, 2015 at 6:57 PM, Alexander Boettcher <
alexander.boettc...@genode-labs.com> wrote:

> On 30.10.2015 11:49, Christian Helmuth wrote:
> > What puzzles me in your log is the following
> >
> > 342: [cli_monitor -> linux -> vbox] EMT-0PDMR3ThreadSuspend ->
> rc=VERR_TIMEOUT enmState=2 suspending 'nic_thread'
> > 343: [cli_monitor -> linux -> vbox] PDMR3ThreadSuspend ->
> rc=VERR_TIMEOUT enmState=2 suspending 'nic_thread'
> >
> > Could you please disable networking like follows in both vbox
> > configurations and retry?
> >
> > -  cable="true" speed="0" type="82540EM">
> > +  cable="true" speed="0" type="82540EM">
> >
>
> I suspect you will have to add a nic session multiplexer (nic_bridge),
> since you are now trying to start two nic clients (linux + windows) and
> the wifi driver can serve only one client.
>
> Cheers,
>
> Alex.
>
>
> --
> ___
> 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: Turmvilla scenario

2015-11-02 Thread Vincent Digital

Hi, Christian,

Yes, thanks. I have resolved the mouse pointer issue after installation the
guest additions.

Regards.

On Fri, Oct 30, 2015 at 6:49 PM, Christian Helmuth <
christian.helm...@genode-labs.com> wrote:

> Hi Vincent,
>
> On Fri, Oct 30, 2015 at 04:50:32PM +0800, Vincent Digital wrote:
> > Hi,
> >
> > With the previous Turmvilla scenario, I wish to setup two virtualbox
> > sessions, one running LInux process and the other running Windows,
> > concurrently. I created a new Win7 subsystem, emulating the LInux
> > subsystem, with new vm_win7.vdi.
> >
> > However, I could startup only one of each sessions from NOUX, either
> > Windows or Linux, but not both sessions at the same time. From CLI
> monitor,
> > I could see that RAM is allocated separately for both sessions. I suspect
> > some concurrency issue but could not find the issue.
> >
> > I've attached the log from captured from NOUX.
>
> What puzzles me in your log is the following
>
> 342: [cli_monitor -> linux -> vbox] EMT-0PDMR3ThreadSuspend ->
> rc=VERR_TIMEOUT enmState=2 suspending 'nic_thread'
> 343: [cli_monitor -> linux -> vbox] PDMR3ThreadSuspend -> rc=VERR_TIMEOUT
> enmState=2 suspending 'nic_thread'
>
> Could you please disable networking like follows in both vbox
> configurations and retry?
>
> -  speed="0" type="82540EM">
> +  speed="0" type="82540EM">
>
> In the log, win7 vbox appears only after the assertion in linux vbox.
> Currently, I've no idea why win7 gets stuck in the middle of
> initialization. Later in the log, there's another try to start linux
> vbox if I'm not mistaken, which also did not succeed.
>
> It may also matter if the base services incl. core and NOVA log some
> diagnostics in the time span of the multiple vbox startup. Could you
> please check the serial log for suspicious messages?
>
> > Another issue I encountered is that the virtual box mouse pointer in the
> > WIndows session and the Nitpicker mouse pointer can't seem to merge
> > together unlike the Linux session where both pointers are merged.
>
> I suspect your Windows installation is missing the VirtualBox guest
> tools. In this case, the guest draws a software mouse pointer into the
> framebuffer which often appears not in sync with the Nitpicker
> pointer. So, after the guest tools are installed the Windows pointer
> will disappear. Looking at
>
>
> https://github.com/nfeske/genode/blob/turmvilla/repos/gems/run/turmvilla.run
>
> I also expect the mouse-pointer integration for win7 will work out of
> the box and the shape will be reported from the Windows guest to
> vbox_pointer.
>
> Regards
> --
> Christian Helmuth
> Genode Labs
>
> http://www.genode-labs.com/ · http://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
>
>
> --
> ___
> 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: Turmvilla scenario

2015-11-02 Thread Vincent Digital

Hi, Alex/Christian,

Okay (partially), by adding the "nic_bridge" with the "turmvilla.run" file,
I could start both the Windows and Linux subsystems at the same time. For
configuration of "nic_bridge", I followed the examples in the
repos/libports/run - test-nicbridge-static.run, network-test.run, etc.

However, after adding in the "nic_bridge", I could not access the network
(Internet) from either the Windows or Linux subsystem. I suspect
configuration issues of the "nic_bridge". The MAC address in the log file
does not change to my assigned MAC address "02:00:00:00:00:00" but my own
NIC card. It seems that if I used auto assignment of VMs' IP addresses via
DHCP, I would just need to configure the turmvilla.run file.  Is there any
other file(s) that I should change as well ?

Any suggestions ? Thanks in advance.

I've attached part of turmvilla.run file and the AMT log file.

server/nic_bridge
209,227d207
< 
< 
< 
<  

< 
<
< 
< 
< 
< 
< 
< 
< 
< 
< 
< 
<
<
<
627,631d606
< 
< 
< 

map multi-boot module: physical 0x7bbd3000+0x000e73d8 - core
map multi-boot module: physical 0x7bcbb000+0x4ac9 - config
map multi-boot module: physical 0x7bcc+0x0005ecd0 - init
map multi-boot module: physical 0x7bd1f000+0x0005ad38 - timer
map multi-boot module: physical 0x7bd7a000+0x0005ab80 - part_blk
map multi-boot module: physical 0x7bdd5000+0x00071ca8 - ahci_drv
map multi-boot module: physical 0x7be47000+0x0009b908 - ld.lib.so
map multi-boot module: physical 0x7bee3000+0x00108810 - libc.lib.so
map multi-boot module: physical 0x7bfec000+0x000285f0 - libm.lib.so
map multi-boot module: physical 0x7c015000+0x9a10 - pthread.lib.so
map multi-boot module: physical 0x7c01f000+0x5db8 - libc_lock_pipe.lib.so
map multi-boot module: physical 0x7c025000+0x00013238 - libc_terminal.lib.so
map multi-boot module: physical 0x7c039000+0x000e71e8 - libiconv.lib.so
map multi-boot module: physical 0x7c121000+0x000deaf0 - stdcxx.lib.so
map multi-boot module: physical 0x7c20+0x001cdd70 - rump.lib.so
map multi-boot module: physical 0x7c3ce000+0x0012bd78 - rump_fs.lib.so
map multi-boot module: physical 0x7c4fa000+0x000265a8 - rump_fs
map multi-boot module: physical 0x7c521000+0x0080a310 - virtualbox
map multi-boot module: physical 0x7cd2c000+0x0005d160 - ps2_drv
map multi-boot module: physical 0x7cd8a000+0x001110b8 - usb_drv
map multi-boot module: physical 0x7ce9c000+0x0004e5e0 - acpi_drv
map multi-boot module: physical 0x7ceeb000+0x00070b40 - platform_drv
map multi-boot module: physical 0x7cf5c000+0x00087de0 - fb_drv
map multi-boot module: physical 0x7cfe4000+0x00051ab0 - device_pd
map multi-boot module: physical 0x7d036000+0x0005def8 - rtc_drv
map multi-boot module: physical 0x7d094000+0x0005b728 - input_merger
map multi-boot module: physical 0x7d0f+0x0007d9f8 - nic_drv
map multi-boot module: physical 0x7d16e000+0x00071190 - nic_bridge
map multi-boot module: physical 0x7d1e+0x0007e400 - nitpicker
map multi-boot module: physical 0x7d25f000+0x00056358 - vbox_pointer
map multi-boot module: physical 0x7d2b6000+0x00062838 - nit_fb
map multi-boot module: physical 0x7d319000+0x00061148 - report_rom
map multi-boot module: physical 0x7d37b000+0x00069d60 - wm
map multi-boot module: physical 0x7d3e5000+0x00064f58 - decorator
map multi-boot module: physical 0x7d44a000+0x000541f8 - floating_window_layouter
map multi-boot module: physical 0x7d49f000+0x000671b0 - noux
map multi-boot module: physical 0x7d507000+0x00070ff8 - terminal
map multi-boot module: physical 0x7d579000+0x0005fa40 - ram_fs
map multi-boot module: physical 0x7d5d9000+0x000184e0 - libc_noux.lib.so
map multi-boot module: physical 0x7d5f2000+0x00052d10 - ncurses.lib.so
map multi-boot module: physical 0x7d645000+0x0037 - bash.tar
map multi-boot module: physical 0x7d9b6000+0x008cf000 - coreutils.tar
map multi-boot module: physical 0x7e286000+0x01315000 - vim.tar
map multi-boot module: physical 0x7f59c000+0x00058550 - cli_monitor
map multi-boot module: physical 0x7f5f5000+0x000500b0 - pointer
map multi-boot module: physical 0x7f646000+0x00010a60 - file_terminal
map multi-boot module: physical 0x7f657000+0x000532b0 - terminal_log
map multi-boot module: physical 0x7f6ab000+0x00014e58 - wifi_drv
map multi-boot module: physical 0x7f6c+0x00056e88 - fs_rom
map multi-boot module: physical 0x7f717000+0x83e8 - vfs_jitterentropy.lib.so
map multi-boot module: physical 0x7f72+0x001dde90 - libcrypto.lib.so
map multi-boot module: physical 0x7f8fe000+0x0006e7c0 - libssl.lib.so
map multi-boot module: physical 0x7f96d000+0x000324d0 - 
wpa_driver_nl80211.lib.so
map multi-boot module: physical 0x7f9a+0x000703a0 - wpa_supplicant.lib.so
map multi-boot module: physical

Turmvilla scenario

2015-10-30 Thread Vincent Digital

Hi,

With the previous Turmvilla scenario, I wish to setup two virtualbox
sessions, one running LInux process and the other running Windows,
concurrently. I created a new Win7 subsystem, emulating the LInux
subsystem, with new vm_win7.vdi.

However, I could startup only one of each sessions from NOUX, either
Windows or Linux, but not both sessions at the same time. From CLI monitor,
I could see that RAM is allocated separately for both sessions. I suspect
some concurrency issue but could not find the issue.

I've attached the log from captured from NOUX.

Another issue I encountered is that the virtual box mouse pointer in the
WIndows session and the Nitpicker mouse pointer can't seem to merge
together unlike the Linux session where both pointers are merged.

Any advise.

Thanks in advance.


log-30Oct15
Description: Binary data
--
___
genode-main mailing list
genode-main@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/genode-main

Re: Turmvilla scenario

2015-10-21 Thread Vincent Digital

Hi, Alex,

Thanks. I've updated the Turmvilla - Nova as 64bit and now I could start
the Noux subsystem.
i'm still facing hang issue in starting up the Linux subsystem.
This time I could capture the Logs from the /shared/log file.
A few questions :

1. For the wifi configuration, I've tried to configure it from within Noux
under the /config/wlan_configuration.
But it seems to points to WPA_SUPPLICANT file. i have configured both but
not sure if it is correct as I checked the /reports for wireless state and
it seems to be not working.
How can I made the configuration permanent as the files seem to be
overwritten everytime NOUX startup.
Is there a manual on how to configure NOUX ?


2 . For the Linux subsystem, from the /shared/log file, it seems to
indicate some issues with the virtualbox configuration. Writing to
non-existent port. Any advise on how to move on.

Regards.

Part of the /shared/log file.

[wifi_drv] wlan0: CTRL-EVENT-SCAN-STARTED
[wifi_drv] wlan0: CTRL-EVENT-SCAN-STARTED
[wifi_drv] wlan0: CTRL-EVENT-SCAN-STARTED
[wifi_drv] wlan0: CTRL-EVENT-SCAN-STARTED
[cli_monitor -> linux -> nit_fb] [32musing xywh=(0,0,1024,768)[0m
[rump_fs] [32mupgrading quota donation for Env::RM (8192 bytes)[0m
[cli_monitor -> linux -> vbox] void init_libc_lock_pipe():
[33minit_libc_lock_pipe()
[0m[cli_monitor -> linux -> vbox] using the pipe libc plugin
[cli_monitor -> linux -> vbox] [34mgetenv called for non-existent variable
"XML_MEM_BREAKPOINT"[0m
[cli_monitor -> linux -> vbox] [34mgetenv called for non-existent variable
"XML_MEM_TRACE"[0m
[cli_monitor -> linux -> vbox] [34mgetenv called for non-existent variable
"LC_ALL"[0m
[cli_monitor -> linux -> vbox] [34mgetenv called for non-existent variable
"LC_CTYPE"[0m
[cli_monitor -> linux -> vbox] [34mgetenv called for non-existent variable
"LANG"[0m
[cli_monitor -> linux -> vbox] [34mgetenv called for non-existent variable
"PATH_LOCALE"[0m
[cli_monitor -> linux -> vbox] [34mgetenv called for non-existent variable
"VBOX_DISABLE_HOST_DISK_CACHE"[0m
[cli_monitor -> linux -> vbox] [34mgetenv called for non-existent variable
"CHARSETALIASDIR"[0m
[cli_monitor -> linux -> vbox] [34mgetenv called for non-existent variable
"TZ"[0m
[cli_monitor -> linux -> vbox] int access(const char*, int): [33maccess
not implemented[0m
[cli_monitor -> linux -> vbox] [34mgetenv called for non-existent variable
"TZ"[0m
[cli_monitor -> linux -> vbox] [31mfcntl(): command 2 not supported[0m
[cli_monitor -> linux -> vbox] Log created: 2015-10-21T10:33:00.99800Z
[cli_monitor -> linux -> vbox] main Executable: /virtualbox
[cli_monitor -> linux -> vbox] [31mSystemProperties : Cannot determine
default Guest Additions ISO location. Most likely they are not available[0m
[cli_monitor -> linux -> vbox] [34mgetenv called for non-existent variable
"VBOX_USER_VMLOGDIR"[0m
[cli_monitor -> linux -> vbox] [34mrequested stack for thread 'EMT-0' of
1048576 Bytes is too large, limit to 1036288 Bytes[0m
[cli_monitor -> linux -> vbox] [34mrequested stack for thread 'EMT-1' of
1048576 Bytes is too large, limit to 1036288 Bytes[0m
[cli_monitor -> linux -> vbox] [34mrequested stack for thread 'EMT-2' of
1048576 Bytes is too large, limit to 1036288 Bytes[0m
[cli_monitor -> linux -> vbox] [32mupgrading quota donation for Env::CPU
(8192 bytes)[0m
[cli_monitor -> linux -> vbox] [32mupgrading quota donation for Env::RM
(8192 bytes)[0m
[cli_monitor -> linux -> vbox] [32mupgrading quota donation for Env::RM
(8192 bytes)[0m
[cli_monitor -> linux -> vbox] [34mrequested stack for thread 'EMT-3' of
1048576 Bytes is too large, limit to 1036288 Bytes[0m
[cli_monitor -> linux -> vbox] [32mupgrading quota donation for Env::RM
(8192 bytes)[0m
[cli_monitor -> linux -> vbox] [32mupgrading quota donation for Env::RM
(8192 bytes)[0m
[cli_monitor -> linux -> vbox] [31mshared library 'VBoxSharedClipboard'
not supported[0m
[wifi_drv] wlan0: CTRL-EVENT-SCAN-STARTED
[wifi_drv] wlan0: CTRL-EVENT-SCAN-STARTED
[wifi_drv] wlan0: CTRL-EVENT-SCAN-STARTED
[cli_monitor -> linux -> nit_fb] [32musing xywh=(0,0,1024,768)[0m
[cli_monitor -> linux -> vbox] void init_libc_lock_pipe():
[33minit_libc_lock_pipe()
[0m[cli_monitor -> linux -> vbox] using the pipe libc plugin
[cli_monitor -> linux -> vbox] [34mgetenv called for non-existent variable
"XML_MEM_BREAKPOINT"[0m
[cli_monitor -> linux -> vbox] [34mgetenv called for non-existent variable
"XML_MEM_TRACE"[0m
[cli_monitor -> linux -> vbox] [34mgetenv called for non-existent variable
"LC_ALL"[0m
[cli_monitor -> linux -> vbox] [34mgetenv called for non-existent variable
"LC_CTYPE"[0m
[cli_monitor -> linux -> vbox] [34mgetenv called for non-existent variable
"LANG"[0m
[cli_monitor -> linux -> vbox] [34mgetenv called for non-existent variable
"PATH_LOCALE"[0m
[cli_monitor -> linux -> vbox] [34mgetenv called for non-existent variable
"VBOX_DISABLE_HOST_DISK_CACHE"[0m
[cli_monitor -> linux -> vbox] [34mgetenv called for non-existent

Re: Turmvilla scenario

2015-10-20 Thread Vincent Digital

Hi, Alex,

Okay, I tried to activate the Noux subsystem as advised by you after
activiting the Linux subsystem.
I encountered a total hang situation. In fact, anytime I activated the Noux
subsystem, it always hanged. Nothing can move on the screen.
As for the previous Linux subsystem which I thought was "hanged", actually
after waiting for about 30 minutes, the Linux subsystem shows a "kernel
panic".

Any idea what I can do to troubleshoot further.
I have attached the log after the Noux subsystem hang.
Are those quota overflow messages really a problem ?


NOVA Microhypervisor v7-a4a926a (x86_32): Oct 10 2015 18:00:57 [gcc 4.9.2]

[ 0] CORE:0:0:0 6:25:5:4 [2] Intel(R) Core(TM) i5 CPU   M 580  @ 2.67GHz
[ 1] CORE:0:0:1 6:25:5:4 [2] Intel(R) Core(TM) i5 CPU   M 580  @ 2.67GHz
[ 3] CORE:0:2:1 6:25:5:4 [2] Intel(R) Core(TM) i5 CPU   M 580  @ 2.67GHz
[ 2] CORE:0:2:0 6:25:5:4 [2] Intel(R) Core(TM) i5 CPU   M 580  @ 2.67GHz
[ 0] DMAR:0xc23c5060 FRR:0 FR:0x5 BDF:0:2:0 FI:0x77fb7f000
Hypervisor features VMX
Hypervisor reports 4x1 CPUs - boot CPU is 0
Hypervisor info page contains 99 memory descriptors:
detected physical memory: 0x - size: 0x9e800
use  physical memory: 0x - size: 0x9e000
detected physical memory: 0x0010 - size: 0xbb17c000
use  physical memory: 0x0010 - size: 0xbb17c000
detected physical memory: 0xbb282000 - size: 0xdd000
use  physical memory: 0xbb282000 - size: 0xdd000
detected physical memory: 0xbb40f000 - size: 0x6
use  physical memory: 0xbb40f000 - size: 0x6
detected physical memory: 0xbb70f000 - size: 0x8000
use  physical memory: 0xbb70f000 - size: 0x8000
detected physical memory: 0xbb71f000 - size: 0x4c000
use  physical memory: 0xbb71f000 - size: 0x4c000
detected physical memory: 0xbb7ff000 - size: 0x1000
use  physical memory: 0xbb7ff000 - size: 0x1000
detected physical memory: 0x0001 - size: 0xfc00
detected physical memory: 0x0002 - size: 0x3c00
map multi-boot module: physical 0x7bd3a000 -> [0x001d-0x002a02b0) - core
map multi-boot module: physical 0x7be0b000 -> [0x2000-0x6031) -
config
map multi-boot module: physical 0x7be1 -> [0xa000-0x0006c2d8) - init
map multi-boot module: physical 0x7be73000 -> [0x0007-0x000cec2c) -
timer
map multi-boot module: physical 0x7bed2000 -> [0xb000-0xb005f0f8) -
part_blk
map multi-boot module: physical 0x7bf32000 -> [0x002a4000-0x0031bd84) -
ahci_drv
map multi-boot module: physical 0x7bfaa000 -> [0xb0061000-0xb00f6000) -
ld.lib.so
map multi-boot module: physical 0x7c04 -> [0xb00f6000-0xb01f0950) -
libc.lib.so
map multi-boot module: physical 0x7c13b000 -> [0xb01f2000-0xb02188f4) -
libm.lib.so
map multi-boot module: physical 0x7c162000 -> [0x000dd000-0x000e53d0) -
pthread.lib.so
map multi-boot module: physical 0x7c16b000 -> [0x000e9000-0x000ed9d4) -
libc_lock_pipe.lib.so
map multi-boot module: physical 0x7c17 -> [0xb021a000-0xb022c9d0) -
libc_terminal.lib.so
map multi-boot module: physical 0x7c183000 -> [0xb022e000-0xb0312a70) -
libiconv.lib.so
map multi-boot module: physical 0x7c268000 -> [0xb0314000-0xb03e9e74) -
stdcxx.lib.so
map multi-boot module: physical 0x7c33e000 -> [0xb03eb000-0xb0520a9c) -
rump.lib.so
map multi-boot module: physical 0x7c474000 -> [0xb0522000-0xb0673c24) -
rump_fs.lib.so
map multi-boot module: physical 0x7c5c6000 -> [0xb0675000-0xb069b234) -
rump_fs
map multi-boot module: physical 0x7c5ed000 -> [0xb069d000-0xb0f8b1bc) -
virtualbox
map multi-boot module: physical 0x7cedc000 -> [0xb0f8d000-0xb0fee5d4) -
ps2_drv
map multi-boot module: physical 0x7cf3e000 -> [0xb0ff1000-0xb1116c74) -
usb_drv
map multi-boot module: physical 0x7d064000 -> [0xb111a000-0xb116ae30) -
acpi_drv
map multi-boot module: physical 0x7d0b5000 -> [0xb116e000-0xb11dfe24) -
platform_drv
map multi-boot module: physical 0x7d127000 -> [0xb11e3000-0xb1271c84) -
fb_drv
map multi-boot module: physical 0x7d1b6000 -> [0xb1275000-0xb12c8fdc) -
device_pd
map multi-boot module: physical 0x7d20a000 -> [0xb12cc000-0xb132ce98) -
rtc_drv
map multi-boot module: physical 0x7d26b000 -> [0xb133-0xb138fbb0) -
input_merger
map multi-boot module: physical 0x7d2cb000 -> [0xb1393000-0xb141470c) -
nic_drv
map multi-boot module: physical 0x7d34d000 -> [0xb1418000-0xb14983e4) -
nitpicker
map multi-boot module: physical 0x7d3ce000 -> [0xb149c000-0xb14f5a74) -
vbox_pointer
map multi-boot module: physical 0x7d428000 -> [0xb14f9000-0xb155ed40) -
nit_fb
map multi-boot module: physical 0x7d48e000 -> [0xb1562000-0xb15c61ac) -
report_rom
map multi-boot module: physical 0x7d4f3000 -> [0xb15cb000-0xb1634aa4) - wm
map multi-boot module: physical 0x7d55d000 -> [0xb1638000-0xb1698ca8) -
decorator
map multi-boot module: physical 0x7d5be000 -> [0xb169c000-0xb16f2504) -
floating_window_layouter
map multi-boot module: physical 0x7d615000 ->

Turmvilla scenario

2015-10-19 Thread Vincent Digital

Hi,

Can anyone help. Thanks in advance.

I've set up the Turmvilla scenario on a Lenovo X201 as much as I can based
on the documentation stated by everyone else that contributed. On boot-up I
could get the CLI_Monitor and upon entering "start linux" subsystem, I've a
pop-up window that just hang. I could not kill it too from the CLI_Monitor.

Attached are the log messages captured via AME :

Bender: Hello World.
 Need 043fb000 bytes to relocate modules.
 Relocating to 7bc05000:
 Copying 679780 bytes...
 Copying 679436 bytes...
 Copying 677296 bytes...
 Copying 454608 bytes...
 Copying 362676 bytes...
 Copying 402116 bytes...
 Copying 4604 bytes...
 Copying 87208 bytes...
 Copying 1470576 bytes...
 Copying 475500 bytes...
 Copying 224656 bytes...
 Copying 438044 bytes...
 Copying 1893512 bytes...
 Copying 28508 bytes...
 Copying 370384 bytes...
 Copying 87208 bytes...
 Copying 354672 bytes...
 Copying 61056 bytes...
 Copying 342200 bytes...
 Copying 350488 bytes...
 Copying 19947520 bytes...
 Copying 9277440 bytes...
 Copying 3553280 bytes...
 Copying 293864 bytes...
 Copying 89428 bytes...
 Copying 409848 bytes...
 Copying 481064 bytes...
 Copying 401276 bytes...
 Copying 353540 bytes...
 Copying 396456 bytes...
 Copying 432804 bytes...
 Copying 410028 bytes...
 Copying 417088 bytes...
 Copying 367220 bytes...
 Copying 525284 bytes...
 Copying 530188 bytes...
 Copying 392112 bytes...
 Copying 396952 bytes...
 Copying 344028 bytes...
 Copying 584836 bytes...
 Copying 466468 bytes...
 Copying 331312 bytes...
 Copying 1203316 bytes...
 Copying 398804 bytes...
 Copying 9363900 bytes...
 Copying 156212 bytes...
 Copying 1383460 bytes...
 Copying 1268380 bytes...
 Copying 876148 bytes...
 Copying 936560 bytes...
 Copying 76240 bytes...
 Copying 18900 bytes...
 Copying 33744 bytes...
 Copying 157940 bytes...
 Copying 1026384 bytes...
 Copying 610304 bytes...
 Copying 490884 bytes...
 Copying 389368 bytes...
 Copying 388140 bytes...
 Copying 402136 bytes...
 Copying 16433 bytes...
 Copying 852656 bytes...
 Copying 1264272 bytes...

  NOVA Microhypervisor v7-a4a926a (x86_32): Oct 10 2015 18:00:57 [gcc
4.9.2]

[ 0] CORE:0:0:0 6:25:5:4 [2] Intel(R) Core(TM) i5 CPU   M 580  @
2.67GHz
[ 1] CORE:0:0:1 6:25:5:4 [2] Intel(R) Core(TM) i5 CPU   M 580  @
2.67GHz
[ 3] CORE:0:2:1 6:25:5:4 [2] Intel(R) Core(TM) i5 CPU   M 580  @
2.67GHz
[ 2] CORE:0:2:0 6:25:5:4 [2] Intel(R) Core(TM) i5 CPU   M 580  @
2.67GHz
[ 0] DMAR:0xc23c5060 FRR:0 FR:0x5 BDF:0:2:0 FI:0xb56b4000
Hypervisor features VMX
Hypervisor reports 4x1 CPUs - boot CPU is 0
Hypervisor info page contains 99 memory descriptors:
detected physical memory: 0x - size: 0x9e800
use  physical memory: 0x - size: 0x9e000
detected physical memory: 0x0010 - size: 0xbb17c000
use  physical memory: 0x0010 - size: 0xbb17c000
detected physical memory: 0xbb282000 - size: 0xdd000
use  physical memory: 0xbb282000 - size: 0xdd000
detected physical memory: 0xbb40f000 - size: 0x6
use  physical memory: 0xbb40f000 - size: 0x6
detected physical memory: 0xbb70f000 - size: 0x8000
use  physical memory: 0xbb70f000 - size: 0x8000
detected physical memory: 0xbb71f000 - size: 0x4c000
use  physical memory: 0xbb71f000 - size: 0x4c000
detected physical memory: 0xbb7ff000 - size: 0x1000
use  physical memory: 0xbb7ff000 - size: 0x1000
detected physical memory: 0x0001 - size: 0xfc00
detected physical memory: 0x0002 - size: 0x3c00
map multi-boot module: physical 0x7bd3a000 -> [0x001d-0x002a02b0) -
core
map multi-boot module: physical 0x7be0b000 -> [0x2000-0x6031) -
config
map multi-boot module: physical 0x7be1 -> [0xa000-0x0006c2d8) -
init
map multi-boot module: physical 0x7be73000 -> [0x0007-0x000cec2c) -
timer
map multi-boot module: physical 0x7bed2000 -> [0xb000-0xb005f0f8) -
part_blk
map multi-boot module: physical 0x7bf32000 -> [0x002a4000-0x0031bd84) -
ahci_drv
map multi-boot module: physical 0x7bfaa000 -> [0xb0061000-0xb00f6000) -
ld.lib.so
map multi-boot module: physical 0x7c04 -> [0xb00f6000-0xb01f0950) -
libc.lib.so
map multi-boot module: physical 0x7c13b000 -> [0xb01f2000-0xb02188f4) -
libm.lib.so
map multi-boot module: physical 0x7c162000 -> [0x000dd000-0x000e53d0) -
pthread.lib.so
map multi-boot module: physical 0x7c16b000 -> [0x000e9000-0x000ed9d4) -
libc_lock_pipe.lib.so
map multi-boot module: physical 0x7c17 -> [0xb021a000-0xb022c9d0) -
libc_terminal.lib.so
map multi-boot module: physical 0x7c183000 -> [0xb022e000-0xb0312a70) -
libiconv.lib.so
map multi-boot module: physical 0x7c268000 -> [0xb0314000-0xb03e9e74) -
stdcxx.lib.so
map multi-boot module: physical 0x7c33e000 -> [0xb03eb000-0xb0520a9c) -
rump.lib.so
map multi-boot module: physical 0x7c474000 -> [0xb0522000-0xb0673c24) -
rump_fs.lib.so
map multi-boot module: physical 0x7c5c6000 ->

Re: Turmvilla scenario

2015-10-09 Thread Vincent Digital

Hi, Christian,

Thanks for clarifying.
I'm using Ubuntu 14.04 32-bit OS as Guest VM.
I've figured out the /home mapping based on the presentation that Norman
created for his presentation earlier this year.

The final issue that I have not get it working is the GRUB configuration
https://github.com/cproc/genode/blob/vbox_vm_linux/doc/virtualbox_setup.txt
 .
It could not work based on the instructions below :

#!/bin/sh



cat <"

On reboot, what is the expected result, am I supposed to be able to choose
between boot-up into Genode or back into the Rescue Linux in the 3rd
partition ?
However, on reboot, I was not able to boot into Genode, just boot straight
into the Rescue Linux O/S in the 3rd partition.
Is there a sample grub2 configuration that I can use to select bootup
either into Genode or the Rescue Linux O/S.

Thanks



On Wed, Oct 7, 2015 at 11:57 PM, Christian Prochaska <
christian.procha...@genode-labs.com> wrote:

> Hello Vincent,
>
> On 10/07/2015 03:23 AM, Vincent Digital wrote:
> > Hi, Can anyone help out. I'm trying to create the Turmvilla scenario on
> my
> > Lenovo X201 By following the setup file as compiled by@cproc
> > <https://github.com/cproc>:
> >
> https://github.com/cproc/genode/blob/vbox_vm_linux/doc/virtualbox_setup.txt
> > I'm trying to understand these parts of the instructions, a bit
> confusing :
> > After creating the 3 partitions and installing the *Create the Linux VM*
> > *  - attach the 3 image files from the /genode directory *
> >
> > >>> How do I attach the image files "linux.vdi" and "home.vmdk" to the
> same Linux VM. "linux.vdi" is of 32 GB while
> > >>>"home.vmdk" is created from /dev/sda2 (at the host disk) which is 60
> GB. I tried to attach both image files to the same
> > >>> SATA controller using the **storage settings of the VM - is this
> correct ?
>
> yes
>
> > * - add a permanent shared folder (for the generated Genode binaries)  -
> > start the VM  - install Linux  - if the Linux installer supports it,
> create
> > an encrypted /home partition on /dev/sdb *
> >
> >
> > >>> "/dev/sdb" refers to the partition within the Guest Linux VM that I
> am installing ? Is it referring to the "home.vmdk" ?**
>
> correct
>
> > >>> How do I specify /home on this partition /dev/sdb ? There are no
> options for input of this folder name.*
> >
>
> Which Linux distribution are you installing as Guest VM?
>
> Christian
>
>
>
>
> --
> Full-scale, agent-less Infrastructure Monitoring from a single dashboard
> Integrate with 40+ ManageEngine ITSM Solutions for complete visibility
> Physical-Virtual-Cloud Infrastructure monitoring from one console
> Real user monitoring with APM Insights and performance trend reports
> Learn More
> http://pubads.g.doubleclick.net/gampad/clk?id=247754911=/4140
> ___
> 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: Announcement: Genode OS Framework version 15.08 released

2015-10-06 Thread Vincent Digital

Hi, Can anyone help out. I'm trying to create the Turmvilla scenario on my
Lenovo X201 By following the setup file as compiled by@cproc
<https://github.com/cproc>:
https://github.com/cproc/genode/blob/vbox_vm_linux/doc/virtualbox_setup.txt
I'm trying to understand these parts of the instructions, a bit confusing :
After creating the 3 partitions and installing the *Create the Linux VM*
*  - attach the 3 image files from the /genode directory *



*   >>> How do I attach the image files "linux.vdi" and "home.vmdk" to the
same Linux VM. "linux.vdi" is of 32 GB while   >>>"home.vmdk" is created
from /dev/sda2 (at the host disk) which is 60 GB. I tried to attach both
image files to the same   >>> SATA controller using the **storage settings
of the VM - is this correct ?*





* - add a permanent shared folder (for the generated Genode binaries)  -
start the VM  - install Linux  - if the Linux installer supports it, create
an encrypted /home partition on /dev/sdb *


*   >>> "/dev/sdb" refers to the partition within the Guest Linux VM that I
am installing ? Is it referring to the "home.vmdk" ?**   >>> How do I
specify /home on this partition /dev/sdb ? There are no options for input
of this folder name.*


*Appreciate if someone can help. Thanks so much.*

On Tue, Sep 1, 2015 at 7:12 PM, Vincent Digital <vdigital3...@gmail.com>
wrote:

> Hi, Alex,
>
> Thanks for the pointer. Will try it out.
>
> Regards.
>
> On Tue, Sep 1, 2015 at 3:36 PM, Alexander Boettcher <
> alexander.boettc...@genode-labs.com> wrote:
>
>> Hello,
>>
>> it is documented here:
>>
>> https://github.com/genodelabs/genode/issues/1552
>>
>> Cheers,
>>
>> Alex.
>>
>> On 01.09.2015 05:12, Vincent Digital wrote:
>> > Hi, congratulations to the release of 15.08 and with it, the use of
>> > Genode/Nova as a day-to-day operating system.
>> > I'm interested to build the same to explore the robustness of Genode -
>> > could you advise which "run" file is used to create the Genode version
>> that
>> > Norman is using ?
>> >
>> > Thanks.
>> >
>> > On Mon, Aug 31, 2015 at 3:54 AM, Christian Helmuth <
>> > christian.helm...@genode-labs.com> wrote:
>> >
>> >> The current release is characterized by our efforts to use Genode as
>> >> day-to-day operating system. From this background, we packed quite a
>> >> few improvements regarding user GUI experience, VirtualBox robustness
>> >> and performance, integration of native Genode applications and guest
>> >> OSes as well as tools to inspect the system behavior into Genode
>> >> 15.08. Beyond that, we're proud to integrate community contributions
>> >> as the support to run Genode base-hw on the Muen separation kernel on
>> >> x86_64 and extended device-driver support for Raspberry Pi and
>> >> Odroid-X2.
>> >>
>> >> In short, version 15.08 comes with the following highlights:
>> >>
>> >>   - Genode/NOVA used as day-to-day operating system
>> >>   - Genode on top of the Muen separation kernel
>> >>   - Kernel-resource management on NOVA and our custom base-hw kernel
>> >>   - Base framework and low-level OS infrastructure
>> >> - Improved audio support
>> >> - Unified networking components
>> >> - Enhanced tracing and file-system facilities
>> >> - Low-complexity software rendering
>> >>   - Device drivers
>> >> - Raspberry Pi and Odroid-X2 on Fiasco.OC, including
>> >>   USB support
>> >> - BCM57cxx network cards
>> >>   - VirtualBox
>> >> - Guest-host integration (policy-based mouse shapes, dynamic
>> >>   adaptation to screen size changes, audio)
>> >> - Multi-processor support
>> >>
>> >> Those and many more improvements are illustrated by the release
>> >> documentation
>> >>
>> >>   http://genode.org/documentation/release-notes/15.08
>> >>
>> >> Best regards
>> >> --
>> >> Christian Helmuth
>> >> Genode Labs
>> >>
>> >> http://www.genode-labs.com/ · http://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
&

Turmvilla scenario

2015-10-06 Thread Vincent Digital

Hi, Can anyone help out. I'm trying to create the Turmvilla scenario on my
Lenovo X201 By following the setup file as compiled by@cproc
:
https://github.com/cproc/genode/blob/vbox_vm_linux/doc/virtualbox_setup.txt
I'm trying to understand these parts of the instructions, a bit confusing :
After creating the 3 partitions and installing the *Create the Linux VM*
*  - attach the 3 image files from the /genode directory *



*   >>> How do I attach the image files "linux.vdi" and "home.vmdk" to the
same Linux VM. "linux.vdi" is of 32 GB while   >>>"home.vmdk" is created
from /dev/sda2 (at the host disk) which is 60 GB. I tried to attach both
image files to the same   >>> SATA controller using the **storage settings
of the VM - is this correct ?*





* - add a permanent shared folder (for the generated Genode binaries)  -
start the VM  - install Linux  - if the Linux installer supports it, create
an encrypted /home partition on /dev/sdb *


*   >>> "/dev/sdb" refers to the partition within the Guest Linux VM that I
am installing ? Is it referring to the "home.vmdk" ?**   >>> How do I
specify /home on this partition /dev/sdb ? There are no options for input
of this folder name.*


*Appreciate if someone can help. Thanks so much.*
--
Full-scale, agent-less Infrastructure Monitoring from a single dashboard
Integrate with 40+ ManageEngine ITSM Solutions for complete visibility
Physical-Virtual-Cloud Infrastructure monitoring from one console
Real user monitoring with APM Insights and performance trend reports 
Learn More http://pubads.g.doubleclick.net/gampad/clk?id=247754911=/4140___
genode-main mailing list
genode-main@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/genode-main

Re: running Virtualbox on Genode

2015-09-24 Thread Vincent Digital

Hi, Alex,

> I notice the vbox_auto_win8 using the "assert_spec 64bit", does this meant
> that this script is for 64-bit Guest OS.

No. By invoking the run script you build Genode - not a VM. The VM image
is provided by you (vdi/iso) and is just used as is. So it means by
invoking the run script the assertion takes care that you build a 64bit
Genode "host".
>> I understand that the various run scripts are to build Genode with
various components including the Guest VM provided in a VDI.
>> The thing that I don't understand are the macros that you use in scripts
- such as "assert_spec".
>> Can you point me to where I can find documentation for the various
macros which I understand are based on Expect.

But still - whatever you buy/setup - you need a way to get serial output
from the machine - otherwise we can't help you really.
>> Noted. I'll try to explore using Intel AMT to support the serial logging.
>> I've acquired a refurbished Lenovo X201, can you advise how I can try to
emulate what Norman is doing - configuration and run scripts.

Thanks.


On Wed, Sep 23, 2015 at 8:01 PM, Alexander Boettcher <
alexander.boettc...@genode-labs.com> wrote:

> Hi Vincent,
>
> On 23.09.2015 04:41, Vincent Digital wrote:
> > I understand without serial port hardware, it is near to impossible to
> > troubleshoot.
>
> Yes.
>
> > Btw, is it necessary to stick to 32-bit versions of the Guest OSs ?
>
> Yes. We don't support 64bit guests currently.
>
> > I notice the vbox_auto_win8 using the "assert_spec 64bit", does this
> meant
> > that this script is for 64-bit Guest OS.
>
> No. By invoking the run script you build Genode - not a VM. The VM image
> is provided by you (vdi/iso) and is just used as is. So it means by
> invoking the run script the assertion takes care that you build a 64bit
> Genode "host".
>
> > Anyway, I would to consult you what are the main hardware features that
> are
> > required to be compatible to the Nova/Genode software ?
>
> Here at Genode Labs we focus for Genode/Nova on Intel-based hardware
> (especially CPU, graphic card, wifi cards) - but not exclusively. In
> principal all other vendors do - but you should expect extra efforts to
> debug things or to develop/port/enable drivers for your devices. The CPU
> must not be too old for the Nova kernel - especially if you want to use
> virtualization extensions. Beginning with 1st generation of Intel Core
> i3/5/7 CPUs you should be fine. Good experience we have with Lenovo
> notebooks which we use regularly/daily to run Genode.
>
> But still - whatever you buy/setup - you need a way to get serial output
> from the machine - otherwise we can't help you really.
>
> Cheers,
>
> Alex.
>
>
> --
> Monitor Your Dynamic Infrastructure at Any Scale With Datadog!
> Get real-time metrics from all of your servers, apps and tools
> in one place.
> SourceForge users - Click here to start your Free Trial of Datadog now!
> http://pubads.g.doubleclick.net/gampad/clk?id=241902991=/4140
> ___
> genode-main mailing list
> genode-main@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/genode-main
>
--
Monitor Your Dynamic Infrastructure at Any Scale With Datadog!
Get real-time metrics from all of your servers, apps and tools
in one place.
SourceForge users - Click here to start your Free Trial of Datadog now!
http://pubads.g.doubleclick.net/gampad/clk?id=241902991=/4140___
genode-main mailing list
genode-main@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/genode-main

Re: running Virtualbox on Genode

2015-09-22 Thread Vincent Digital

Hi, Alex,

After a long break, I would like to update you on my recent work.
I've revisited the run script that you created for a USB boot-up.
It worked - previously it was a careless mistake on my part with the dd
command - use a wrong device name.

The USB boot-up could now boot-up partially but mainly on Acer hardware,
but not on Dell or HP hardware - the screen would hang on the Genode bootup.

For the Acer bootup, it was only partial - after the Windows 7 screen came
up, it seemed "hang" for very long. The mouse pointer can still movec
though.
I understand without serial port hardware, it is near to impossible to
troubleshoot. As such, I am thinking of purchasing a refurbished Lenovo
X201 - the same one that Norman is using.
I also tried using VMware Workstation and Virtualbox to boot up the USB
stick. I even swapped the Guest VMs between Ubuntu and Windows 7. All would
hang after Genode boots up.

Btw, is it necessary to stick to 32-bit versions of the Guest OSs ? I
notice the vbox_auto_win8 using the "assert_spec 64bit", does this meant
that this script is for 64-bit Guest OS.
Anyway, I would to consult you what are the main hardware features that are
required to be compatible to the Nova/Genode software ?

I would like to move on to a hard-disk based configuration in the long run.
I hope to be able to run two operating systems, Windows and a Linux on top
of Genode/Nova, both supporting Java applications. Can you recommend any
scripts or configuration steps that I can use to do such a setup. I am
trying using the vbox_auto_win7 and vbox_auto_win8 scripts.

Thanks.

On Thu, Sep 10, 2015 at 8:06 PM, Vincent Digital <vdigital3...@gmail.com>
wrote:

> Okay, noted. Thanks.
> I'll try again maybe with a new USB stick.
>
> Regards.
>
> On Thu, Sep 10, 2015 at 3:48 PM, Alexander Boettcher <
> alexander.boettc...@genode-labs.com> wrote:
>
>> Some additional note:
>>
>> make sure that you remove/uncomment all RUN_OPT in your etc/build.conf
>> and really replace it by this line:
>>
>> # Set RUN_OPT in your build.conf to: RUN_OPT = --include image/disk
>>
>> Otherwise the resulting image is not in the expected state.
>>
>> Alex.
>>
>> On 10.09.2015 05:38, Vincent Digital wrote:
>> > Hi, Alex,
>> >
>> > I've used your USB_RUN script to create an image file.
>> > I followed your instructions to prepare the USB stick. However, the USB
>> > stick cannot boot up.
>> > Unfortunately, I do not have access to a laptop with serial port so I am
>> > unable to get any logs.
>> > Can I check with you on your instructions (the mini-howto below)
>> instead.
>> > Thanks.
>> >
>> > # Short mini howto for nova_x86_64:
>> > # - assumption - /dev/sdc is your USB stick
>> > # - assumption - you are in the genode source root directory
>> > # - assumption - you have prepared all external ports
>> > # - assumption - you have build the rump tools -> tool/tool_chain_rump
>> > #
>> > # create a nova_x86_64 build directory
>> > # - tool/create_builddir nova_x86_64
>> > #
>> > # Put/symlink your Windows 7 vdi to build/nova_x86_64/win7.vdi
>> > #
>> > # Set RUN_OPT in your build.conf to: RUN_OPT = --include image/disk
>> > #
>> > # Build everything:
>> > # - make -C build/nova_x86_64 run/vbox_usb
>> > #
>> > # Make sure that the USB is not used - all partitions are un-mounted.
>> >>> How should I prepare this USB stick, should it be formatted under a
>> > particular filesystem (ext2, or FAT32)
>> >>> I have tried various ways - delete everything including partitions,
>> etc.
>> > and then create a new partition
>> >>> Can I clarify the steps below are in sequential order
>> >>> 1. dd operation
>> >>> 2. fdisk operation  - delete all partitions, then create a new
>> partition
>> > and then write to disk.
>> >>> 3. Resizefs operation
>> >>> 4. Mount partiton (I tried this but could not get a successful mount
>> > until I create a filesystem using mke2fs. Is this step necessary ?)
>> >
>> > # Copy disk image to your USB stick:
>> > # - sudo dd if=build/nova_x86_64/var/run/vbox_usb.img of=/dev/sdc
>> > #
>> > # Make sure that the USB partition of the stick is un-mounted.
>> > #
>> > # Resize USB stick partition to maximum:
>> > # - sudo fdisk /dev/sdc
>> > # -- delete partition ('d')
>> > # -- create partition - ('p')
>> > # -- write table to disk and exit ('w')
>> > #
>> > # - sudo resize2fs -p /dev/

Re: running Virtualbox on Genode

2015-09-10 Thread Vincent Digital

Okay, noted. Thanks.
I'll try again maybe with a new USB stick.

Regards.

On Thu, Sep 10, 2015 at 3:48 PM, Alexander Boettcher <
alexander.boettc...@genode-labs.com> wrote:

> Some additional note:
>
> make sure that you remove/uncomment all RUN_OPT in your etc/build.conf
> and really replace it by this line:
>
> # Set RUN_OPT in your build.conf to: RUN_OPT = --include image/disk
>
> Otherwise the resulting image is not in the expected state.
>
> Alex.
>
> On 10.09.2015 05:38, Vincent Digital wrote:
> > Hi, Alex,
> >
> > I've used your USB_RUN script to create an image file.
> > I followed your instructions to prepare the USB stick. However, the USB
> > stick cannot boot up.
> > Unfortunately, I do not have access to a laptop with serial port so I am
> > unable to get any logs.
> > Can I check with you on your instructions (the mini-howto below) instead.
> > Thanks.
> >
> > # Short mini howto for nova_x86_64:
> > # - assumption - /dev/sdc is your USB stick
> > # - assumption - you are in the genode source root directory
> > # - assumption - you have prepared all external ports
> > # - assumption - you have build the rump tools -> tool/tool_chain_rump
> > #
> > # create a nova_x86_64 build directory
> > # - tool/create_builddir nova_x86_64
> > #
> > # Put/symlink your Windows 7 vdi to build/nova_x86_64/win7.vdi
> > #
> > # Set RUN_OPT in your build.conf to: RUN_OPT = --include image/disk
> > #
> > # Build everything:
> > # - make -C build/nova_x86_64 run/vbox_usb
> > #
> > # Make sure that the USB is not used - all partitions are un-mounted.
> >>> How should I prepare this USB stick, should it be formatted under a
> > particular filesystem (ext2, or FAT32)
> >>> I have tried various ways - delete everything including partitions,
> etc.
> > and then create a new partition
> >>> Can I clarify the steps below are in sequential order
> >>> 1. dd operation
> >>> 2. fdisk operation  - delete all partitions, then create a new
> partition
> > and then write to disk.
> >>> 3. Resizefs operation
> >>> 4. Mount partiton (I tried this but could not get a successful mount
> > until I create a filesystem using mke2fs. Is this step necessary ?)
> >
> > # Copy disk image to your USB stick:
> > # - sudo dd if=build/nova_x86_64/var/run/vbox_usb.img of=/dev/sdc
> > #
> > # Make sure that the USB partition of the stick is un-mounted.
> > #
> > # Resize USB stick partition to maximum:
> > # - sudo fdisk /dev/sdc
> > # -- delete partition ('d')
> > # -- create partition - ('p')
> > # -- write table to disk and exit ('w')
> > #
> > # - sudo resize2fs -p /dev/sdc1
> > #
> > # Mount Genode partition on USB stick and copy your Windows image to the
> USB
> > # stick:
> > #
> > # - sudo mount /dev/sdc1 /media/genode
> > # - cp build/nova_x86_64/win7.vdi /media/genode/.
> > # - mkdir /media/genode/ram
> > # - cp build/nova_x86_64/bin/overlay_win7.vdi /media/genode/ram/.
> > # - umount /media/genode
> > #
> > # Boot your USB stick. For debugging get the serial output of the test
> > machine.
> > #
> >
> >
> >
> >
> >
> >
> > On Tue, Sep 1, 2015 at 3:03 AM, Alexander Boettcher <
> > alexander.boettc...@genode-labs.com> wrote:
> >
> >> On 28.08.2015 13:44, Alexander Boettcher wrote:
> >>>> The part that I am not sure are the "win7.vdi" and "overlay_win7.vdi"
> >>>> files. How are they linked to the vbox_auto_win7.iso file ?
> >>>> I have copied them onto the thumbdrive but is this correct ?
> >>
> >> You may try the following branch
> >> https://github.com/alex-ab/genode/commits/vbox_usb_run. There exists
> now
> >> a run script called repos/ports/run/vbox_usb.run which helps you in
> >> setting up a Virtualbox on Genode/NOVA running from USB stick and
> >> fetching the Virtualbox image from the vary same USB stick. Please
> >> follow the instruction as described in the run script.
> >>
> >> Still, there a lot of manual steps to go - but it may help a bit.
> >>
> >> Please keep in mind, depending on the read and write performance of your
> >> USB controller and stick the overall experience may be not as good as
> >> when used with a real hard disk.
> >>
> >> Alex.
> >>
> >>
> >>
>

Re: running Virtualbox on Genode

2015-09-09 Thread Vincent Digital

Hi, Alex,

I've used your USB_RUN script to create an image file.
I followed your instructions to prepare the USB stick. However, the USB
stick cannot boot up.
Unfortunately, I do not have access to a laptop with serial port so I am
unable to get any logs.
Can I check with you on your instructions (the mini-howto below) instead.
Thanks.

# Short mini howto for nova_x86_64:
# - assumption - /dev/sdc is your USB stick
# - assumption - you are in the genode source root directory
# - assumption - you have prepared all external ports
# - assumption - you have build the rump tools -> tool/tool_chain_rump
#
# create a nova_x86_64 build directory
# - tool/create_builddir nova_x86_64
#
# Put/symlink your Windows 7 vdi to build/nova_x86_64/win7.vdi
#
# Set RUN_OPT in your build.conf to: RUN_OPT = --include image/disk
#
# Build everything:
# - make -C build/nova_x86_64 run/vbox_usb
#
# Make sure that the USB is not used - all partitions are un-mounted.
>> How should I prepare this USB stick, should it be formatted under a
particular filesystem (ext2, or FAT32)
>> I have tried various ways - delete everything including partitions, etc.
and then create a new partition
>> Can I clarify the steps below are in sequential order
>> 1. dd operation
>> 2. fdisk operation  - delete all partitions, then create a new partition
and then write to disk.
>> 3. Resizefs operation
>> 4. Mount partiton (I tried this but could not get a successful mount
until I create a filesystem using mke2fs. Is this step necessary ?)

# Copy disk image to your USB stick:
# - sudo dd if=build/nova_x86_64/var/run/vbox_usb.img of=/dev/sdc
#
# Make sure that the USB partition of the stick is un-mounted.
#
# Resize USB stick partition to maximum:
# - sudo fdisk /dev/sdc
# -- delete partition ('d')
# -- create partition - ('p')
# -- write table to disk and exit ('w')
#
# - sudo resize2fs -p /dev/sdc1
#
# Mount Genode partition on USB stick and copy your Windows image to the USB
# stick:
#
# - sudo mount /dev/sdc1 /media/genode
# - cp build/nova_x86_64/win7.vdi /media/genode/.
# - mkdir /media/genode/ram
# - cp build/nova_x86_64/bin/overlay_win7.vdi /media/genode/ram/.
# - umount /media/genode
#
# Boot your USB stick. For debugging get the serial output of the test
machine.
#






On Tue, Sep 1, 2015 at 3:03 AM, Alexander Boettcher <
alexander.boettc...@genode-labs.com> wrote:

> On 28.08.2015 13:44, Alexander Boettcher wrote:
> >> The part that I am not sure are the "win7.vdi" and "overlay_win7.vdi"
> >> files. How are they linked to the vbox_auto_win7.iso file ?
> >> I have copied them onto the thumbdrive but is this correct ?
>
> You may try the following branch
> https://github.com/alex-ab/genode/commits/vbox_usb_run. There exists now
> a run script called repos/ports/run/vbox_usb.run which helps you in
> setting up a Virtualbox on Genode/NOVA running from USB stick and
> fetching the Virtualbox image from the vary same USB stick. Please
> follow the instruction as described in the run script.
>
> Still, there a lot of manual steps to go - but it may help a bit.
>
> Please keep in mind, depending on the read and write performance of your
> USB controller and stick the overall experience may be not as good as
> when used with a real hard disk.
>
> Alex.
>
>
> --
> ___
> genode-main mailing list
> genode-main@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/genode-main
>
--
Monitor Your Dynamic Infrastructure at Any Scale With Datadog!
Get real-time metrics from all of your servers, apps and tools
in one place.
SourceForge users - Click here to start your Free Trial of Datadog now!
http://pubads.g.doubleclick.net/gampad/clk?id=241902991=/4140___
genode-main mailing list
genode-main@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/genode-main

Re: Announcement: Genode OS Framework version 15.08 released

2015-09-01 Thread Vincent Digital

Hi, Alex,

Thanks for the pointer. Will try it out.

Regards.

On Tue, Sep 1, 2015 at 3:36 PM, Alexander Boettcher <
alexander.boettc...@genode-labs.com> wrote:

> Hello,
>
> it is documented here:
>
> https://github.com/genodelabs/genode/issues/1552
>
> Cheers,
>
> Alex.
>
> On 01.09.2015 05:12, Vincent Digital wrote:
> > Hi, congratulations to the release of 15.08 and with it, the use of
> > Genode/Nova as a day-to-day operating system.
> > I'm interested to build the same to explore the robustness of Genode -
> > could you advise which "run" file is used to create the Genode version
> that
> > Norman is using ?
> >
> > Thanks.
> >
> > On Mon, Aug 31, 2015 at 3:54 AM, Christian Helmuth <
> > christian.helm...@genode-labs.com> wrote:
> >
> >> The current release is characterized by our efforts to use Genode as
> >> day-to-day operating system. From this background, we packed quite a
> >> few improvements regarding user GUI experience, VirtualBox robustness
> >> and performance, integration of native Genode applications and guest
> >> OSes as well as tools to inspect the system behavior into Genode
> >> 15.08. Beyond that, we're proud to integrate community contributions
> >> as the support to run Genode base-hw on the Muen separation kernel on
> >> x86_64 and extended device-driver support for Raspberry Pi and
> >> Odroid-X2.
> >>
> >> In short, version 15.08 comes with the following highlights:
> >>
> >>   - Genode/NOVA used as day-to-day operating system
> >>   - Genode on top of the Muen separation kernel
> >>   - Kernel-resource management on NOVA and our custom base-hw kernel
> >>   - Base framework and low-level OS infrastructure
> >> - Improved audio support
> >> - Unified networking components
> >> - Enhanced tracing and file-system facilities
> >> - Low-complexity software rendering
> >>   - Device drivers
> >> - Raspberry Pi and Odroid-X2 on Fiasco.OC, including
> >>   USB support
> >> - BCM57cxx network cards
> >>   - VirtualBox
> >> - Guest-host integration (policy-based mouse shapes, dynamic
> >>   adaptation to screen size changes, audio)
> >> - Multi-processor support
> >>
> >> Those and many more improvements are illustrated by the release
> >> documentation
> >>
> >>   http://genode.org/documentation/release-notes/15.08
> >>
> >> Best regards
> >> --
> >> Christian Helmuth
> >> Genode Labs
> >>
> >> http://www.genode-labs.com/ · http://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
> >>
> >>
> >>
> --
> >> ___
> >> 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
> >
>
>
>
> --
> ___
> 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: Announcement: Genode OS Framework version 15.08 released

2015-08-31 Thread Vincent Digital

Hi, congratulations to the release of 15.08 and with it, the use of
Genode/Nova as a day-to-day operating system.
I'm interested to build the same to explore the robustness of Genode -
could you advise which "run" file is used to create the Genode version that
Norman is using ?

Thanks.

On Mon, Aug 31, 2015 at 3:54 AM, Christian Helmuth <
christian.helm...@genode-labs.com> wrote:

> The current release is characterized by our efforts to use Genode as
> day-to-day operating system. From this background, we packed quite a
> few improvements regarding user GUI experience, VirtualBox robustness
> and performance, integration of native Genode applications and guest
> OSes as well as tools to inspect the system behavior into Genode
> 15.08. Beyond that, we're proud to integrate community contributions
> as the support to run Genode base-hw on the Muen separation kernel on
> x86_64 and extended device-driver support for Raspberry Pi and
> Odroid-X2.
>
> In short, version 15.08 comes with the following highlights:
>
>   - Genode/NOVA used as day-to-day operating system
>   - Genode on top of the Muen separation kernel
>   - Kernel-resource management on NOVA and our custom base-hw kernel
>   - Base framework and low-level OS infrastructure
> - Improved audio support
> - Unified networking components
> - Enhanced tracing and file-system facilities
> - Low-complexity software rendering
>   - Device drivers
> - Raspberry Pi and Odroid-X2 on Fiasco.OC, including
>   USB support
> - BCM57cxx network cards
>   - VirtualBox
> - Guest-host integration (policy-based mouse shapes, dynamic
>   adaptation to screen size changes, audio)
> - Multi-processor support
>
> Those and many more improvements are illustrated by the release
> documentation
>
>   http://genode.org/documentation/release-notes/15.08
>
> Best regards
> --
> Christian Helmuth
> Genode Labs
>
> http://www.genode-labs.com/ · http://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
>
>
> --
> ___
> 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: Problems with building NetBSD rump filesystem

2015-08-28 Thread Vincent Digital

Hi,

I've found what is missing - I forgot to install the pre-requisite
libSDL-dev package. After installing with sudo apt-get install
libSDL-dev.
All previous make issues are resolved.  Thanks everyone for your help.

I could now proceed to my next stage - basically to build a Genode system
with NOVA micro-kernel, running Virtualbox with a Windows 7 VM.
I have managed to make the vbox_auto_win7.run script - everything is made
successfully and the output is a vbox_auto_win7.iso file.
However, when I tried to use the vbox_auto_win7.iso file and put it onto
a USB thumdrive to run. The result is that after boot-up, it just hang.

The part that I am not sure are the win7.vdi and overlay_win7.vdi
files. How are they linked to the vbox_auto_win7.iso file ?
I have copied them onto the thumbdrive but is this correct ?

I have tried to understand the email exchange on
http://sourceforge.net/p/genode/mailman/message/33496592/ discussion
between Christian and Adrian.
Does anyone have a blueprint on how I can create a win7.vdi using an
existing Windows 7 DVD onto a ext2 partition.
How is this win7.vdi file subsequently linked to the
vbox_auto_win7.iso  file .

Can anyone advise.

Thanks in advance.

Regards.

On Thu, Aug 27, 2015 at 10:44 PM, Christian Helmuth 
christian.helm...@genode-labs.com wrote:

 Hello Vincent,

 On Thu, Aug 27, 2015 at 06:41:04PM +0800, Vincent Digital wrote:
  On Wed, Aug 26, 2015 at 11:16 PM, Sebastian Sumpf 
 sebastian.su...@genode-labs.com wrote:
   The rump tools will be executed on your host system, i.e. Linux
   3.19.0-25-generic x86_64, not within Genode, they are needed to compile
   rump. Do you have the zlib package installed in your Linux
 distribution?
  
 
  Yes, I have installed the zlib package via sudo apt-get install zlibc.
  I have used ./tool/ports/prepare_port zlib to prepare the zlib port as
  well.
  For the rump tools, are you referring to the dde_rump which I had
  prepared by using ./tool/ports/prepare_port dde_rump.
  Finally, I used the tool chain make to build up everything - make
  server/rump_fs or make run/rump_ext2.
  Did I miss out anything ?

 The zlib Debian package (or zlib1g on Ubuntu) is just the binary part,
 i.e., the library already linked programs depend on. For building the
 rump tools you also need the development package containing the C
 header files used on compilation of the sources. On my Ubuntu, the
 package is called zlib1g-dev, so you may try

   apt-get install zlib-dev   or
   aptitude install zlib-dev

 on your Debian system.

 Regards
 --
 Christian Helmuth
 Genode Labs

 http://www.genode-labs.com/ · http://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


 --
 ___
 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: Problems with building NetBSD rump filesystem

2015-08-27 Thread Vincent Digital

Hi, Sebastian,


On Wed, Aug 26, 2015 at 11:16 PM, Sebastian Sumpf 
sebastian.su...@genode-labs.com wrote:

 Hi Vincent,

 On 08/26/2015 03:14 AM, Vincent Digital wrote:
  configure: error: zlib must be installed in a compiler-visible path
  --- config.cache ---
  *** [config.cache] Error code 1

 it seems like the error occurred when building the rump tools:

  nbmake[6]: stopped in
 /home/vincent/genode/contrib/dde_rump-8719ed349bf425eb570d0ee7f16acf980b44adb4/src/lib/dde_rump/src/tools/compat

 The rump tools will be executed on your host system, i.e. Linux
 3.19.0-25-generic x86_64, not within Genode, they are needed to compile
 rump. Do you have the zlib package installed in your Linux distribution?


 Yes, I have installed the zlib package via sudo apt-get install zlibc.
 I have used ./tool/ports/prepare_port zlib to prepare the zlib port as
well.
 For the rump tools, are you referring to the dde_rump which I had
prepared by using ./tool/ports/prepare_port dde_rump.
 Finally, I used the tool chain make to build up everything - make
server/rump_fs or make run/rump_ext2.
 Did I miss out anything ?


 Regards,

 Sebastian



 --
 Sebastian Sumpf
 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





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

Problems with building NetBSD rump filesystem

2015-08-25 Thread Vincent Digital

Hi,

Could anyone help and advise how to resolve the issue below ?
I've ported and prepared the NetBsd build infra- using prepare_port
dde_rump successfully. I've also prepare_port zlib as well.
However, when I run make server/rump_fs. I encountered the following
output :


~/genode/build_nova$ make server/rump_fs
checking library dependencies...
  Library platform
MERGEplatform.lib.a
  Library ldso-startup
COMPILE  startup.o
MERGEldso-startup.lib.a
  Library cxx
COMPILE  exception.o
COMPILE  guard.o
COMPILE  malloc_free.o
COMPILE  misc.o
COMPILE  new_delete.o
COMPILE  unwind.o
MERGEsupc++.o
CONVERT  supc++.o
MERGEcxx.lib.a
  Library syscall
MERGEsyscall.lib.a
  Library startup
COMPILE  _main.o
ASSEMBLE crt0.o
COMPILE  init_main_thread.o
MERGEstartup.lib.a
  Library base-common
COMPILE  allocator/allocator_avl.o
COMPILE  allocator/slab.o
COMPILE  avl_tree/avl_tree.o
COMPILE  child/child.o
COMPILE  console/console.o
COMPILE  elf/elf_binary.o
COMPILE  env/cap_map.o
COMPILE  heap/heap.o
COMPILE  heap/sliced_heap.o
COMPILE  ipc/ipc.o
COMPILE  lock/lock.o
COMPILE  process/process.o
COMPILE  server/server.o
COMPILE  signal/common.o
COMPILE  signal/platform.o
COMPILE  signal/signal.o
COMPILE  thread/context_allocator.o
COMPILE  thread/myself.o
COMPILE  thread/thread.o
COMPILE  thread/thread_context.o
COMPILE  thread/trace.o
MERGEbase-common.lib.a
  Library base
COMPILE  console/log_console.o
COMPILE  cpu/cache.o
COMPILE  env/context_area.o
COMPILE  env/env.o
COMPILE  env/reinitialize.o
COMPILE  irq/platform.o
COMPILE  thread/thread_nova.o
MERGEbase.lib.a
  Library alarm
COMPILE  alarm.o
MERGEalarm.lib.a
  Library timed_semaphore
COMPILE  timed_semaphore.o
MERGEtimed_semaphore.lib.a
  Library config
COMPILE  config.o
MERGEconfig.lib.a
  Library ld
COMPILE  debug.o
COMPILE  dependency.o
COMPILE  exception.o
COMPILE  file.o
ASSEMBLE jmp_slot.o
COMPILE  main.o
COMPILE  shared_object.o
COMPILE  test.o
MERGEld.lib.so
  Library rump
CC=/usr/local/genode-gcc/bin/genode-x86-gcc BUILD_CC=cc BUILD_AR=ar
BUILD_NM=nm BUILD_OBJCOPY=objcopy AR=/usr/local/genode-gcc/bin/genode-x86-ar
NM=/usr/local/genode-gcc/bin/genode-x86-nm
OBJCOPY=/usr/local/genode-gcc/bin/genode-x86-objcopy
CC_TARGET=genode-x86-gcc /home/vincent/genode/contrib/dde_rump-
8719ed349bf425eb570d0ee7f16acf980b44adb4/src/lib/dde_rump/buildrump.sh -k
-V'MAKEVERBOSE=0' -V'NOGCCERROR=1'  -V'RUMP_LOCKS_UP=yes' -s
/home/vincent/genode/contrib/dde_rump-8719ed349bf425eb570d0ee7f16acf
980b44adb4/src/lib/dde_rump/src -T
/home/vincent/genode/build_nova/var/libcache/rump/tools
-o /home/vincent/genode/build_nova/var/libcache/rump/obj -d
/home/vincent/genode/build_nova/var/libcache/rump -N -V
RUMP_KERNEL_IS_LIBC=1 tools
MACH_ARCH cc x86

 WARNING: repository in /home/vincent/genode/contrib/dde_rump-
8719ed349bf425eb570d0ee7f16acf980b44adb4/src/lib/dde_rump/src is not clean

Tool  CC: /usr/local/genode-gcc/bin/genode-x86-gcc
Tool  AR: /usr/local/genode-gcc/bin/genode-x86-ar
Tool  NM: /usr/local/genode-gcc/bin/genode-x86-nm
Tool  OBJCOPY   : /usr/local/genode-gcc/bin/genode-x86-objcopy
Cmd   SRCDIR: /home/vincent/genode/contrib/dde_rump-
8719ed349bf425eb570d0ee7f16acf980b44adb4/src/lib/dde_rump/src
Cmd   DESTDIR   : /home/vincent/genode/build_nova/var/libcache/rump
Cmd   OBJDIR: /home/vincent/genode/build_
nova/var/libcache/rump/obj
Cmd   BRTOOLDIR : /home/vincent/genode/build_
nova/var/libcache/rump/tools
Cmd   DBG   : -O2 -g
Cmd   make -j[num]  : -j 4
Cmd   RUMPKERN_ONLY : yes
Cmd   CPPFLAGS  : -D__NetBSD__
Probe CPPFLAGS  : -D'CTASSERT(x)='
Probe RUMP_VIRTIF   : no
Probe RUMP_LDSCRIPT : no
 Build environment (from shell)
Env   BUILDRUMP_CPPFLAGS:
Env   BUILDRUMP_CFLAGS  :
Env   BUILDRUMP_AFLAGS  :
Env   BUILDRUMP_LDFLAGS :
=== build.sh command:./build.sh -m amd64 -u -D
/home/vincent/genode/build_nova/var/libcache/rump/tools/dest -w
/home/vincent/genode/build_nova/var/libcache/rump/tools/rumpmake -T
/home/vincent/genode/build_nova/var/libcache/rump/tools -j 4 -N2 -E -Z S -V
EXTERNAL_TOOLCHAIN=/home/vincent/genode/build_nova/var/libcache/rump/tools
-V TOOLCHAIN_MISSING=yes -V TOOLS_BUILDRUMP=yes -V MKGROFF=no -V MKLINT=no
-V MKZFS=no -V MKDYNAMICROOT=no -V TOPRUMP=/home/vincent/genode/
contrib/dde_rump-8719ed349bf425eb570d0ee7f16acf980b44adb4/src/lib/dde_rump/src/sys/rump
-V MAKECONF=/home/vincent/genode/build_nova/var/libcache/rump/tools/mk.conf
-V MAKEOBJDIR=${.CURDIR:C,^(/home/vincent/genode/contrib/dde_rump-
8719ed349bf425eb570d0ee7f16acf980b44adb4/src/lib/dde_rump/
src|/home/vincent/genode/contrib/dde_rump-8719ed349bf425eb570d0ee7f16acf

Re: Turmvilla scenario

Re: Turmvilla scenario

Re: Turmvilla scenario

Re: Turmvilla scenario

Turmvilla scenario

Re: Turmvilla scenario

Re: Turmvilla scenario

Turmvilla scenario

Re: Turmvilla scenario

Re: Announcement: Genode OS Framework version 15.08 released

Turmvilla scenario

Re: running Virtualbox on Genode

Re: running Virtualbox on Genode

Re: running Virtualbox on Genode

Re: running Virtualbox on Genode

Re: Announcement: Genode OS Framework version 15.08 released

Re: Announcement: Genode OS Framework version 15.08 released

Re: Problems with building NetBSD rump filesystem

Re: Problems with building NetBSD rump filesystem

Problems with building NetBSD rump filesystem

20 matches

Site Navigation

Mail list logo

Footer information