Uploaded image for project: 'Migration Toolkit for Virtualization'
  1. Migration Toolkit for Virtualization
  2. MTV-3796

MTV doesn't recognise the VirtualPCNet32 adapter type from VMware

XMLWordPrintable

    • Incidents & Support
    • False
    • Hide

      None

      Show
      None
    • True
    • Hide
      Improved network interface detection for legacy RHEL 5 32-bit VMs in VMware migration::

      Before this update, {project-short} did not recognize the `VirtualPCNet32` network type in VMware during migration. As a consequence, legacy RHEL 5 32-bit VMs were migrated without network interfaces, causing connectivity issues for users. With this release, {project-short} supports `VirtualPCNet32` NICs and detects 32-bit RHEL5 VMs with the `VirtualPCNet32` network type, enhancing network interface visibility during migration.
      +
      link:https://issues.redhat.com/browse/MTV-3796[MTV-3796]
      Show
      Improved network interface detection for legacy RHEL 5 32-bit VMs in VMware migration:: Before this update, {project-short} did not recognize the `VirtualPCNet32` network type in VMware during migration. As a consequence, legacy RHEL 5 32-bit VMs were migrated without network interfaces, causing connectivity issues for users. With this release, {project-short} supports `VirtualPCNet32` NICs and detects 32-bit RHEL5 VMs with the `VirtualPCNet32` network type, enhancing network interface visibility during migration. + link: https://issues.redhat.com/browse/MTV-3796 [ MTV-3796 ]
    • Bug Fix
    • Done
    • MTV Sprint 5, MTV Sprint 6
    • Low
    • Customer Reported

      Description of problem:

      For legacy 32 bit guest OS, VMware have an option of "Vlance" network type[1]. For these devices, we can see the network type as "VirtualPCNet32"  from VMware mob https://<vcenter-url>/mob/?moid=<vm-id>&doPath=config.hardware.device. This interface is not detected by MTV. The forklift inventory of this VM doesn't show any network interface attached to this VM.

       

      # curl -k -X GET -H "Authorization: Bearer $token" https://127.0.0.1:8443/providers/vsphere/423cef6f-efb9-42db-bcbf-8fc335121c58/vms/vm-86359?detail=1 2>/dev/null' |jq '.nics'
[]

      So when we migrate this VM, it is created without any network interface. 

      Version-Release number of selected component (if applicable):

      Migration Toolkit for Virtualization Operator   2.9.5

      How reproducible:

      Always

      Steps to Reproduce:

      1. Create a RHEL 5 32 bit VM in VMware. Add the interface with "Adapter Type: Flexible" 
2. Try migrating this VM to OpenShift Virtualization. The VM will be created without any interface in OpenShift Virtualization.

      Actual results:

      MTV doesn't recognise the VirtualPCNet32 adapter type from VMware

      Expected results:

      Map it to compatible network driver in OpenShift Virtualization side.

       [1] https://knowledge.broadcom.com/external/article/321259/choosing-a-network-adapter-for-your-virt.html

        1. rhel5-inventory.yaml
          3 kB
        2. image (13).png
          image (13).png
          335 kB

              marnold@redhat.com Matthew Arnold
              rhn-support-nashok Nijin Ashok
              Ameen Barakat Ameen Barakat
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: