Kushal,
Since you disabled the DHCP section of the configuration file,
the only functionality you're losing is giving it a pre-assigned IP
address. DHCP should still be giving it just a dynamic address.
If when you log in, and run `dhclient eth0`, but you are on the
same network as the eth1 device on the physical host, then you need to
talk to your DHCP server administrator (either me or david winters) about
what is wrong there.
~Hunter
On Tue, 25 Oct 2011, Richard Gass wrote:
Sounds like dhcp is not associating the Mac to the ip tashi is giving
the host. Check your dhcpd leases to see if an entry exists. Also
check the configuration to make sure you specified the keys, server
name etc correctly.
Thanks
--
Richard
Sent from my mobile device
On Oct 25, 2011, at 6:24, Kushal Dalmia <[email protected]> wrote:
Hi Micheal,
After looking around a little bit and playing around with the config we
realized that the only issue we have is that the VM is not getting an IP
address on initialization. If we vnc into the VM and assign it an IP
address statically, it becomes pingable/sshable. When the VM gets created,
the nodemanager logs the static IP it "supposedly" assigns the VM. But
that IP is somehow not configured in the VM itself.
(P.S. - We have disabled the DNS and DHCP options in the config since we
need just static allocation of IPs by the tashi scheduler itself)
Thanks,
Kushal
On Mon, October 24, 2011 8:51 am, Michael Stroucken wrote:
Richard Gass wrote:
Did you log into the vm over the vnc console and run dhclient to see
if you can manually setup networking? Also maybe just ifup the interface
with a static ip.
Also consider installing tcpdump in your images, so that you can see if
any network traffic is coming from the outside.
Can you provide the output of brctl show, ifconfig -a and netstat -nr on
your host when a VM is running?
Greetings,
Michael.
