[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [MirageOS-devel] Routing.No_route_to_destination_address running Mirage web server

Thanks. It does seem to be a configuration issue of some kind. At
least the capture looks consistent with the console messages from the

I understand that the ping was done from your Mac to the unikernel?
What I meant to ask is to see a working capture (e.g. ping Mac ->
dom0, or capture Mac -> Ubuntu domU HTTP) in addition to the
non-working one (Mac to unikernel).

If you set your unikernel MAC address to the same as your working
Ubuntu domU (while the Ubuntu domU is stopped of course), does it make
any difference to the problem? Even if it doesn't help, it would be a
more direct comparison between the good and bad captures. Perhaps
attach the pcap files if it is not too much trouble?


On 30 May 2015 at 06:42, Andrew Stuart <andrew.stuart@xxxxxxxxxxxxxxxxxx> wrote:
>>> what's
> My Mirageos unikernel
>>>It doesn't seem to be an interface on the Xen box but that capture was taken 
>>>on xenbr0 on the Xen box, right?
> Yes it is on the xen box
>>>Sorry if this is a *really* stupid question but-- are you sure that your Mac 
>>>has physical reachability to the laptop running Xen?
> Yes, if I run Ubuntu/Nginx as Domu then talks with no problem 
> at all.

MirageOS-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.