Solve the MAC address problem after Virtual Machine migration

Solve the MAC address problem after migration of virtual machines. After migration of virtual machines under vmware, if the NIC cannot be started, as shown in
Nic startup failed, mainly because of replication. the vmdk file completely copies the Virtual Machine (including the MAC address). Because the MAC of the NIC of the new hardware platform is different from that of the NIC in the system, the NIC cannot be started. Solution: 1. Copy the VM file. vmdk (to prepare for Migration) 2. Create a VM and remove the hard disk from www.2cto.com.
3. Add a hard disk, select an existing virtual disk, and specify the Virtual Machine file. After vmdk is configured, start the virtual machine.

4. Modify the nic mac address assigned to the VM Nic MAC address, enter the following command # vi/etc/sysconfig/network-scripts/ifcfg-eth0 [root @ lnmp-cent6 ~] # Vi/etc/sysconfig/network-scripts/ifcfg-eth0DEVICE = "eth0" HWADDR = "00: 0C: 29: 2f: db: f9 "IPADDR = 10.10.223netmask = 255.255.255.0GATEWAY = 10.10.254nm _ CONTROLLED =" yes "ONBOOT =" yes "~ Www.2cto.com writes the MAC address from the gray MAC address on the right to the ifcfg-eth0 File

5. delete the 70-persistent-net.rules file # rm-rf/etc/udev/rules. d/70-persistent-net.rules6. restart the server # shutdown-r now7. verify whether the NIC can be started # ifconfig # service network restart note: This method is applicable to migration between virtual machines in linux and migration between virtual machines-physical machines. Author ciywind