Hi Armaël,
I had a similar problem in the past and I solved by manually
assigning in the .xl file a MAC address to the unikernel. As MAC
addresses are pretty much randomized if you don't manually assign
it, this might lead to problems in the ARP cache (different MAC
same IP) as you start/stop the unikernel consecutively and, as
Richard suggested, you might have to wait for ARP to sort it
before the unikernel is properly reachable.
TL;DR: Try to assign a fixed MAC address to the unikernel in .xl
file and see how it goes.
Best,
Vittorio
Il 02/01/2019 15:51, Armael ha scritto:
Hi everyone,
I'm trying to run the "network" unikernel (from mirage-skeleton [1]) on
my server, which uses Xen. I'm able to run linux VMs on this server, and
the network setup seems to be working for them (my main VM is running,
and I also created a fresh debian VM just to test that).
However it doesn't seem to be working for mirage unikernels...
The unikernel starts, but just trying to ping it or connect to it (from
the dom0) fails.
I've attached the console log from the unikernel, the tcpdump log, and
the log from the host.
Interestingly, if I try to ping the unikernel, it seems to receive the
ping packet, but doesn't reply.
Would anyone have a clue?
Cheers, and happy new year,
Armaël
[1]
https://github.com/mirage/mirage-skeleton/blob/master/device-usage/network/unikernel.ml
_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/mirageos-devel
--
Vittorio Cozzolino, M.Eng.
Technische Universität München - Institut für Informatik
Office 01.05.041
Boltzmannstr. 3, 85748 Garching, Germany
Tel: +49 89 289-17356
http://www.cm.in.tum.de/en/research-group/vittorio-cozzolino
