Hi All,
I hope someone can help me in debugging/pinpointing a problem I'm having etting ESX 4 working in VMWare Workstation 7.0 on Linux (on both Ubuntu 9.04 and 9.10, both exhibit same problem for me).
ESX 4.0 installs fine inside a VM, with the guest operating system set to "ESX Server 4.0", but after bootup, IP packets & DHCP do not work for the guest ESX 4 system. tcpdump inside the guest shows arp traffic and broadcast traffic for the entire LAN segment. ESXi 4 does work successfully, with DHCP/ICMP/vSwitch communications all working fine. I've tested this on
System config:
Host machine: Intel i7 920, 6GB memory, Ubuntu 9.04. IP: 192.168.1.54
Guest: ESX4.0 Build 164009. IP: 192.168.1.243
ESX 4 guest machine:
vswif0 Link encap:Ethernet HWaddr 00:50:56:4E:6B:D1
inet addr:192.168.1.243 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:12662 errors:0 dropped:0 overruns:0 frame:0
TX packets:56 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:791139 (772.5 KiB) TX bytes: 8052 (7.8KiB)
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on vswif0, link-type EN10MB (Ethernet), capture size 96 bytes
22:14:22.850036 00:18:51:aa:19:22 > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 60: arp who-has 192.168.1.160 tell 192.168.1.43
22:14:23.951134 00:1c:10:5f:25:87 > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 60: arp who-has 192.168.1.160 tell 192.168.1.4
Host machine (Ubuntu 9.04):
You can see the ARP reply on the host machine, and the ICMP echo request, but
no reply. tcpdump inside the ESX4 machine only shows the arp request/reply but
no unicast ICMP echo request.
root@i7:~# arp -a -n | grep 192.168.1.243
? (192.168.1.243) at 00:50:56:4e:6b:d1 on eth0
11:49:37.376389 00:24:8c:56:d9:a0 > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 42: arp who-has 192.168.1.243 tell 192.168.1.54
11:49:37.376604 00:50:56:4e:6b:d1 > 00:24:8c:56:d9:a0, ethertype ARP (0x0806), length 60: arp reply 192.168.1.243 is-at 00:50:56:4e:6b:d1
11:49:37.376617 00:24:8c:56:d9:a0 > 00:50:56:4e:6b:d1, ethertype IPv4 (0x0800), length 98: (tos 0x0, ttl 64, id 0, offset 0, flags |DF|, proto ICMP (1), length 84) 192.168.1.54 > 192.168.1.243: ICMP echo request, id 8551, seq 1, length 64
11:49:38.371782 00:24:8c:56:d9:a0 > 00:50:56:4e:6b:d1, ethertype IPv4 (0x0800), length 98: (tos 0x0, ttl 64, id 0, offset 0, flags |DF|, proto ICMP (1), length 84) 192.168.1.54 > 192.168.1.243: ICMP echo request, id 8551, seq 2, length 64
I have sat on this for a while hoping a kernel update or later ESX build might
fix my problem, but I've had no such luck. Last night I tested ESX4.0 on
Workstation 7 in Windows 7, and that worked successfully for guest<->lan
communications. Frustratingly, ESXi does work on this platform/configuration, but I want to evaluate some software that only works on ESX4.0.
I havn't been able to find anyone else with my symptoms, so
I'm hoping one of you clever experts can help me to debug this or provide a
suggestion on what could be wrong.
Thanks in advance,
Chris
Have you configured the virtual network devices on the Linux host to allow promiscuous mode? See KB 287.
Have you configured the virtual network devices on the Linux host to allow promiscuous mode? See KB 287.
sorry for the obvious...have you set it to bridged networking?
Thank you for both your replies. Annoyingly, it was permissions on /dev/vmnet* that prevented ESX 4 putting the interface into promiscuous mode, which of course would cause the exact symptoms I was seeing (only broadcast, no unicast packets).
damn66, I had tried all networking modes with no success.
I am none the wiser why ESXi 4 did work, including VM's running inside the ESXi VM, but I'm glad that I've got a solution (booting into Windows to do this? No thanks .. ).
Thanks again to jmattson for the sharp & accurate reply