main-noip apps never terminate

[mor1]

even if main-noip: ... is specified, mirari generates the backend.ml to create a thread that accepts on a socket, and adds the Backend.run() thread to the join list in main.ml.

this means a unikernel that never invokes networking will never terminate -- the Backend.run() thread remains live in the accept loop forever.

[vbmithr]

As mirage unikernels were supposed to support interface hotplug (eventually), I was fine having an unikernel never terminates. How do you think that should be handled ?

[samoht]

Maybe the hotplug ability can also be enabled with a flag ?

[avsm]

I think unikernels should be explicitly modelled as something that is started and stopped. The UNIX version could/should have a CLI to "list running unikernels with IDs" just like Xen kernels do.

This makes management of them much much easier, since I can just start 8 UNIX unikernels on a Linux box and have them use 8 cores in parallel, just as we would under Xen.

I.e. why not go for an explicit hotplug + start/stop model right now, since it's the only eventual model that makes sense. Very Erlang-like...

On 13 Aug 2013, at 11:21, Vincent Bernardoff [email protected] wrote:

As mirage unikernels were supposed to support interface hotplug (eventually), I was fine having an unikernel never terminates. How do you think that should be handled ?

—
Reply to this email directly or view it on GitHub.

[mor1]

that makes sense to me -- making mirari a thing that basically abstracts over xl for both Xen and POSIX unikernels seems like a useful thing. if it can also send hotplug events to model environmental changes, so much the better.