Uploaded image for project: 'RHEL'
  1. RHEL
  2. RHEL-39332

virt-v2v does not know about <interface type='vds'> network devices

Linking RHIVOS CVEs to...Migration: Automation ...Sync from "Extern...XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Normal Normal
    • None
    • rhel-9.2.0
    • virt-v2v
    • None
    • None
    • Moderate
    • rhel-virt-tools
    • ssg_virtualization
    • 5
    • False
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • None
    • None

      When migrating a VM with multiple network cards from VMware to OCP-V, the order of the network cards should be maintained. As an example, the attached vmware screenshot(s)  shows the following order:

      • Network adapter 1 - 00:50:56:86:90:ed
      • Network adapter 2 - 00:50:56:86:1a:3b
      • Network adapter 3 - 00:50:56:86:1a:fc
      • Network adapter 4 - 00:50:56:86:77:ab

      The converted VM using MTV has the following as part of the VM definition:

      ```
      interfaces:
        - bridge: {}
           macAddress: '00:50:56:86:1a:fc'
           model: virtio
           name: net-0
        - bridge: {}
           macAddress: '00:50:56:86:1a:3b'
           model: virtio
           name: net-1
        - bridge: {}
           macAddress: '00:50:56:86:90:ed'
           model: virtio
           name: net-2
        - bridge: {}
           macAddress: '00:50:56:86:77:ab'
           model: virtio
           name: net-3
      ```
      NOTE: the first and third interfaces in the list are swapped. I have attached the logs from the migration container.

              rhn-eng-rjones Richard Jones
              mdeneve@redhat.com Mark DeNeve
              virt-maint virt-maint
              virt-bugs virt-bugs
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: