So I thought it was time to add something useful again to my blog.
Working with something for work, I had to configure a FC4 box with multiple IPs on different subnets, binding them to a sub nterface (eth0:1, eth0:2 and so on)
When we first got everythng on, only the primary IP address were working (bound to eth0 and eth1). All other interfaces were resolving to the physical ESXi servers MAC address on the switch, which is no good. After looking around, I found out there wasn’t support for this, everyone was saying to configure a Brige, or NAT everything through the local machine, which would NOT work out in our situation.
So after thinking a bit, I remembered the other issue we had with older OpenBSD 3.8 machines and the native VIC driver which was making the machines randomly crash reporting an unsupported mode. Well the resolution for that was to shut down the guest, and add in ethernet0.VirtualDev = “e1000″ and ethernet1.VirtualDev = “e1000″ to the guest-name.vmx file. So I figured I would try this on the Fc4 machine too, figuring I couldn’t lose anything. Well, I didn’t lose anything, but I gained a working ssystem, with sub-interfaces!
So for all of those out there with weird networing issues on an ESXi (ESX as well) guests, try changing the network emulation from built-in VIC to intel e1000!
