No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>


To have a better experience, please upgrade your IE browser.


NICs on a Linux VM Were Disordered After the PV Driver Was Upgraded

Publication Date:  2014-07-15 Views:  88 Downloads:  0
Issue Description
After the PV Driver Was upgraded in a FusionCompute V100R003C00 cutover scenario, NICs on a Linux VM became disordered.
When the configuration file /etc/udev/rules.d/70-persistent-net.rules is copied from the Linux VM images of the V100R002C01 version, the MAC addresses of three NICs in the file are from other VMs. When the PV Driver of the V100R003C00 version is installed during the cutover, the previously mentioned MAC addresses use eth0, eth1, and eth2. Therefore, the MAC addresses of the current VM cannot find their mapping NICs, and the VM creates eth3 for its MAC address, which is the same for other NICs. Consequently, the first NIC of the V100R003C00 version in the cutover is eth3. Figure 1 shows the information in /etc/udev/rules.d/70-persistent-net.rules.
Figure 1 Configuration file

Alarm Information
Handling Process
The following two methods are provided depending on different scenarios:
1. If the VM has been created, delete the /etc/udev/rules.d/70-persistent-net.rules file before the upgrade.
2. If a template is being created for the VM, delete the /etc/udev/rules.d/70-persistent-net.rules file after the template is created.
Root Cause
When the PV Driver is configured for the V100R003C00 version, the VM first check the /etc/udev/rules.d/70-persistent-net.rules file for mapping NICs and MAC addresses. If the NICs maps to the MAC addresses, the VM displays them directly. Otherwise, the VM generates NICs for the MAC addresses.