The below Windows 10 VM is migrated from a vanilla Windows 10 VM creaed in ESXi/vSphere and migrated to OpenShift via the Migration Toolkit for Virtualization (MTV). Pre-migration, there were NO vmware tools installed in the VM.
One strange behavior witnessed is: Do VirtIO drivers automatically get installed post MTV migration? Last night I set up a fresh Windows 10 VM and migrated it and it installed VirtIO drivers on it's own and rebooted! Where did the drivers come from? The VM should have had no knowledge of VirtIO devices, and the only thing I can think of is these are avilable in Windows update?
Additionally, I do wonder if https://github.com/kubev2v/forklift-controller/issues/468 is related as upon migration, secure boot is improperly flagged on the VM, and upon successful migration into OpenShift, Secure Boot must be manually disabled in UEFI BIOS at least one time to get the VM to boot. Upon successful boot, upon reboot, Secure Boot is re-enabled on it's own (In UEFI BIOS, but not YAML configuration of VM), even with setting the below:
And NOT:
Run from the root of the virtio-win drivers iso (Post mounting it, or unzipping with 7zip):
pnputil /add-driver *.inf /subdirs
Resultion editable from UEFI BIOS
Resultion does not dynamically scale, even when new tab has virtual console
Microsoft Basic Display Adapter always gets applied
What the display should look like with the correct VirtIO driver
What it actually looks like if manually telling Windows to use a specific driver (Notice the error)
Helpful Links:
https://forums.unraid.net/topic/55117-virtual-windows-10-display-set-at-800-x-600/
https://github.com/virtio-win/virtio-win-pkg-scripts/blob/master/README.md