Solution: Loading kernel module CAP_SYS_MODULE CAP_NET_ADMIN alias

The following problems occur when cloning a virtual machine, starting, configuring the network, and restarting the network service:

[root@localhost ~]# service network restartLoading kernel module for a network device with CAP_SYS_MODULE (deprecated).  Use CAP_NET_ADMIN and alias netdev-eth0 insteadLoading kernel module for a network device with CAP_SYS_MODULE (deprecated).  Use CAP_NET_ADMIN and alias netdev-eth1 insteadShutting down loopback interface:                          [  OK  ]Bringing up loopback interface:  lo: Disabled Privacy Extensions                                                           [  OK  ]Bringing up interface eth0:  e1000 device eth0 does not seem to be present, delaying initialization.                                                           [FAILED]Bringing up interface eth1:  e1000 device eth1 does not seem to be present, delaying initialization.                                                           [FAILED]

View the network interface. The result is as follows:

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00    inet 127.0.0.1/8 scope host lo    inet6 ::1/128 scope host       valid_lft forever preferred_lft forever2: eth3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000    link/ether 00:0c:29:9e:85:f7 brd ff:ff:ff:ff:ff:ff3: eth2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000    link/ether 00:0c:29:9e:85:01 brd ff:ff:ff:ff:ff:ff

Failed to restart the network, and the corresponding interface was not started. Here it should be eth0 and eth1, but there are eth2 and eth3

See http://haoyun.blog.51cto.com/2038762/1220485 for solutions

This article is from the "good luck" blog, please be sure to keep this source http://haoyun.blog.51cto.com/2038762/1301083