Solution CentOS 7.0 vmwarevm has no Nic

Solution CentOS 7.0 vmwarevm has no Nic

Environment

CentOS: Version 7

[root@net592~] #uname-a Linuxnet5923.10.0-123.el7.x86_64 #1SMPMonJun3012:09:22UTC2014x86_64x86_64x86_64GNU/Linux

Problem 1: Vmware cannot identify the NIC, And the VM cannot access the Internet.

Problem 2: The vmwarevm cannot bridge the network adapter and prompts that the network cannot be changed to the bridge mode without a host network adapter

Problem 1 Solution

The driver cannot be properly installed due to compatibility issues with Vmware Virtual NICs and linux, and the default Nic type is incompatible.

Find our vmwarevm folder and setVMware virtual machine configuration (. vmx), append a set our Nic type ethernet0.virtualDev = "e1000"

Cause

VMware provides the old AMD PCNet10/100Mbps virtual network card in virtual clients. Later, VMware provides 10/100/Mbit/s performance through a vmxnet-optimized virtual network card similar to some virtualization, which undoubtedly delivers better performance. Now, VMware ESX Server can provide Intel E1000-based Gigabit virtual NICs. From the compatibility and performance perspective, E1000 is a better choice. However, it seems that in the graphic interface of ESX/ESXi 3.5, you cannot directly select the NIC type. You need to configure it manually.

You can select multiple types

The value is "e1000", and the specified Nic type is Intel (R) PRO/1000.
The value is "vlance" and the network card type is AMD PCNet AM79C970A (incompatible by default)

The value is "vmxnet", and the NIC type is VMware PCI Ethernet Adapter.

After the modification is complete, check that Our NIC inter can be used. AMD still cannot be enabled by default.

[root@sky~]#lspci|grepEth02:01.0Ethernetcontroller:IntelCorporation82545EMGigabitEthernetController(Copper)(rev01)### Normal use02:05.0Ethernetcontroller:AdvancedMicroDevices,Inc.[AMD]79c970[PCnet32LANCE](rev10)### Unsupported Centos[root@sky~]#

Problem 2 solution

Set the Vmware bridging settings, delete all the bridging cards net0 net8, restart our computer, and then click Restore Default.

Cause: the Vm Nic is not properly driven.