This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
Bug 2207741 - Cannot migrate VMware VM due to Missing essential config entry 'ethernet0.networkName'
Summary: Cannot migrate VMware VM due to Missing essential config entry 'ethernet0.net...
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Migration Toolkit for Virtualization
Classification: Red Hat
Component: Controller
Version: 2.4.0
Hardware: Unspecified
OS: Unspecified
urgent
high
Target Milestone: ---
: ---
Assignee: Arik
QA Contact: meital avital
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-05-16 17:50 UTC by Ales Nosek
Modified: 2023-09-26 04:25 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-05-28 10:38:26 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   MTV-583 0 None None None 2023-05-28 10:38:25 UTC

Description Ales Nosek 2023-05-16 17:50:20 UTC 
When trying to migrate a virtual machine from VMware to OpenShift Virtualization, the migration process fails in the stage of "Convert image to kubevirt". The error message in the mtv-virt-v2v-rhel9 pod says:

virt-v2v: error: exception: libvirt: VIR_ERR_INTERNAL_ERROR: VIR_FROM_NONE: internal error: Missing essential config entry 'ethernet0.networkName'

The migration fails if the VM doesn't have any network interfaces or if the VM is connected to vSphere Distributed Switch. We verified that the migration works for VMs that are connected to vSphere Standard Switch.

This issue is likely caused by a bug in the libvirt-client library. The issue was fixed in version libvirt-client-8.7.0-1.el9.x86_64. See also https://bugzilla.redhat.com/show_bug.cgi?id=1988211.

The Migration Toolkit for Virtualization version 2.4 uses the following library versions:

$ rpm -qa | grep libvirt
libvirt-libs-8.5.0-7.4.el9_1.x86_64
libvirt-daemon-8.5.0-7.4.el9_1.x86_64
libvirt-daemon-driver-network-8.5.0-7.4.el9_1.x86_64
libvirt-daemon-config-network-8.5.0-7.4.el9_1.x86_64
libvirt-daemon-driver-secret-8.5.0-7.4.el9_1.x86_64
libvirt-daemon-driver-storage-core-8.5.0-7.4.el9_1.x86_64
libvirt-client-8.5.0-7.4.el9_1.x86_64
libvirt-daemon-driver-qemu-8.5.0-7.4.el9_1.x86_64

The libvirt-client-8.5.0-7.4.el9_1.x86_64 library is most likely buggy. It would probably be enough to update the libvirt-client to version >= 8.7 to solve the problem.
Comment 5 Red Hat Bugzilla 2023-09-26 04:25:02 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days
Note You need to log in before you can comment on or make changes to this bug.