In addition to Weibo, there is also WeChat
Please pay attention
WeChat public account
Shulou
2025-01-30 Update From: SLTechnology News&Howtos shulou NAV: SLTechnology News&Howtos > Servers >
Share
Shulou(Shulou.com)06/01 Report--
This article shows you how to restart the VMware virtual machine network error "Error: No suitable device found", the content is concise and easy to understand, it will definitely brighten your eyes. I hope you can get something through the detailed introduction of this article.
Error in cloning CentOS in VMware virtual machine and restarting network times
[root@localhost ~] # service network restart
Shutting down loopback interface: [OK]
Bringing up loopback interface: [OK]
Bringing up interface eth0: Error: No suitable device found: no device found for connection 'System eth0'.
[FAILED]
Check the network settings and find that there is a problem with the MAC address configuration of the network card.
[root@localhost ~] # cat / etc/sysconfig/network-scripts/ifcfg-eth0
DEVICE= "eth0"
BOOTPROTO= "dhcp"
HWADDR= "00:0c:29:f5:68:ae"
IPV6INIT= "yes"
NM_CONTROLLED= "yes"
ONBOOT= "yes"
TYPE= "Ethernet"
UUID= "08734f61-956d-4d50-b8ca-ef9fd9242f60"
[root@localhost ~] # cat / etc/sysconfig/network-scripts/ifcfg-eth2
DEVICE=eth2
BOOTPROT=static
HWADDR= "00:0c:29:f5:68:b8"
IPADDR=192.168.174.30
GATEWAY=192.168.174.1
NETMASK=255.255.255.0
ONBOOT=yes
[root@localhost ~] # cat / etc/udev/rules.d/70-persistent-net.rules
# This file was automatically generated by the / lib/udev/write_net_rules
# program, run by the persistent-net-generator.rules rules file.
#
# You can modify it, as long as you keep each rule on a single
# line, and change only the value of the NAME= key.
# PCI device 0x8086:0x100f (e1000) (custom name provided by external tool)
SUBSYSTEM== "net", ACTION== "add", DRIVERS== "? *", ATTR {address} = = "00:0c:29:f5:68:ae", ATTR {type} = = "1", KERNEL== "eth*", NAME= "eth0"
# PCI device 0x8086:0x100f (e1000)
SUBSYSTEM== "net", ACTION== "add", DRIVERS== "? *", ATTR {address} = = "00:0c:29:f5:68:b8", ATTR {type} = = "1", KERNEL== "eth*", NAME= "eth2"
# PCI device 0x8086:0x100f (e1000)
SUBSYSTEM== "net", ACTION== "add", DRIVERS== "? *", ATTR {address} = = "00:0c:29:05:7a:9d", ATTR {type} = = "1", KERNEL== "eth*", NAME= "eth3"
# PCI device 0x8086:0x100f (e1000)
SUBSYSTEM== "net", ACTION== "add", DRIVERS== "? *", ATTR {address} = = "00:0c:29:05:7a:a7", ATTR {type} = = "1", KERNEL== "eth*", NAME= "eth4"
Change the network card settin
[root@localhost ~] # cat / etc/sysconfig/network-scripts/ifcfg-eth0
DEVICE= "eth0"
BOOTPROTO= "dhcp"
HWADDR= "00:0c:29:05:7a:9d"
IPV6INIT= "yes"
NM_CONTROLLED= "yes"
ONBOOT= "yes"
TYPE= "Ethernet"
UUID= "08734f61-956d-4d50-b8ca-ef9fd9242f60"
[root@localhost ~] # cat / etc/sysconfig/network-scripts/ifcfg-eth2
DEVICE=eth2
BOOTPROT=static
HWADDR= "00:0c:29:05:7a:a7"
IPADDR=192.168.174.30
GATEWAY=192.168.174.1
NETMASK=255.255.255.0
ONBOOT=yes
Delete the Nic information in the configuration file below
[root@localhost ~] # cat / etc/udev/rules.d/70-persistent-net.rules
# This file was automatically generated by the / lib/udev/write_net_rules
# program, run by the persistent-net-generator.rules rules file.
#
# You can modify it, as long as you keep each rule on a single
# line, and change only the value of the NAME= key.
Return to normal after restarting the virtual machine
[root@localhost ~] # reboot
[root@localhost ~] # ifconfig
Eth0 Link encap:Ethernet HWaddr 00:0C:29:05:7A:9D
Inet addr:192.168.174.133 Bcast:192.168.174.255 Mask:255.255.255.0
Inet6 addr: fe80::20c:29ff:fe05:7a9d/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:26 errors:0 dropped:0 overruns:0 frame:0
TX packets:29 errors:0 dropped:0 overruns:0 carrier:0
Collisions:0 txqueuelen:1000
RX bytes:3445 (3.3KiB) TX bytes:3147 (3.0KiB)
Eth2 Link encap:Ethernet HWaddr 00:0C:29:05:7A:A7
Inet addr:192.168.174.30 Bcast:192.168.174.255 Mask:255.255.255.0
Inet6 addr: fe80::20c:29ff:fe05:7aa7/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:8 errors:0 dropped:0 overruns:0 frame:0
TX packets:16 errors:0 dropped:0 overruns:0 carrier:0
Collisions:0 txqueuelen:1000
RX bytes:1696 (1.6 KiB) TX bytes:1045 (1.0 KiB)
Lo Link encap:Local Loopback
Inet addr:127.0.0.1 Mask:255.0.0.0
Inet6 addr: 1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:12 errors:0 dropped:0 overruns:0 frame:0
TX packets:12 errors:0 dropped:0 overruns:0 carrier:0
Collisions:0 txqueuelen:0
RX bytes:720 (720.0 b) TX bytes:720 (720.0 b)
The above content is the VMware virtual machine restart network error "Error: No suitable device found" what to do, have you learned the knowledge or skills? If you want to learn more skills or enrich your knowledge reserve, you are welcome to follow the industry information channel.
Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.
Views: 0
*The comments in the above article only represent the author's personal views and do not represent the views and positions of this website. If you have more insights, please feel free to contribute and share.
Continue with the installation of the previous hadoop.First, install zookooper1. Decompress zookoope
"Every 5-10 years, there's a rare product, a really special, very unusual product that's the most un
© 2024 shulou.com SLNews company. All rights reserved.