OpenStack Mirroring-the eth0 boot failure of the NIC after booting a mirror with clone virtual mechanism

Source: Internet
Author: User

1, recently, to get a colleague through cloning to do a mirror, upload to the cloud platform, after the load network card, found that eth0 access to IP, restart the network service

service network restart shutting downloopback insterface:                                                               [  OK  ]Bringing uploopback insterface:                                                                 [  OK  ]Bringing upinterface eth0:  Device eth0  does notseem to Be present,delaying initialization. [failed] 

2, after a multi-party lookup, because the clone of the previous virtual machine MAC address information copied to the network configuration information in the mirror, exists in the Eth0 network card, and the Udev network card profile eth0 field of the Mac Association, resulting in the current image to create a cloud host boot, Udev automatically generated a new MAC address, found that eth0 already exists cloned Mac information, so the newly generated Mac named Eth1, because the eth0 Mac information is cloned, Udev generated Mac is not synchronized to the eth0 NIC configuration, Therefore, the system considers that Eth0 's Mac information is incorrect and therefore fails to start.


Workaround:

(1) The ETH0 network card configuration information in the Mac to Udev new generated MAC address, and delete the Udev network card information configuration file eth0 field, change eth1 to eth0, save and restart the system.

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. #net   device  ()   (custom name provided by external tool) subsystem== "NET",  action== "Add",  drivers== "? *", attr{address}== "08:00:27:16:31:11″, attr{type}==" 1″, KERNEL== "eth* ", name=" Eth0″ #net  device  () subsystem== "net",  action== "Add",  drivers== "? *", attr{address}== " 08:00:27:32:66:63″, attr{type}== "1″, kernel==" eth* ", name=" Eth1″ 
Vim/etc/sysconfig/network-scripts/ifcfg-eth0/etc/sysconfig/network-scripts/ifcfg-eth0hwaddr=08:00:27:16:31:11 # Modify the hwaddr=08:00:27:32:66:63 for eth1
vim/etc/udev/rules.d/70-persistent-net.rulessubsystem== "NET", action== "Add", drivers== "? *", attr{address}== " 08:00:27:32:66:63″, attr{type}== "1″, kernel==" eth* ", name=" Eth0″ #将eth0那一行删除, then change eth1 to Eth0

  (2) directly delete /etc/udev/rules.d/70-persistent-net.rules the file (deleting the file does not affect system crashes, is automatically generated after the system restarts), and then removes the /etc/sysconfig/network-scripts/ifcfg-eth0 h WADDR and UUID two lines, shutdown restart.  

This article is from the "Youth Memory" blog, please be sure to keep this source http://mltyrone.blog.51cto.com/6204409/1828872

OpenStack Mirroring-the eth0 boot failure of the NIC after booting a mirror with clone virtual mechanism

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.