Hi Everyone:
I ran into difficulties creating an Ubuntu Server 12.04.3 LTS VM with dual network adapters on Workstation 10 (ver. 10.0.1). The problem manifests itself in two ways. First, the second network adapter is misidentified and assigned the wrong driver during installation (AMD 79c970 instead of Intel 82545EM). Second, the assignment of logical names to the network adapters are transposed (Network0 --> eth1 and Network1 --> eth0) once the OS is installed preventing connection to the network on boot.
The problem can be replicated and I have tried this on multiple computers running Windows 7 and Windows 8.1. I have included steps that demonstrate the issue and provided two temporary fixes. It would be great if someone would verify the problem so a resolution can be found.
Problem Demonstration
1. Create a new VM with two network adapters (settings shown) and load a Ubuntu Server 12.04.3 LTS ISO image file in CD/DVD drive.
2. I generally disable the floppy drive and I/O devices and have included the following step for completeness. Select VM | Power On | Power On to BIOS and set the following BIOS settings:
3. Begin the installation using the default settings. The first indication of the problem appears on the 'Configure the network' screen (shown) where interface eth1 is assigned the AMD 79c970 driver. The driver should be the Intel 82545EM, the same as shown on interface eth0.
4. Select eth0 as the primary interface. The installation will proceed using eth0 as the primary network adapter. The "Configure the clock' screen shown demonstrates that eth0 has made a connection and identified the time zone.
5. Complete the installation. The VM will reboot once the OS is installed, however, the installed OS will fail to connect to the network (shown) even though is connected properly during installation.
6. Once the operating loads, login and type 'sudo lshw -class network' at the prompt to display the network hardware information. I received the following output:
*-network:0
description: Ethernet interface
product: 82545EM Gigabit Ethernet Controller (Copper)
vendor: Intel Corporation
physical id: 1
bus info: pci@0000:02:01.0
logical name: eth1
version: 01
serial: 00:0c:29:d4:93:a3
size: 1Gbit/s
capacity: 1Gbit/s
width: 64 bits
clock: 66MHz
capabilities: pm pcix bus_master cap_list rom ethernet physical logical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=e1000 driverversion=7.3.21-k8-NAPI duplex=full ip=192.168.1.131 latency=0 link=yes mingnt=255 multicast=yes port=twisted pair speed=1Gbit/s
resources: irq:19 memory:fd5c0000-fd5dffff memory:fdff0000-fdffffff ioport:2080(size=64) memory:e7b00000-e7b0ffff
*-network:1 DISABLED
description: Ethernet interface
product: 79c970 [PCnet32 LANCE]
vendor: Hynix Semiconductor (Hyundai Electronics)
physical id: 2
bus info: pci@0000:02:02.0
logical name: eth0
version: 10
serial: 00:0c:29:d4:93:ad
width: 32 bits
clock: 33MHz
capabilities: bus_master rom ethernet physical logical
configuration: broadcast=yes driver=pcnet32 driverversion=1.35 latency=64 link=no maxlatency=255 mingnt=6 multicast=yes
resources: irq:16 ioport:2000(size=128) memory:e7b10000-e7b1ffff
The output shows that the Network 0 (the primary network) is assigned to eth1 and Network 1 is assigned to eth0 along with their respective drivers. To demonstrate that the network interface names are indeed transposed, edit the network interfaces file '/etc/network/interfaces' and change eth0 to eth1 as shown.
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface
auto lo
iface lo inet loopbacka
# The primary network interface
auto eth1
iface eth1 inet dhcp
Save the changes and reboot. This time, the system will connect to the network and load normally.
Temporary Fixes
Option 1: Install the OS with one network adapter first. Once the OS is installed, add the second adapter. It will be added as eth1 with the proper Intel 82545EM driver. Verify by typing 'sudo lshw -class network' at the command prompt.
Option 2: Power off the VM, remove the second network adapter from the computer, and reboot. The eth1 network interface will be reassigned to eth0 on Network0. Power off the VM, add the second network adapter, and reboot. The new adapter should be assigned to eth1 on Network1 with the proper Intel 82545EM driver. Verify by typing 'sudo lshw -class network' at the command prompt.
Let me know if additional information is needed. Thanks!
Have a GREAT DAY!!
Shaun
I think option 2 is best
Option 2: Power off the VM, remove the second network adapter from the computer, and reboot. The eth1 network interface will be reassigned to eth0 on Network0. Power off the VM, add the second network adapter, and reboot. The new adapter should be assigned to eth1 on Network1 with the proper Intel 82545EM driver. Verify by typing 'sudo lshw -class network' at the command prompt.
Thanks
Take care!