Issue/Introduction

This article describes how to troubleshoot an abnormal VM instance network after V2V migration. It applies to the initial diagnosis and resolution of similar issues in ZStack Cloud.

Environment

• Product: ZCF
• Component: Cloud
• Version: 3.x-5.5.30

Symptoms

After a Linux VM instance is migrated through V2V migration, its network service cannot start normally.

Possible causes

The source NIC device name is typically ens33 on VMware but eth0 or eth1 on KVM. Because the names differ, the configuration file cannot identify the NIC and the network service cannot start.

Resolution

1. Run the following command in the VM instance operating system to open the NIC configuration file directory:

  [root@localhost ~]#  cd /etc/sysconfig/network-scripts/

2. Run the following command to edit the NIC configuration file:

  [root@localhost ~]#  vim ifcfg-ens33

3. Change the NAME and DEVICE parameters to eth0.

4. Run the following command to save the change and exit:

  [root@localhost ~]#  mv /etc/sysconfig/network-scripts/ifcfg-ens33 /etc/sysconfig/network-scripts/ifcfg-eth0

5. Run the following command to restart the network service:

  [root@localhost ~]#  systemctl restart network