Re: [MirageOS-devel] Mirage unikernels and network setup

[Armael <armael@xxxxxxxxxxxxx>]

> it might be useful to include the .xl file you’re using to start it? 

Good point. Here's the network.xl file I'm using:

---------
name = 'network2'
kernel = '/root/vms/network.xen'
builder = 'linux'
memory = 50
on_crash = 'preserve'

disk = [  ]

vif = [ 'bridge=br0' ]
----------

> Also have you tried from a Linux domU rather than dom0? (ISTR sometimes 
> routing being a bit weird from dom0. But as I said, it’s been a while…) Or 
> even just waiting a while (several minutes) for ARP to sort itself out?

I tried, and being from a Linux domU rather than a Linux dom0 does not
seem to make a difference. However, by waiting a bit more, I could
observe a bit more:

- When I first create the unikernel, a `nc 10.0.42.20 2345` will hang
for 67 seconds, and afterwards terminate with

"(UNKNOWN) [10.0.42.20] 2345 (?) : No route to host"

If I re-start the netcat command, then it terminates in a few seconds
with the same message.


If that's useful, here's the result of "ip r" on the Linux domU:

default via 10.0.42.1 dev eth0 onlink
10.0.42.0/24 dev eth0 proto kernel scope link src 10.0.42.200

and the dom0:

default via 51.15.171.1 dev enp1s0 onlink
10.0.42.0/24 dev br0 proto kernel scope link src 10.0.42.1
51.15.171.0/24 dev enp1s0 proto kernel scope link src 51.15.171.237

_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/mirageos-devel