VirtualBox CentOS-6.7 online troubleshooting _ PHP Tutorial

CentOS-6.7 online troubleshooting under VirtualBox. VirtualBox CentOS-6.7 online troubleshooting 201511218: 10: 43 recently needed to install a CentOS virtual machine, colleagues recommended small VirtualBox to replace the "heavy" VMware, so their own VirtualBox CentOS-6.7 online troubleshooting
18:10:43

Recently I needed to install a CentOS virtual machine, and my colleagues recommended a small VirtualBox to replace "bulky" VMware, so I tried to install a CentOS-6.7 virtual machine on VirtualBox.

The process of installing a virtual machine is similar to that of VMware. if you are familiar with VMware's children's shoes, it is not a problem, but the newly installed virtual machine cannot connect to the network, and many problems have been encountered.

My VirtualBox version is 4.3.24 r98716 and the CentOS-6.7 kernel version is 2.6.32-513.3.1.el6.i686.

1. No suitable device found

This is the first problem encountered by myself, although the Bridge connection mode is set, re-establish the ifcfg-eth0 file, but still encountered a prompt that there is no network device problem, the specific screenshot is as follows:

We can refer to the online solution for this problem:

1. Delete the/etc/udev/rules. d/70-persistent-net.rules file;
2. Analyze whether the actual HWADDR value of ifconig is consistent with that set in the configuration file, that is, view the HWADDR value in the/etc/sysconfig/network-scripts/ifcfg-eth0 file;

After comparison, the two values are indeed inconsistent, and the configuration file is modified again; however, after running, the eth0 port is still faulty:

2. Device not managed by NetworkManager or unavailable

The first thing I think of here is to add parameters in the ifcfg-eth0 configuration file.NM_CONTROLLED = yes, and the problem persists after the system is restarted. Continue to find information on the Internet, and finally found the cause of the problem, CentOS-6.0 and above the system, NetworkManager and Network services at the same time when the problem of Nic management, the solution is to execute the following commands in sequence:

1. Chkconfig NetworkManager off
2. Chkconfig network on
3. Service NetworkManager stop
4. Service network start

Then the problem was solved, but my CentOS still could not bridge the Internet through VitualBox. I thought the problem should be in the VirtualBox settings. Indeed, the virtual network needs to be allowed in the network settings:

The final problem is solved, and the network can be connected.

In addition, it should be noted that the previous use of VMware or VirtualBox using NAT to establish a CentOS-6.7 virtual machine, the network is always unable to connect, and then the use of the Bridge mode, the bridge mode is more stable than the NAT mode.

18:10:43 a CentOS virtual machine needs to be installed recently. my colleagues recommended the small VirtualBox to replace the "bulky" VMware, so they can do it themselves...