Network problem with CentOS 5 guest under VMware ESXi

Thanks Marco, but I'm ignorant of Linux, so could you spell out how check if these are installed?
I've got xwindows up and under Applications --> System Tools --> Virtual Machine Manager there is an entry: Name=localhost, ID=xen. I deleted it, but it re-appears after restarting network service.

Hi,

ok to completely remove all the bultin virtualization just type:

yum groupremove Virtualization

at a command prompt

also a

rpm -e -nodeps libvirt

might work, but the former is preferable as it'll correctly remove everything related!

Cheers,
]\/[arco

Hi Marco, see error messages below:

[root@vm-lnx-01 ~]# yum groupremove "Virtualization"
Setting up Group Process
Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=5&arch=x86_64&repo=os error was
[Errno 4] IOError: <urlopen error (-3, 'Temporary failure in name resolution')>
Error: Cannot retrieve repository metadata (repomd.xml) for repository: base. Please verify its path and try again
[root@vm-lnx-01 ~]#

[root@vm-lnx-01 ~]#
[root@vm-lnx-01 ~]# rpm -e -nodeps libvirt
-nodeps: unknown option
[root@vm-lnx-01 ~]#
[root@vm-lnx-01 ~]# rpm -e libvirt
error: "libvirt" specifies multiple packages
[root@vm-lnx-01 ~]#

Any thoughts?
Thanks!

Of coruse yum won't work without an internet connection sorry, and looks like it's configured to not look at the local cache. Before trying something else, would you please post the contents of your routing table? Just type:

route -n

at the command prompt and post the results!

Cheers,
]\/[arco

Routing table below:

[root@vm-lnx-01 ~]# route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
192.168.1.0     0.0.0.0         255.255.255.0   U     0      0        0 eth0
192.168.122.0   0.0.0.0         255.255.255.0   U     0      0        0 virbr0
169.254.0.0     0.0.0.0         255.255.0.0     U     0      0        0 eth0
0.0.0.0         192.168.1.254   0.0.0.0         UG    0      0        0 eth0
[root@vm-lnx-01 ~]#

Cheers.

Ok your default gateway is setup as 192.168.1.254, is that correct? That's tied to interface eth0, that's the right one. In VMWare make sure that you're assigned the right vSwitch to this virtual machine. Doublecheck by pinging the 192.168.1.254 IP (just ping 192.168.1.254 at a command prompt) , that should answer back fine. Then try pinging an external ip like ping 208.67.222.222. If that's answering fine, your problem may simply be the DNS. Write the following in a command prompt:

echo nameserver 208.67.222.222 > /etc/resolv.conf
echo nameserver 208.67.220.220 >> /etc/resolv.conf

Those commands will add the OpenDNS servers to your /etc/resolv.conf file.
Now try to ping www.google.com, and that should succeed.
If all this does not help the problem probably lies outside of this virtual machine. Could be wrong vSwitch assigned, the router configuration of a firewall in between that's not working correctly, and will need more infos about the rest of your infrastructure!

Cheers,
]\/[arco

Yes, I believe the gateway is correct - 192.168.1.254 is the firewall.
VMware only has 1 vSwitch setup and all VMs are on the same Virtual Machine Port Group.
Pinging 192.168.1.254 returns Destination Host Unreachable, likewise with 208.67.222.222.
I should also mention this VM worked fine under VMware Server, but the problem occured when I converted it to ESXi.

Thanks!

Oh well that could be the problem then! How did you convert the vm from VMWare server to ESXi? with vmkfstools of with vm converter? Could you also post the contents of /etc/sysconfig/network-scripts/ifcfg-eth0? You may have to upgrade the vmware tools before the network would work after a conversion, but since you actually have an IP assigned to that nic, I want to check if the IP as been setup manually of via dhcp!

Cheers,
]\/[arco

I used vCenter Converter Standalone Client 4.0.1.  Also, I did update VMware Tools.

ifcfg-eth0 contents:
# Intel Corporation 82545EM Gigabit Ethernet Controller (Copper)
DEVICE=eth0
ONBOOT=yes
BOOTPROTO=dhcp
HWADDR=00:0c:29:52:92:c2

The hardware address matches the MAC Address in VMware.
Thanks again!

Hi,

that's very strange indeed. Your virtual nic is correctly taking an IP from your router, so you definitely have network connectivity. It may be that some firewall rules on the routes is preventing this particular IP address to going out to the network? It's even possible that you have some rules in your iptables preventing you frmo going out, but I find it difficult to happen. However you can try to type:

iptables-save

to show the rules setup on your firewall and post them here. If there are active rules, you may try to disable your firewall, just to check if that gets your connectivity back:

service iptables stop

Cheers,
]\/[arco