Re: run/demo in VirtualBox
Thanks, Christian. This commit works (actually I just grabbed the HEAD of the lxip_arp branch: 67835617). I tried to do my due diligence by looking for this issue in the mailing list. Next time I'll check the issues list as well. Regards, Tom On Wed, Oct 4, 2017 at 5:54 AM, Christian Helmuth < christian.helm...@genode-labs.com> wrote: > Hello Thomas, > > On Mon, Oct 02, 2017 at 11:37:40PM -0500, Thomas Dundon wrote: > > I cannot get the basic demo to work inside my VM. Here's my setup: > > > >- x86_64 machine running > >- Windows 7 running > >- VirtualBox 5.1.28 running > >- Ubuntu 16.04 > > > > ... > > this issue was discovered before and the progress is documented in the > following ticket of our issue tracker. > > https://github.com/genodelabs/genode/issues/2521 > > Please give the mentioned commit a try. It fixes the issue for with > 16.04 and linux kernel 4.4.0-93-generic as well as 4.4.0-96-generic. > > https://github.com/chelmuth/genode/commit/03a17e2cf61879cdfecb32df1484b3 > d058231a48 > > Greets > -- > Christian Helmuth > Genode Labs > -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ genode-main mailing list genode-main@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/genode-main
Re: run/demo in VirtualBox
Hello Thomas, On Mon, Oct 02, 2017 at 11:37:40PM -0500, Thomas Dundon wrote: > I cannot get the basic demo to work inside my VM. Here's my setup: > >- x86_64 machine running >- Windows 7 running >- VirtualBox 5.1.28 running >- Ubuntu 16.04 > > My process within the Ubuntu VM was: > >- Installed the various tools to build (genode-toolchain-17.05, >libsdl2-dev, etc) >- Ran git clone to get Genode 17.08 >- Ran *./tool/create_builddir linux BUILD_DIR=../build* >- Changed *build.conf* to enable MAKE += -j4 >- Ran *make run/demo* > > Everything builds fine but nothing significant happens. Here's the console > output (post build): > > using 'core-linux' as 'core' > using 'ld-linux.lib.so' as 'ld.lib.so' > using 'linux_timer_drv' as 'timer' > spawn ./core > Genode 17.08 > > 17592186044415 MiB RAM and 8997 caps assigned to init > Warning: blocking canceled in entrypoint constructor > this issue was discovered before and the progress is documented in the following ticket of our issue tracker. https://github.com/genodelabs/genode/issues/2521 Please give the mentioned commit a try. It fixes the issue for with 16.04 and linux kernel 4.4.0-93-generic as well as 4.4.0-96-generic. https://github.com/chelmuth/genode/commit/03a17e2cf61879cdfecb32df1484b3d058231a48 Greets -- Christian Helmuth Genode Labs https://www.genode-labs.com/ · https://genode.org/ https://twitter.com/GenodeLabs · /ˈdʒiː.nəʊd/ Genode Labs GmbH · Amtsgericht Dresden · HRB 28424 · Sitz Dresden Geschäftsführer: Dr.-Ing. Norman Feske, Christian Helmuth -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ genode-main mailing list genode-main@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/genode-main
run/demo in VirtualBox
Hi, I cannot get the basic demo to work inside my VM. Here's my setup: - x86_64 machine running - Windows 7 running - VirtualBox 5.1.28 running - Ubuntu 16.04 My process within the Ubuntu VM was: - Installed the various tools to build (genode-toolchain-17.05, libsdl2-dev, etc) - Ran git clone to get Genode 17.08 - Ran *./tool/create_builddir linux BUILD_DIR=../build* - Changed *build.conf* to enable MAKE += -j4 - Ran *make run/demo* Everything builds fine but nothing significant happens. Here's the console output (post build): using 'core-linux' as 'core' using 'ld-linux.lib.so' as 'ld.lib.so' using 'linux_timer_drv' as 'timer' spawn ./core Genode 17.08 17592186044415 MiB RAM and 8997 caps assigned to init Warning: blocking canceled in entrypoint constructor If I check the process list (before the Ctrl-C) I don't see anything other than *make*, *expect*, and *core*. After attaching gdb to the (unstripped) *core *process I see that one thread is sleeping in* _sig_rec->block_for_signal()* and another thread is sleeping in *_wait_for_exit_sem.down()*. The huge RAM allocation for init seems unreasonable, but I saw some similar output in other posts. Is the "blocking canceled" warning to be expected? Should I see the other processes listed in *launchpad.config* running? Just to be safe I've redone all these steps multiple times and even built the genode toolchain from source. What should I check next? Thanks, Tom -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ genode-main mailing list genode-main@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/genode-main
