Today, under VMware installed CentOS 6.9, after installation, ifconfig, found that eth0 can not obtain IP, recall that the previous installation of the Redhat virtual machine did not appear this problem, so, compared to two virtual machine settings, Discover that the network connection mode for the Redhat virtual machine is bridged, and CentOS is NAT
650) this.width=650; "Src=" https://s5.51cto.com/wyfs02/M00/9D/E4/wKioL1mIKMmynjA8AABSfcRsVfA953.jpg-wh_500x0-wm_ 3-wmp_4-s_3698770108.jpg "title=" PIC1. JPG "alt=" Wkiol1mikmmynja8aabsfcrsvfa953.jpg-wh_50 "/>
Change to bridging mode first, and then open the VMware Virtual Network editor to determine, but service network restart or ifcfg-eth0 up still does not work, and restarting the virtual machine is not working. Changed the etc/sysconfig/ The Onboot option in Network-scripts/ifcfg-eth0 is yes, still not available,
Later thought of Redhat virtual machine can be acquired, which virtual machine up to see, redhat up and found that the same can not get IP problems, is it a virtual machine problem?
Workaround:
Immediately cmd, Services.msc discovers that several key services for the virtual machine are turned off,
650) this.width=650; "Src=" https://s2.51cto.com/wyfs02/M00/9D/E5/wKiom1mIKzTh4pgBAABl9EEvRLQ173.jpg-wh_500x0-wm_ 3-wmp_4-s_2959691588.jpg "title=" Pic2. JPG "alt=" Wkiom1mikzth4pgbaabl9eevrlq173.jpg-wh_50 "/>
Decisively start the service, ifconfig, this time there is IP, the original VMware DHCP service did not start, the specific shutdown reason is ominous, possible error operation caused.
This article is from the "Bean Daddy Blog" blog, please make sure to keep this source http://imlearner.blog.51cto.com/9615100/1954248
Unable to obtain IP reason records after installation of CentOS under VMware