Network card not initialized on SLES 11 target physical machine

  • 7012911
  • 19-Jul-2013
  • 05-May-2016

Environment

PlateSpin Migrate
Source is cloned SLES 11 VM on VMware ESX host
Target is a physcial machine or VM (faked as physical)

Situation

SLES 11 workload (cloned VM) migration via semi-automated method to target VM (faked physical) on Windows 2008 Hyper-V host gets stuck at step 8.1 "Configuring OS".

Resolution

Follow the steps below to resolve this issue:
 
1. Before booting target VM with take control ISO (bootofx2p.iso), analyze the cloned SLES 11 VM, to check if NIC name matches with it's index.

2. Run the "ifconfig" command to determine which NIC are active.

3. Using the NIC information from step 2, verify device naming convention and MAC address of the NIC by executing the following command:

    more /etc/udev/rules.d/70-persistent-net.rules

4. Remove the non existing Network Interface Card in "/etc/udev/rules.d/70-persistent-net.rules" file by editing it.

5. Ensure that NIC "NAME" attribute in "/etc/udev/rules.d/70-persistent-net.rules" file starts from "eth0" and goes on like "eth1", "eth2" for more NICs.

6. Refresh discovery of the source SLES 11 VM prior to configuring the V2P job to fake physical target.

Cause

After cloning a SLES 11 VM, ESX will generate a new MAC address for the NIC in cloned machine.Since the source workload (cloned copy) OS (SLES 11 32 bit) is unaware of the cloning, while detecting the devices during first boot, UDEV daemon creates and appends a new rule to the file "/etc/udev/rules.d/70-persistent-net.rules" and names this new NIC as "eth1". The old NIC (identified by the MAC address) retains the name of "eth0" in the above mentioned UDEV rules file.

Feedback service temporarily unavailable. For content questions or problems, please contact Support.