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 Sun, 04 Jan 1970 05:24:11 GMT
What is in dns and dhcp should be what the host gets for an address.
Check the log to make sure the cm is assigning a dhcp and dns address
to the newly created vm.  Also, is this host special in any way?
Newer or older hardware?  Could be that the vm comes up before the
dns/dhcp assignment happens.  I can't remember the steps that happen
when allocating a vm off the top of my head.  You are reproducing this
error consistently?  You mentioned that there was high load before,
are you getting this error with no system load?

Sent from my mobile device


On Aug 2, 2011, at 20:20, David O'Hallaron <> wrote:

> Hi guys,
> I was able to characterize my problem better, but I'm still not sure
> why it is happening:
> For any instance created on one particular host (called roughshark),
> the instance boots up OK and gets a valid IP address. But for some
> reason, the DNS thinks it has a different IP address: For example:
> Instance test-00.vmnet has a true IP address of
> (confirmed by ifconfig in the console), but DNS thinks it's IP address
> is (via nslookup test-00.vmnet).
> It only happens on roughshark, it happens to every instance created on
> roughshark, and it never happens on other hosts.
> Does this sound like a host configuration issue to you?
> Thanks!
> Dave
> -- David O'Hallaron
> -- Prof of CS and ECE, Carnegie Mellon University
> -- contact:
> On Mon, Aug 1, 2011 at 7:55 PM, Michael Stroucken <> wrote:
>> David O'Hallaron wrote:
>>> Thanks guys. I'll take a look at the console .
>>> -- David O'Hallaron
>>> -- Prof of CS and ECE, Carnegie Mellon University
>>> -- contact:
>> I think both Richard and I mean attaching to the VMs console using VNC.
>> Greetings,
>> Michael.

View raw message