On Wed, Aug 15, 2012 at 12:20 AM, William Scott Lockwood III
<
vladi...@gmail.com> wrote:
> The host has the e1000 and vmxnet3 drivers available, and
> dmesg shows that the driver loads, and eth0 is created.
I am presuming you mean the guest OS.
The word host is somewhat confusing within the context of virtualisation.
I prefer to make the references unambiguous; "host OS" (providing the
virt. platform) and "guest OS" (the VMs running on virt. platform)
> Once I am able
> to log into the system however, there is no eth0, and it cannot be
> brought up.
Dump the output of 'ifconfig -a' and see how many interfaces it reports.
> The right version of the vmware tools has been installed.
> The /etc/network/interfaces entry has been tested on another machine,
> and works there. I am baffled by this.
When you say tested on another machine, does it mean you have
transferred the guest OS image file?
I have no experience with VMWare. However, make sure that your
"host" OS i.e. VMWare is giving the same mac address as in the
machine where you tested it.
In the guest OS, you could also delete all the eth? lines in the file:
/etc/udev/rules.d/70-persistent-net.rules and reboot the system.
Upon reboot do ifconfig -a and see what is reported.
This may sound like stating the obvious but I have been bitten by it a
few times in my Linux KVM setups.
HTH
--
Arun Khan
"As a layman, I would say we have it, but as a scientist I have to
say, 'What do we have?'"
Rolf Heuer, Director General CERN on the announcement of Higgs Boson particle.