Description of problem:

Create a cold migration plan to migrate a shutoff VM with "Preserve Static IPs" on, the plan page is without warning message below, which will cause user migrate a shutoff VM, and the VM will not have static ip settings on the target cluster, especially for win2008 r2/sp2 VMs which need to install additional drivers.

"Guest information on vNICs is missing, cannot preserve static IPs. Make sure VMware tools are installed and the VM is running."

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

MTV 2.8.5 with CNV 4.18.6,
MTV 2.9.0(forklift-fbc-prod-v418:on-pr-16546d253dda4fc8d8b838f0703040f30a985cf0) with CNV 4.18.7

How reproducible:

Always

Steps to Reproduce:

1) Try to create a migration plan to migrate a shutoff VM: mtv-func-win2008r2-test or mtv-func-WIN2019-test from vCenter7, VM Network, Mgmt Network are mapping to NAD bridge networks, set the "Preserve Static IPs": on

2) The plan for VM: mtv-runc-win2018r2-test is without warning

3) The plan for VM: mtv-func-WIN2019-test is with warning for VM name, but without the warning for static ip:

"Guest information on vNICs is missing, cannot preserve static IPs. Make sure VMware tools are installed and the VM is running."

4) Check the conversion pod log for migrating VM: mtv-func-win2019-test, the virt-v2v command line without ip address/ gateway/ dns settings, which will cause the target VM without static IPs, more details in attached file: cold-2019-staticip-vm-1034-ftl88-virt-v2v.log

 Check the plan is executed successfully, login to VM check the static ip settings are not existed

Building command:virt-v2v[-v -x -o kubevirt -os /var/tmp/v2v -on mtv-func-win2019-test -i libvirt -ic vpx://administrator%40vsphere.local@10.**/data/host/10.**?no_verify=1 -ip /etc/secret/secretKey --root first -it vddk -io vddk-libdir=/opt/vmware-vix-disklib-distrib -io vddk-thumbprint=9B:33:C8:10:11:0B:DA:66:9B:9B:E7:0D:CB:E9:8D:A5:A6:DB:E5:93 -- mtv-func-WIN2019-test]Building command:/usr/local/bin/virt-v2v-monitor[]virt-v2v monitoring: Setting up prometheus endpoint :2112/metrics

5) On newer version, check the conversion pod for migrating VM: mtv-runc-win2018r2-test is with ip address/gateway/ dns settings, but the driver is not correct, more details in pod log:[ cold-2008r2-test-vm-1350-t2pk4-virt-v2v.log|cold-2008r2-test-vm-1350-t2pk4-virt-v2v.log] , login to VM on target cluster, check the driver is not correct, no network adapter is detected, thus no static ip settings

Actual results:

Step2: The plan is without the warning for static ip, user start the plan without power on VM
Step5: The target VM is without static IP settings

Expected results:

Step2: The plan is with the warning for static ip, which need the VM is running, reminder the user to power on the VM on source provider
Step5: The target VM is with correct driver and with static IP settings