lxip vfs and RM-session

[Emery Hemingway]

Hello Stefan,

Did you add a route in your deploy config?

<start name="..." pkg="...">
  <route>
    <service name="RM"> <parent/> </service>
    ...
  </route>
</start>

The RM session is not needed by most components, so it is not included
in the default deploy routes.

Cheers,
Emery

On Thursday, July 19, 2018 2:15:52 PM CEST, Stefan Thöni wrote:
> Hello Genodians,
>
> I'm currently trying to use a lxip stack in a vfs component (name tcpip)
> in a package in the sculpt runtime. This fails with the following error:
>
> [runtime] Warning: upd: no route to service "RM"
> [runtime -> upd -> tcpip] Error: RM-session creation failed
> (ram_quota=65536, cap_quota=2)
> [runtime -> upd -> tcpip] Error: __cxa_guard_abort called
> [runtime -> upd -> tcpip] Error: failed to create <lxip> VFS node
> [runtime -> upd -> tcpip] Error:      dhcp="yes"
>
> The RM-session seems properly configured in both runtime and deploy.
>
> The "tcpip" vfs component then continues to run and accepts file system
> session, but obviously the socket part doesn't work.
>
> [runtime -> upd -> tcpip] session opened for 'subinit -> tcpip' at '/'
> [runtime -> upd -> subinit -> fetchurl] fetch https://...
> [runtime -> upd -> subinit -> fetchurl] Error: failed to open new socket
> at /tcpip/socket/udp/new_socket
> [runtime -> upd -> subinit -> fetchurl] Error: Couldn't resolve host
> name, failed to fetch https://...
>
> Any ideas what the problem with said RM-session could be?
>
> Bests
> Stefan
>