Hi,
I am trying to run the demo and a QEMU appeared with a blank screen although before thr blank screen appeared it did display messages that looks like from the NOVA hypervisor loading.
The log can be found on this pastebin: http://pastebin.com/8P3UF7Zt
The image screenshot can be seen from: http://i.imgur.com/lp8uVvO.jpg
Is it normal for the demo to appear as a blank screen. I remembered when I built he NOVA for 15.05 it showed a nitpicker GUI demo screen though.
Regards, Thoth.
Hi,
The above image link is a typo. The correct link is:
http://i.imgur.com/lp8uVyO.jpg On 2 Sep 2015 11:48 am, "Thotheolh Tay" <twzgerald@...9...> wrote:
Hi,
I am trying to run the demo and a QEMU appeared with a blank screen although before thr blank screen appeared it did display messages that looks like from the NOVA hypervisor loading.
The log can be found on this pastebin: http://pastebin.com/8P3UF7Zt
The image screenshot can be seen from: http://i.imgur.com/lp8uVvO.jpg
Is it normal for the demo to appear as a blank screen. I remembered when I built he NOVA for 15.05 it showed a nitpicker GUI demo screen though.
Regards, Thoth.
Hi,
From the log it seems your PS/2 driver suffers a ring-buffer overflow. What's your Qemu version?
Greets Christian
Am 2. September 2015 05:54:40 MESZ, schrieb Thotheolh Tay <twzgerald@...51....>:
Hi,
The above image link is a typo. The correct link is:
http://i.imgur.com/lp8uVyO.jpg On 2 Sep 2015 11:48 am, "Thotheolh Tay" <twzgerald@...9...> wrote:
Hi,
I am trying to run the demo and a QEMU appeared with a blank screen although before thr blank screen appeared it did display messages
that
looks like from the NOVA hypervisor loading.
The log can be found on this pastebin: http://pastebin.com/8P3UF7Zt
The image screenshot can be seen from: http://i.imgur.com/lp8uVvO.jpg
Is it normal for the demo to appear as a blank screen. I remembered
when I
built he NOVA for 15.05 it showed a nitpicker GUI demo screen though.
Regards, Thoth.
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&iu=/4140
genode-main mailing list genode-main@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/genode-main
Hi,
QEMU emulator version 2.0.0 (Debian 2.0.0+dfsg-2ubuntu1.17. On 2 Sep 2015 1:21 pm, "Christian Helmuth" < christian.helmuth@...1...> wrote:
Hi,
From the log it seems your PS/2 driver suffers a ring-buffer overflow. What's your Qemu version?
Greets Christian
Am 2. September 2015 05:54:40 MESZ, schrieb Thotheolh Tay < twzgerald@...9...>:
Hi,
The above image link is a typo. The correct link is:
http://i.imgur.com/lp8uVyO.jpg On 2 Sep 2015 11:48 am, "Thotheolh Tay" <twzgerald@...9...> wrote:
Hi,
I am trying to run the demo and a QEMU appeared with a blank screen although before thr blank screen appeared it did display messages
that
looks like from the NOVA hypervisor loading.
The log can be found on this pastebin: http://pastebin.com/8P3UF7Zt
The image screenshot can be seen from: http://i.imgur.com/lp8uVvO.jpg
Is it normal for the demo to appear as a blank screen. I remembered
when I
built he NOVA for 15.05 it showed a nitpicker GUI demo screen though.
Regards, Thoth.
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&iu=/4140
genode-main mailing list genode-main@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/genode-main
-- Christian Helmuth Genode Labs
http://www.genode-labs.com/ · http://genode.org/ · /ˈdʒiː.nəʊd/
Genode Labs GmbH · Amtsgericht Dresden · HRB 28424 · Sitz Dresden Geschäftsführer: Dr.-Ing. Norman Feske, Christian Helmuth
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&iu=/4140 _______________________________________________ genode-main mailing list genode-main@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/genode-main
Hello,
I experiences similar problems using the exact same Qemu version as yours. To work around it, I first instructed Qemu to use the SDL back end by adding the following line to the Genode build configuration at '<build-dir>/etc/build.conf':
QEMU_OPT += -display sdl
But that was not enough to fix the bugged user input. I also had to set the environment variable SDL_VIDEO_X11_DGAMOUSE to 0.
export SDL_VIDEO_X11_DGAMOUSE=0
This fixed the problem for me. But I still have not investigated what strange kind of events Qemu is delivering by default now. The events seem to confuse the PS/2 driver completely.
Cheers Norman
Hi,
Do you need me to open a bug on the Github for this ?
On Wed, Sep 2, 2015 at 4:53 PM, Norman Feske <norman.feske@...1...> wrote:
Hello,
I experiences similar problems using the exact same Qemu version as yours. To work around it, I first instructed Qemu to use the SDL back end by adding the following line to the Genode build configuration at '<build-dir>/etc/build.conf':
QEMU_OPT += -display sdl
But that was not enough to fix the bugged user input. I also had to set the environment variable SDL_VIDEO_X11_DGAMOUSE to 0.
export SDL_VIDEO_X11_DGAMOUSE=0
This fixed the problem for me. But I still have not investigated what strange kind of events Qemu is delivering by default now. The events seem to confuse the PS/2 driver completely.
Cheers Norman
-- Dr.-Ing. Norman Feske 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
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&iu=/4140 _______________________________________________ genode-main mailing list genode-main@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/genode-main
Hi Thotheolh,
On 04.09.2015 15:08, Thotheolh Tay wrote:
Do you need me to open a bug on the Github for this ?
just out of curiosity, did my workaround work for you?
I investigated the symptom a bit further by instrumenting Qemu (hw/input/ps2.c). The function 'ps2_mouse_event' is called with bogus arguments for dx and dy. It receives relative motion values in the order of thousands. Normally one would expect single-digit numbers. Qemu now tries to convert those values into a sequence of PS/2 packets. Because the values are so extreme, a flood of PS/2 packets is generated, which eventually triggers the overrun of an internal queue in our PS/2 driver. This would never occur at a normal rate of events. The problem stems from the fact that Qemu receives bogus motion events unless SDL's DGAMOUSE parameter is set to 0. I am afraid that we won't be able to solve or work around it within Genode. The problem lies somewhere in libSDL or Qemu. Hence, opening an issue at our issue tracker seems futile.
I guess that the problem only occurs when executing Qemu within a guest OS. E.g., I am running Qemu on Linux inside VirtualBox. Is this similar to your setup?
Cheers Norman
Hi,
I have not tried the workaround yet.
My environment is a LinuxMint 17.2 64 bit in VirtualBox with Qemu which is the same as yours.
On Fri, Sep 4, 2015 at 9:26 PM, Norman Feske <norman.feske@...1...> wrote:
Hi Thotheolh,
On 04.09.2015 15:08, Thotheolh Tay wrote:
Do you need me to open a bug on the Github for this ?
just out of curiosity, did my workaround work for you?
I investigated the symptom a bit further by instrumenting Qemu (hw/input/ps2.c). The function 'ps2_mouse_event' is called with bogus arguments for dx and dy. It receives relative motion values in the order of thousands. Normally one would expect single-digit numbers. Qemu now tries to convert those values into a sequence of PS/2 packets. Because the values are so extreme, a flood of PS/2 packets is generated, which eventually triggers the overrun of an internal queue in our PS/2 driver. This would never occur at a normal rate of events. The problem stems from the fact that Qemu receives bogus motion events unless SDL's DGAMOUSE parameter is set to 0. I am afraid that we won't be able to solve or work around it within Genode. The problem lies somewhere in libSDL or Qemu. Hence, opening an issue at our issue tracker seems futile.
I guess that the problem only occurs when executing Qemu within a guest OS. E.g., I am running Qemu on Linux inside VirtualBox. Is this similar to your setup?
Cheers Norman
-- Dr.-Ing. Norman Feske 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
Hi Norman,
I have successfully managed to launch the NOVA in demo with your suggestions.
What other run options do I have besides demo ? On 4 Sep 2015 10:41 pm, "Thotheolh Tay" <twzgerald@...9...> wrote:
Hi,
I have not tried the workaround yet.
My environment is a LinuxMint 17.2 64 bit in VirtualBox with Qemu which is the same as yours.
On Fri, Sep 4, 2015 at 9:26 PM, Norman Feske <norman.feske@...1...
wrote:
Hi Thotheolh,
On 04.09.2015 15:08, Thotheolh Tay wrote:
Do you need me to open a bug on the Github for this ?
just out of curiosity, did my workaround work for you?
I investigated the symptom a bit further by instrumenting Qemu (hw/input/ps2.c). The function 'ps2_mouse_event' is called with bogus arguments for dx and dy. It receives relative motion values in the order of thousands. Normally one would expect single-digit numbers. Qemu now tries to convert those values into a sequence of PS/2 packets. Because the values are so extreme, a flood of PS/2 packets is generated, which eventually triggers the overrun of an internal queue in our PS/2 driver. This would never occur at a normal rate of events. The problem stems from the fact that Qemu receives bogus motion events unless SDL's DGAMOUSE parameter is set to 0. I am afraid that we won't be able to solve or work around it within Genode. The problem lies somewhere in libSDL or Qemu. Hence, opening an issue at our issue tracker seems futile.
I guess that the problem only occurs when executing Qemu within a guest OS. E.g., I am running Qemu on Linux inside VirtualBox. Is this similar to your setup?
Cheers Norman
-- Dr.-Ing. Norman Feske 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
-- ,----------------------------------------------------------, PGP Secure Email Key ID:6FBFC19D 7721 3E54 FA6D B79D AFE6 AC45 8885 F995 6FBF C19D '----------------------------------------------------------'
Hi,
I decided to take a look around after managing to run the demo nitpicker via "make run/demo" and so now I did a cd into the "GENODE_DIR\repos\ports\run" folder and found some ".run" scripts inside. I changed them to 777 permission as I noticed the permissions do not allow execute somehow and did a "./virtualbox.run" to test out the script. It threw me a
line 7: core: command not found line 8: drivers/framebuffer: No such file or directory line 9: drivers/timer: No such fole or directory line 10: syntax error near unexpected token '}' line 10: '}'
Am I running it to correct manner ? On 7 Sep 2015 1:43 pm, "Thotheolh Tay" <twzgerald@...9...> wrote:
Hi Norman,
I have successfully managed to launch the NOVA in demo with your suggestions.
What other run options do I have besides demo ? On 4 Sep 2015 10:41 pm, "Thotheolh Tay" <twzgerald@...9...> wrote:
Hi,
I have not tried the workaround yet.
My environment is a LinuxMint 17.2 64 bit in VirtualBox with Qemu which is the same as yours.
On Fri, Sep 4, 2015 at 9:26 PM, Norman Feske < norman.feske@...1...> wrote:
Hi Thotheolh,
On 04.09.2015 15:08, Thotheolh Tay wrote:
Do you need me to open a bug on the Github for this ?
just out of curiosity, did my workaround work for you?
I investigated the symptom a bit further by instrumenting Qemu (hw/input/ps2.c). The function 'ps2_mouse_event' is called with bogus arguments for dx and dy. It receives relative motion values in the order of thousands. Normally one would expect single-digit numbers. Qemu now tries to convert those values into a sequence of PS/2 packets. Because the values are so extreme, a flood of PS/2 packets is generated, which eventually triggers the overrun of an internal queue in our PS/2 driver. This would never occur at a normal rate of events. The problem stems from the fact that Qemu receives bogus motion events unless SDL's DGAMOUSE parameter is set to 0. I am afraid that we won't be able to solve or work around it within Genode. The problem lies somewhere in libSDL or Qemu. Hence, opening an issue at our issue tracker seems futile.
I guess that the problem only occurs when executing Qemu within a guest OS. E.g., I am running Qemu on Linux inside VirtualBox. Is this similar to your setup?
Cheers Norman
-- Dr.-Ing. Norman Feske 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
-- ,----------------------------------------------------------, PGP Secure Email Key ID:6FBFC19D 7721 3E54 FA6D B79D AFE6 AC45 8885 F995 6FBF C19D '----------------------------------------------------------'
Hello,
On 07.09.2015 08:05, Thotheolh Tay wrote:
I decided to take a look around after managing to run the demo nitpicker via "make run/demo" and so now I did a cd into the "GENODE_DIR\repos\ports\run" folder and found some ".run" scripts inside. I changed them to 777 permission as I noticed the permissions do not allow execute somehow and did a "./virtualbox.run" to test out the script. It threw me a
line 7: core: command not found line 8: drivers/framebuffer: No such file or directory line 9: drivers/timer: No such fole or directory line 10: syntax error near unexpected token '}' line 10: '}'
Am I running it to correct manner ?
run scripts cannot be executed directly but are taken as input of the so-called run tool when invoking 'make run/<run-script-name>' from within the build directory. Please refer to Section "2.4. A simple system scenario" and Section "5.4.1. Run tool" of the documentation [1] to learn more about the underlying concept.
[1] http://genode.org/documentation/genode-foundations-15-05.pdf
Regards Norman
Hi,
I entered the build directory and ran "make run/virtualbox" and the resulting message is:
Error: No run script for virtualbox make: *** [run/virtualbox] Error 255 On 7 Sep 2015 9:06 pm, "Norman Feske" <norman.feske@...1...> wrote:
Hello,
On 07.09.2015 08:05, Thotheolh Tay wrote:
I decided to take a look around after managing to run the demo nitpicker via "make run/demo" and so now I did a cd into the "GENODE_DIR\repos\ports\run" folder and found some ".run" scripts inside. I changed them to 777 permission as I noticed the permissions do not allow execute somehow and did a "./virtualbox.run" to test out the script. It threw me a
line 7: core: command not found line 8: drivers/framebuffer: No such file or directory line 9: drivers/timer: No such fole or directory line 10: syntax error near unexpected token '}' line 10: '}'
Am I running it to correct manner ?
run scripts cannot be executed directly but are taken as input of the so-called run tool when invoking 'make run/<run-script-name>' from within the build directory. Please refer to Section "2.4. A simple system scenario" and Section "5.4.1. Run tool" of the documentation [1] to learn more about the underlying concept.
[1] http://genode.org/documentation/genode-foundations-15-05.pdf
Regards Norman
-- Dr.-Ing. Norman Feske 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
Hi,
On 09/08/2015 10:16 AM, Thotheolh Tay wrote:
Hi,
I entered the build directory and ran "make run/virtualbox" and the resulting message is:
Error: No run script for virtualbox make: *** [run/virtualbox] Error 255
You have to ensure that all necessary repositories are enabled in the 'etc/build.conf' file within your build directory, e.g. repos/ports and repos/libports, repos/dde_linux. To enable them, remove the '#' at the beginning of the corresponding line.
Regards Stefan
On 7 Sep 2015 9:06 pm, "Norman Feske" <norman.feske@...1...> wrote:
Hello,
On 07.09.2015 08:05, Thotheolh Tay wrote:
I decided to take a look around after managing to run the demo nitpicker via "make run/demo" and so now I did a cd into the "GENODE_DIR\repos\ports\run" folder and found some ".run" scripts inside. I changed them to 777 permission as I noticed the permissions do not allow execute somehow and did a "./virtualbox.run" to test out the script. It threw me a
line 7: core: command not found line 8: drivers/framebuffer: No such file or directory line 9: drivers/timer: No such fole or directory line 10: syntax error near unexpected token '}' line 10: '}'
Am I running it to correct manner ?
run scripts cannot be executed directly but are taken as input of the so-called run tool when invoking 'make run/<run-script-name>' from within the build directory. Please refer to Section "2.4. A simple system scenario" and Section "5.4.1. Run tool" of the documentation [1] to learn more about the underlying concept.
[1] http://genode.org/documentation/genode-foundations-15-05.pdf
Regards Norman
-- Dr.-Ing. Norman Feske 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
Hi, I uncommented the ($BUILDERDIR)\etc\build.conf as shown below:
GENODE_DIR = /home/wss/Desktop/genode
BASE_DIR = $(GENODE_DIR)/repos/base
CONTRIB_DIR = $(GENODE_DIR)/contrib
#
# Prevent Qemu from using KVM
#
# Qemu version that come with major Linux distributions (i.e., Ubuntu)
enable
# KVM by default. To use Qemu without KVM, Qemu must be started with the
# '-no-kvm' argument. However, if your Qemu version does not support this
# argument, comment-out this line.
#
QEMU_OPT += -no-kvm
##
## Kernel-specific base repository
##
REPOSITORIES = $(GENODE_DIR)/repos/base-nova
##
## Kernel-specific run tool configuration
##
RUN_OPT = --include boot_dir/nova \
--include power_on/qemu --include log/qemu --include image/iso
#
# The current NOVA kernel build is optimized for Intel Core2 Duo.
#
QEMU_OPT += -cpu core2duo
##
## Repositories needed for the default demo scenario
##
REPOSITORIES += $(GENODE_DIR)/repos/base
REPOSITORIES += $(GENODE_DIR)/repos/os
REPOSITORIES += $(GENODE_DIR)/repos/demo
##
## Optional repositories
##
#
# Ports of popular open-source libraries and the C library.
#
# Make sure to execute 'make prepare' in 'libports' prior building.
#
REPOSITORIES += $(GENODE_DIR)/repos/libports
#
# Ports of popular 3rd-party applications
#
# The 'ports' repository depends on 'libc' and 'libports'.
# Make sure to execute 'make prepare' in 'ports' prior building.
#
REPOSITORIES += $(GENODE_DIR)/repos/ports
#
# Ports of the Linux TCP/IP stack and Linux drivers (USB) from the Linux
kernel
#
REPOSITORIES += $(GENODE_DIR)/repos/dde_linux
#
# NetBSD file-system support
#
REPOSITORIES += $(GENODE_DIR)/repos/dde_rump
#
# High-level Genode-specific services and applications
#
# The 'gems' repository depends on 'libc' and 'libports'.
#
REPOSITORIES += $(GENODE_DIR)/repos/gems
#
# Drivers ported from the OpenBSD
#
REPOSITORIES += $(GENODE_DIR)/repos/dde_bsd
#
# Drivers ported from iPXE
#
REPOSITORIES += $(GENODE_DIR)/repos/dde_ipxe
QEMU_OPT += -display sdl
And I got the following error:
wss@...351... ~/Desktop/genode/builds/nova/01092015v1 $ make
run/virtualboxincluding /home/wss/Desktop/genode/tool/run/boot_dir/nova including /home/wss/Desktop/genode/tool/run/power_on/qemu including /home/wss/Desktop/genode/tool/run/log/qemu including /home/wss/Desktop/genode/tool/run/image/iso including /home/wss/Desktop/genode/repos/ports/run/virtualbox.run building targets: core init virtualbox drivers/framebuffer drivers/timer drivers/input drivers/rtc drivers/platform drivers/acpi server/report_rom drivers/platform/x86/device_pd spawn make core init virtualbox drivers/framebuffer drivers/timer drivers/input drivers/rtc drivers/platform drivers/acpi server/report_rom drivers/platform/x86/device_pd make[1]: Entering directory `/home/wss/Desktop/genode/builds/nova/01092015v1' checking library dependencies... Skip target drivers/framebuffer/exynos5 because it requires exynos5 Skip target drivers/framebuffer/imx53 because it requires imx53 Skip target drivers/framebuffer/omap4 because it requires omap4 Skip target drivers/framebuffer/pl11x/pbxa9 because it requires pl11x platform_pbxa9 Skip target drivers/framebuffer/pl11x/vpb926 because it requires pl11x platform_vpb926 Skip target drivers/framebuffer/rpi because it requires platform_rpi Skip target drivers/framebuffer/sdl because it requires linux sdl Skip target drivers/input/imx53 because it requires imx53 Skip target drivers/input/ps2/pl050 because it requires pl050 Skip target drivers/platform/arndale because it requires platform_arndale Skip target drivers/platform/imx53 because it requires imx53 Skip target drivers/platform/odroid_x2 because it requires platform_odroid_x2 Skip target drivers/platform/rpi because it requires platform_rpi Skip target virtualbox because it requires installation_of_yasm installation_of_iasl Library platform Library cxx Library syscall Library startup Library base-common Library base Program drivers/acpi/x86/acpi_drv Library blit Library x86emu Library config Program drivers/framebuffer/vesa/fb_drv Library server Program drivers/input/dummy/dummy_input_drv Program drivers/input/ps2/x86/ps2_drv Program drivers/platform/x86/device_pd/device_pd Program drivers/platform/x86/platform_drv Program drivers/rtc/x86/rtc_drv Library alarm Library timer Program drivers/timer/timer Library init_pd_args Program init/init Program server/report_rom/report_rom Library core Program core/core COMPILE version.o LINK core make[1]: Leaving directory `/home/wss/Desktop/genode/builds/nova/01092015v1' genode build completed cp: cannot stat ‘bin/virtualbox’: No such file or directory while executing "exec cp bin/$binary [run_dir]/genode" (procedure "copy_and_strip_genode_binaries_to_run_dir" line 4) invoked from within "copy_and_strip_genode_binaries_to_run_dir $binaries" (procedure "run_boot_dir" line 6) invoked from within "run_boot_dir $binaries" (procedure "build_boot_image" line 2) invoked from within "build_boot_image $boot_modules" (file "/home/wss/Desktop/genode/repos/ports/run/virtualbox.run" line 152) 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/wss/Desktop/genode/tool/run/run" line 636) make: *** [run/virtualbox] Error 1
I have uncommented every options that was commented. I also went back to '/home/wss/Desktop/genode/repos/libports' and '/home/wss/Desktop/genode/repos/ports' to execute 'make prepare' and all seems to have gone well.
What else am I still lacking ?
Regards.
On Tue, Sep 8, 2015 at 5:10 PM, Stefan Kalkowski < stefan.kalkowski@...1...> wrote:
Hi,
On 09/08/2015 10:16 AM, Thotheolh Tay wrote:
Hi,
I entered the build directory and ran "make run/virtualbox" and the resulting message is:
Error: No run script for virtualbox make: *** [run/virtualbox] Error 255
You have to ensure that all necessary repositories are enabled in the 'etc/build.conf' file within your build directory, e.g. repos/ports and repos/libports, repos/dde_linux. To enable them, remove the '#' at the beginning of the corresponding line.
Regards Stefan
On 7 Sep 2015 9:06 pm, "Norman Feske" <norman.feske@...1...>
wrote:
Hello,
On 07.09.2015 08:05, Thotheolh Tay wrote:
I decided to take a look around after managing to run the demo
nitpicker
via "make run/demo" and so now I did a cd into the "GENODE_DIR\repos\ports\run" folder and found some ".run" scripts inside. I changed them to 777 permission as I noticed the permissions
do
not allow execute somehow and did a "./virtualbox.run" to test out the script. It threw me a
line 7: core: command not found line 8: drivers/framebuffer: No such file or directory line 9: drivers/timer: No such fole or directory line 10: syntax error near unexpected token '}' line 10: '}'
Am I running it to correct manner ?
run scripts cannot be executed directly but are taken as input of the so-called run tool when invoking 'make run/<run-script-name>' from within the build directory. Please refer to Section "2.4. A simple system scenario" and Section "5.4.1. Run tool" of the documentation [1] to learn more about the underlying concept.
[1] http://genode.org/documentation/genode-foundations-15-05.pdf
Regards Norman
-- Dr.-Ing. Norman Feske 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
-- Stefan Kalkowski Genode Labs
http://www.genode-labs.com/ · http://genode.org/
genode-main mailing list genode-main@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/genode-main
Hi,
the build hints what you might be missing. Please see below.
On Fri, Sep 11, 2015 at 02:36:31PM +0800, Thotheolh Tay wrote:
wss@...351... ~/Desktop/genode/builds/nova/01092015v1 $ make run/virtualbox
including /home/wss/Desktop/genode/tool/run/boot_dir/nova including /home/wss/Desktop/genode/tool/run/power_on/qemu including /home/wss/Desktop/genode/tool/run/log/qemu including /home/wss/Desktop/genode/tool/run/image/iso including /home/wss/Desktop/genode/repos/ports/run/virtualbox.run building targets: core init virtualbox drivers/framebuffer drivers/timer drivers/input drivers/rtc drivers/platform drivers/acpi server/report_rom drivers/platform/x86/device_pd spawn make core init virtualbox drivers/framebuffer drivers/timer drivers/input drivers/rtc drivers/platform drivers/acpi server/report_rom drivers/platform/x86/device_pd make[1]: Entering directory `/home/wss/Desktop/genode/builds/nova/01092015v1' checking library dependencies... Skip target drivers/framebuffer/exynos5 because it requires exynos5 Skip target drivers/framebuffer/imx53 because it requires imx53 Skip target drivers/framebuffer/omap4 because it requires omap4 Skip target drivers/framebuffer/pl11x/pbxa9 because it requires pl11x platform_pbxa9 Skip target drivers/framebuffer/pl11x/vpb926 because it requires pl11x platform_vpb926 Skip target drivers/framebuffer/rpi because it requires platform_rpi Skip target drivers/framebuffer/sdl because it requires linux sdl Skip target drivers/input/imx53 because it requires imx53 Skip target drivers/input/ps2/pl050 because it requires pl050 Skip target drivers/platform/arndale because it requires platform_arndale Skip target drivers/platform/imx53 because it requires imx53 Skip target drivers/platform/odroid_x2 because it requires platform_odroid_x2 Skip target drivers/platform/rpi because it requires platform_rpi Skip target virtualbox because it requires installation_of_yasm installation_of_iasl
The build is skipping virtualbox because required tools (yasm and iasl) are missing. I admit this is not easy to spot but at least highlighted in yellow. Please install both tools, e.g. on Debian/Ubuntu via
aptitude install iasl yasm
cp: cannot stat ‘bin/virtualbox’: No such file or directory while executing
Here you can see that the integration fails because virtualbox was skipped above.
Greets
Hello Thotheolh,
On 11.09.2015 08:36, Thotheolh Tay wrote:
... make run/virtualbox ... What else am I still lacking ?
assuming that you are in the early process of exploring Genode but haven't build up the experience with integrating modest scenarios, I think that the virtualbox scenario will become a source of frustration for you. In any case, let me share just a few precautions about the virtualbox scenario:
* The virtualbox run script won't work with Qemu. According to your previous postings, your host system is running as a guest OS on top of some other OS. This already caused trouble with running Qemu within this environment. Running another nested virtual machine monitor within Qemu is not expected to work. I.e., Qemu's virtualization support is lacking.
Consequently, the virtualbox scenario should be executed on real hardware only. When testing on real hardware, however, you will need a way to obtain the serial output for troubleshooting. The mailing list archive contains several recent discussions of this topic, but it is still a hurdle to take.
* We regularly run VirtualBox solely on the nova_x86_64 kernel. On all other base platforms - even nova_x86_32 - problems are must be expected.
* The virtualbox.run script expects a 'test.iso' image in the bin directory. But not all guest OSes will work out of the box. When picking an ISO image, you need to consider that the image will be loaded by the boot loader into memory. So loading a big ISO of a fully-fledged Linux OS will not only take ages to load but also consumes a lot of memory. It might be the best to use the ISO image of a small Genode scenario (like the one produced by demo.run) to start with.
That said, for exploring Genode, I'd recommend you to review the less sophisticated scenarios at 'repos/os/run' and 'repos/libports/run' before turning to the complex ones located at 'repos/ports/run'.
Regards Norman
-
Christian Helmuth -
Norman Feske -
Stefan Kalkowski -
Thotheolh Tay