Hi,
I don't know if I am bothering you too much! Yes, as you correctly pointed out, I am unable to connect to the VNC server. I am working with Docker containers.
Here's the message I get while I try to run make -C build/x86_32 KERNEL=okl4 run/demo.
spawn qemu-system-i386 -no-kvm 127.0.0.1:0 -serial mon:stdio -m 512 -cdrom var/run/demo.iso
qemu-system-i386: -no-kvm: Unknown protocol '127.0.0.1'
Aborting, received EOF
Log step failed, retry.
spawn qemu-system-i386 -no-kvm 127.0.0.1:0 -serial mon:stdio -m 512 -cdrom var/run/demo.iso -cdrom var/run/demo.iso
qemu-system-i386: -no-kvm: Unknown protocol '127.0.0.1'
Aborting, received EOF
Log step failed, retry.making some silly mistakes
spawn qemu-system-i386 -no-kvm 127.0.0.1:0 -serial mon:stdio -m 512 -cdrom var/run/demo.iso -cdrom var/run/demo.iso -cdrom var/run/demo.iso
qemu-system-i386: -no-kvm: Unknown protocol '127.0.0.1'
Aborting, received EOF
Log step failed, retry.
Boot process failed 3 times in series. I give up!
My container IP details are as follows:
root@...556...:/Genode/genode# ifconfig
eth0 Link encap:Ethernet HWaddr 02:42:ac:11:00:02
inet addr:172.17.0.2 Bcast:0.0.0.0 Mask:255.255.0.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:30181 errors:0 dropped:0 overruns:0 frame:0
TX packets:21859 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:255807677 (255.8 MB) TX bytes:1765833 (1.7 MB)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
I am sure that I am making some silly mistakes. Thank you for your support, though!
Yours sincerely,
Subhadeep
-------------------------------------------------------------------------------------------
Subhadeep Sarkar, PhD
Postdoctoral researcher, Univ Rennes, Inria, CNRS, IRISA
Inria Rennes - Bretagne Atlantique
Campus universitaire de Beaulieu
35042 Rennes cedex, France
Website: subhadeep.cf
E-mail: subhadeep.sarkar@...552... ; subhadeepsarkarybs@...557.....
Phone: +33 2 99 84 73 52
From: "Valery V. Sedletski" <_valerius@...73...>
To: "Subhadeep Sarkar" <subhadeep.sarkar@...552...>, "Genode OS Framework Mailing List" <genode-main@lists.sourceforge.net>
Sent: Tuesday, January 23, 2018 4:05:44 PM
Subject: Re: Installing Genode within container
On 23.01.2018 13:13, Subhadeep Sarkar
wrote:
Hi,
Thank you for your quick response!
However, even after trying on it for the last couple of
last I could not make it work (clearly shows that I am a
newbie in Genode). The good part is I am able to by pass the
problem by installing Genode in a (ubuntu) virtual machine
instead of a container. I successfully launched the demo for
okl4 from there. Launching sel4, however, does not appear to
be as straightforward. ;)
So, what is your problem? Can't connect to the VNC server? What kind
of container did you tried? Does it have a separate IP address
assigned? The IP should be from that container. The display number
is usually 0. So, you should specify
QEMU_OPT += 127.0.0.1:0
if your IP is the same as a host machine (you can try a simple
chroot instead of a container, for simplicity. Then it's IP would be
127.0.0.1. Also, in this case you will be able to access a local
display, and VNC will be unneeded)
So, the problem may be with accessibility of your VNC display from
outside the container. But you could try chroot for simplicity, as I
suggested. VM is a worst option, because you'll need to run QEMU
inside this VM for testing the binaries, which will be slow.
Anyway, thank you very much for your assistance.
Yours sincerely,
Subhadeep
-------------------------------------------------------------------------------------------
Subhadeep Sarkar, PhD
Postdoctoral researcher, Univ Rennes, Inria, CNRS, IRISA
Inria Rennes - Bretagne Atlantique
Campus universitaire de Beaulieu
35042 Rennes cedex, France
Website: subhadeep.cf
E-mail:
subhadeep.sarkar@...552... ;
subhadeepsarkarybs@...54...
Phone: +33 2 99 84 73 52
From: "Valery
V. Sedletski via genode-main"
<genode-main@lists.sourceforge.net>
To: genode-main@...341...eforge.net
Cc: "Valery V. Sedletski" <_valerius@...558......>
Sent: Friday, January 19, 2018 6:15:15 PM
Subject: Re: Installing Genode within container
On 19.01.2018 19:21, Subhadeep
Sarkar wrote:
Hi,
I am a researcher at Inria France and am presently
exploring Genode as a potential option to perform hands
on with Sel4. I am relatively new to Genode and having
an issue while installing it.
Here is the issue:
I am trying to install Genode on Ubuntu (16.04 LTS)
running within
a container. I am able to successfully see
through all the installation steps.
However, when I issue the final command: make -C
build/x86_32 KERNEL=okl4 run/demo, I get this
following error.
make[1]: Leaving
directory '/Genode/genode/build/x86_32'
genode build
completed
using
'core-okl4.o' as 'core.o'
using
'ld-okl4.lib.so' as 'ld.lib.so'
using
'pit_timer_drv' as 'timer'
install
bootloader
creating ISO
image...
xorriso 1.4.2 :
RockRidge filesystem manipulator, libburnia project.
spawn qemu-system-i386
-no-kvm -display sdl -serial mon:stdio -m 512 -cdrom
var/run/demo.iso
Could not initialize
SDL(No available video device) - exiting
Aborting, received EOF
Log step failed,
retry.
spawn
qemu-system-i386 -no-kvm -display sdl -serial
mon:stdio -m 512 -cdrom var/run/demo.iso -cdrom
var/run/demo.iso
qemu-system-i386:
-cdrom var/run/demo.iso: drive with bus=1, unit=0
(index=2) exists
Aborting,
received EOF
Log step failed,
retry.
spawn
qemu-system-i386 -no-kvm -display sdl -serial
mon:stdio -m 512 -cdrom var/run/demo.iso -cdrom
var/run/demo.iso -cdrom var/run/demo.iso
qemu-system-i386:
-cdrom var/run/demo.iso: drive with bus=1, unit=0
(index=2) exists
Aborting,
received EOF
Log step failed,
retry.
I did install libsdl1.2-dbg.
Clearly, I
do not have a display connected, as I am trying to run
it from within a container. Could you please help me
with this issue?
Thank you in advance!
Yours sincerely,
Subhadeep
I'd suggest you to comment
QEMU_OPT += -display sdl
out from the etc/build.conf, and add an option like
QEMU_OPT += -display vnc=<IP address>:<display>
This would activate QEMU built-in VNC server. You would be
able to access the Genode display via a VNC client, connecting
to a <IP address>:<display> VNC display.
I'm connecting to my development Linux system from my main OS,
via SSH. When I need to run binaries, to test them, I start
the corresponding run script. I see the logs in my SSH window.
When I need to see the Genode screen, I just start the VNC
viewer. The only disadvantage is that the mouse cursor in a
VNC client is displaced, relative to Genode mouse cursor. I
still did not worked this problem around. Also, there exists
an option to run QEMU screen, or a SDL window in Genode/Linux,
remotely via X11 remote connection (you need your DISPLAY env.
variable to point to your local X11 display). But I did not
managed to make it working successfully, because when I run it
from an SSH session, it tries to use the "fbcon" SDL backend.
Trying to set SDL_VIDEODRIVER env. variable to "x11" doesn't
help here.
-------------------------------------------------------------------------------------------
Subhadeep Sarkar, PhD
Postdoctoral researcher, Univ Rennes, Inria, CNRS, IRISA
Inria Rennes - Bretagne Atlantique
Campus universitaire de Beaulieu
35042 Rennes cedex, France
Website: subhadeep.cf
E-mail:
subhadeep.sarkar@...552... ;
subhadeepsarkarybs@...54...
Phone: +33 2 99 84 73 52
------------------------------------------------------------------------------
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
------------------------------------------------------------------------------
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