This problem has troubled me for a long time, on the internet to find a lot of information, most of them are not reliable information. Hang Daddy!
Below, I'll take a look at how to completely solve the network problem between the virtual machine and the cloned virtual machine.
Solution:
, is my virtual machine kang1 and the virtual machine kang2 cloned through KANG1:
650) this.width=650; "Src=" Http://s5.51cto.com/wyfs02/M00/89/F3/wKioL1gi0dXRYXqMAAAqDQO87Js592.png-wh_500x0-wm_3 -wmp_4-s_3467368635.png "title=" Qq20161109153621.png "alt=" Wkiol1gi0dxryxqmaaaqdqo87js592.png-wh_50 "/>
The kang1 on the top is normal, right? Then look at the cloned kang2:
650) this.width=650; "Src=" Http://s4.51cto.com/wyfs02/M01/89/F3/wKioL1gi0hugI9ZtAAAjX0mR8mg748.png-wh_500x0-wm_3 -wmp_4-s_3812368979.png "title=" Qq20161109153739.png "alt=" Wkiol1gi0hugi9ztaaajx0mr8mg748.png-wh_50 "/>
Amount Always feel wrong! Oh, yes? Where does the eth1 card come from? Obviously this is not right, our virtual machine is obviously only a piece of network card.
This time to let two virtual machine network interoperability, you need to modify the clone machine kang2 Some of the relevant configuration files, the steps are as follows:
① login kang2, enter the network configuration file/etc/sysconfig/network-scripts/ifcfg-eth0 remove the MAC address, the final result such as, and then save the exit.
650) this.width=650; "Src=" Http://s2.51cto.com/wyfs02/M01/89/F3/wKioL1gi0v_iqZz4AAANFoIyI54806.png-wh_500x0-wm_3 -wmp_4-s_3070224455.png "title=" Qq20161109154119.png "alt=" Wkiol1gi0v_iqzz4aaanfoiyi54806.png-wh_50 "/>
② Open a magical configuration file
650) this.width=650; "Src=" Http://s1.51cto.com/wyfs02/M02/89/F7/wKiom1gi1zmwpW2rAAAPxe8XqqA405.png-wh_500x0-wm_3 -wmp_4-s_711801415.png "title=" Qq20161109155728.png "alt=" Wkiom1gi1zmwpw2raaapxe8xqqa405.png-wh_50 "/>
Open the above configuration file, as shown in the so-called eth1 is caused by this rule file.
650) this.width=650; "Src=" Http://s3.51cto.com/wyfs02/M02/89/F7/wKiom1gi2bfBqdeyAAAo_ZWRHNM248.png-wh_500x0-wm_3 -wmp_4-s_3685527437.png "title=" Qq20161109160952.png "alt=" Wkiom1gi2bfbqdeyaaao_zwrhnm248.png-wh_50 "/>
③ we already know that all this is determined by the/etc/udev/rules.d/70-persistent-net.rules file, OK, we deleted the file and solved the problem. Do not worry, this file deleted after the restart of the virtual machine or will be automatically generated Oh!
650) this.width=650; "Src=" Http://s1.51cto.com/wyfs02/M02/89/F4/wKioL1gi2x6RtMy_AAAIX7wIt6w701.png-wh_500x0-wm_3 -wmp_4-s_1213330899.png "title=" Qq20161109161605.png "alt=" Wkiol1gi2x6rtmy_aaaix7wit6w701.png-wh_50 "/>
④ Verify that two virtual machines can ping each other, the current host ip:192.168.1.106 another host ip:192.168.1.118
650) this.width=650; "Src=" Http://s5.51cto.com/wyfs02/M00/89/F4/wKioL1gi3EyCgrGeAAAbHDLm_EM452.png-wh_500x0-wm_3 -wmp_4-s_1193179633.png "title=" Qq20161109162019.png "alt=" Wkiol1gi3eycgrgeaaabhdlm_em452.png-wh_50 "/>
The ok! problem is solved! There is a wooden feel!!!!!
This article is from the "Brother Hong Linux World" blog, so be sure to keep this source http://zhengkangkang.blog.51cto.com/12015643/1871144
Solution to the problem of not pinging each other between virtual machines and cloned virtual machines