Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Descriptionmxie@redhat.com
2022-09-09 09:53:22 UTC
Created attachment 1910638[details]
guest-has-no-network-after-conversion.png
Description of problem:
Guests won't have network after v2v conversion if source vmware guest's network is attached to standard switch but no entry 'ethernet0.networkName'
Version-Release number of selected component (if applicable):
virt-v2v-2.0.7-6.el9.x86_64
libguestfs-1.48.4-2.el9.x86_64
libvirt-libs-8.7.0-1.el9.x86_64
qemu-img-7.1.0-1.el9.x86_64
nbdkit-server-1.30.8-1.el9.x86_64
libnbd-1.12.6-1.el9.x86_64
guestfs-tools-1.48.2-5.el9.x86_64
How reproducible:
100%
Steps to Reproduce:
1. Prepare a VMware guest and assign a network which is connected to a standard switch of ESXi host to the guest, but the guest vmx file doesn't have entry
'ethernet0.networkName'
#cat esx7.0-rhel9.1-x86_64-uefi-without-secureboot.vmx |grep ethernet
ethernet0.virtualDev = "vmxnet3"
ethernet0.addressType = "vpx"
ethernet0.generatedAddress = "00:50:56:96:4d:83"
ethernet0.uptCompatibility = "TRUE"
ethernet0.present = "TRUE"
ethernet0.pciSlotNumber = "192"
ethernet0.exposeLargeBAR = "TRUE"
2. Use virsh to dump the guest xml from VMware
# virsh -c vpx://root.213.107/data/10.73.212.38/?no_verify=1 dumpxml Auto-esx7.0-rhel9.1-x86_64-uefi-without-network-name
Enter root's password for 10.73.213.107:
<domain type='vmware' xmlns:vmware='http://libvirt.org/schemas/domain/vmware/1.0'>
<name>Auto-esx7.0-rhel9.1-x86_64-uefi-without-network-name</name>
....
<interface type='null'>
<mac address='00:50:56:96:4d:83' type='generated'/>
<model type='vmxnet3'/>
</interface>
.....
3. Convert the guest from VMware to rhv by v2v
virt-v2v -ic vpx://root.213.107/data/10.73.212.38/?no_verify=1 -it vddk -io vddk-libdir=/home/vddk7.0.3 -io vddk-thumbprint=87:F9:29:E7:33:DE:34:68:74:3F:6A:C9:61:96:C3:51:E2:1E:EA:2B -o rhv-upload -oc https://dell-per740-22.lab.eng.pek2.redhat.com/ovirt-engine/api -op /home/rhvpasswd -os nfs_data -ip /home/passwd Auto-esx7.0-rhel9.1-x86_64-uefi-without-network-name --mac 00:50:56:96:4d:83:bridge:ovirtmgmt -v -x |& tee > v2v-convert-guest-with-standard-switch-no-entry-network-name.log
█ 100% [****************************************]
4. Check the guest after conversion, found guest has no network, pls refer to attached screenshot
Actual results:
As above description
Expected results:
Guests have network after v2v conversion or v2v gives a warning about network during conversion if source vmware guest's network is attched to standard switch but no entry 'ethernet0.networkName'
Additional info:
How to create a vmware guest's network is attached to standard switch but no entry 'ethernet0.networkName'
1. Use 'Remove from inventory' to remove a guest from ESXi host on vsphere web client
2. Edit vmx file of above vmware guest to delete entry 'ethernet0.networkName' on the server where vmware guest files are stored
3. Register a new guest from above edited vmx file on vsphere web client, then can find network name is empty in guest's settings, pls refer to screenshot 'vmware-guest-without-network-name.png'
(In reply to mxie from comment #2)
> 2. Edit vmx file of above vmware guest to delete entry
> 'ethernet0.networkName' on the server where vmware guest files are stored
Is this a valid / supported configuration step (by vmware), or does it just work by chance / luck?
What is the purpose of this step? What goal does it serve for a normal vmware user?
Thanks!
(In reply to Laszlo Ersek from comment #4)
> (In reply to mxie from comment #2)
>
> > 2. Edit vmx file of above vmware guest to delete entry
> > 'ethernet0.networkName' on the server where vmware guest files are stored
>
> Is this a valid / supported configuration step (by vmware), or does it just
> work by chance / luck?
>
> What is the purpose of this step? What goal does it serve for a normal
> vmware user?
>
> Thanks!
This is just the way I used to reproduce the bug, in actual customer scenarios, the network name of vmware guest can be empty without editing vmx file. Such as, our another ESXi7.0 host has both standard switch and distributed switch, then open the setting of a guest on this ESXi7.0 host, add a new network device, don't select any network, setting can be saved successfully even if network name is empty. I can send you the VMware env info by mail if you want to try this scenario.