-
Bug
-
Resolution: Unresolved
-
Critical
-
None
-
2.8.7
-
None
Description of problem:
Migrate VM which need legacy drivers (E.g. windows 2008r2) from vSphere to OCP cluster, failed to boot VM after migration, hit this error:
Version-Release number of selected component (if applicable):
2.8.7 (IIB: forklift-fbc-prod-v418:on-pr-b0d302cc0cc03abc5952c82f33682758a072a42b) with CNV 4.18.13)
How reproducible:
Always
Steps to Reproduce:
1)Warm migrate win2008r2 VM: mtv-func-win2008r2-td from vCenter7 to OCP cluster without set installLegacyDrivers in plan, it'll use installLegacyDrivers=true, according to the windows OS 2008r2.
Set preserved static ip: on, map the VM network to mtv-test/mybridge, Mgmt network to mtv-test/mybridge1.
2) The plan executed successfully, but the VM failed to boot, hit this error:
3) Check the conversion pod log as below, more details in attached file: warm-win2008r2-vm-173-kg99k-virt-v2v.log
virt-v2v-in-place: warning: there are no virtio drivers available for this version of Windows (6.1 x86_64 Server win2k8r2). virt-v2v looks for drivers in /usr/local/virtio-win.iso The guest will be configured to use slower emulated devices.
Actual results:
In step2: The VM failed to boot
Expected results:
In steps: The drivers are installed successfully, Start VM successfully
Additional info: