Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 2207741

Summary:	Cannot migrate VMware VM due to Missing essential config entry 'ethernet0.networkName'
Product:	Migration Toolkit for Virtualization	Reporter:	Ales Nosek <anosek>
Component:	Controller	Assignee:	Arik <ahadas>
Status:	CLOSED MIGRATED	QA Contact:	meital avital <mavital>
Severity:	high	Docs Contact:
Priority:	urgent
Version:	2.4.0	CC:	ahadas, mnecas, tuado
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-05-28 10:38:26 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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