Environment CentOS: Version 7 [root @ net592 ~] # Uname-aLinuxnet5923.10.0-123.el7.x86_64 #1 S
Environment
CentOS: Version 7
[root@net592 ~] # uname -a Linux net592 3.10.0-123.el7.x86_64 #1 SMP Mon Jun 30 12:09:22 UTC 2014 x86_64 x86_64 x86_64 GNU/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 field to set the Nic typeEthernet0.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 |grep Eth 02:01.0 Ethernet controller: Intel Corporation 82545EM Gigabit Ethernet Controller (Copper) (rev 01) ### Normal use 02:05.0 Ethernet controller: Advanced Micro Devices, Inc. [AMD] 79c970 [PCnet32 LANCE] (rev 10) ### 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.