incubator-tashi-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Richard Gass <>
Subject Re: Destination host unreachable
Date Mon, 01 Aug 2011 19:20:22 GMT
I would look at the console of the running vm to see what is going on
as Michael said.  Also, it could be something with the specific
physical host that the vm is scheduled on.  Does the problem usually
happen on the same host?

I suspect that the vm is up and running and is wedged somewhere in the
boot process, probably somewhere in the init.  Looking at the console
will probably pinpoint the problem.


On Mon, Aug 1, 2011 at 8:00 PM, Michael Stroucken <> wrote:
> David O'Hallaron wrote:
>>> If the VM is actually up, is the DHCP server capable of handing out an
>>> address in time for the machine to accept it?
>> Tashi seems to think the instance is up but it never seems to have
>> gotten an IP address. After this kind of thing happens, I can
>> subsequently create a new VM that gets a good IP address, so the DHCP
>> server is definitely working.
> But is the actual VM running correctly? :)
> Have you looked at what is on console?
>> Are you suggesting that the DHCP server might get overloaded, not
>> respond, and that Tashi doesn't retry the request?
> That is a failure possibility. DHCP and TFTP sometimes get overloaded. Are
> you running CM, NM and DHCP on the same machine? I can come over and take a
> look at what's going on.
> Greetings,
> Michael.

Richard Gass

View raw message