-
Story
-
Resolution: Unresolved
-
Normal
-
None
-
rhel-9.1.0
-
Medium
-
rhel-virt-tools
-
ssg_virtualization
-
8
-
False
-
False
-
-
None
-
None
-
None
-
None
-
Enhancement
-
-
x86_64
-
None
Description of problem:
[RFE]Guests should have network after v2v conversion if source vmware guest's network is connected to a distributed switch
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 distributed switch of ESXi host to the guest
- cat esx7.0-rhel8.4-with-VDS-network.vmx |grep ethernet
ethernet0.virtualDev = "vmxnet3"
ethernet0.dvs.switchId = "50 34 26 b2 94 e9 3b 16-1d 68 87 bf ff 4a 54 39"
ethernet0.dvs.portId = "7"
ethernet0.dvs.portgroupId = "dvportgroup-1285"
ethernet0.dvs.connectionId = "40347428"
ethernet0.shares = "normal"
ethernet0.addressType = "vpx"
ethernet0.generatedAddress = "00:50:56:b4:ed:5a"
ethernet0.uptCompatibility = "TRUE"
ethernet0.present = "TRUE"
2.Use virsh to dump the guest xml from VMware
- virsh -c vpx://root@10.73.227.27/data/10.73.225.34/?no_verify=1 dumpxml esx7.0-rhel8.4-with-VDS-network
Enter root's password for 10.73.227.27:
<domain type='vmware' xmlns:vmware='http://libvirt.org/schemas/domain/vmware/1.0'>
<name>esx7.0-rhel8.4-with-VDS-network</name>
.....
<interface type='vds'>
<mac address='00:50:56:b4:ed:5a' type='generated'/>
<source switchid='503426b2-94e9-3b16-1d68-87bfff4a5439' portid='7' portgroupid='dvportgroup-1285' connectionid='40347428'/>
<model type='vmxnet3'/>
</interface>
......
3. Convert the guest from VMware to rhv by v2v
- virt-v2v -ic vpx://root@10.73.227.27/data/10.73.225.34/?no_verify=1 -it vddk -io vddk-libdir=/home/vddk7.0.3 -io vddk-thumbprint=76:75:59:0E:32:F5:1E:58:69:93:75:5A:7B:51:32:C5:D1:6D:F1:21 -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 esx7.0-rhel8.4-with-VDS-network --mac 00:50:56:b4:ed:5a:bridge:ovirtmgmt -v -x |& tee > v2v-convert-guest-with-distributed-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:
Guests don't have network after v2v conversion if source vmware guest's network is connected to a distributed switch
Expected results:
As above description
Additional info:
- is duplicated by
-
MTV-1170 Network Interface order should be preserved when migrated from VMWare to OCP-V
-
- Closed
-
-
RHEL-39332 virt-v2v does not know about <interface type='vds'> network devices
-
- Closed
-
- external trackers