According to the data we have and analysis performed, we assume that this bug was caused by anti-virus software in the guest, preventing the virtio drivers from getting successfully installed.

In cases like this, the anti-virus software must be uninstalled in order to perform the migration.

Closing this, as this does not look like it is a bug in the product, but rather a Windows, or anti-virus protection mechanism (feature).

1. Add an admonition Warning that anti-virus can break a migration
2. Add as a Known issue

NOTE

only for VMware

the v2v detects, sadly not MTV, and it might work might fail so just warning should be good

For more information, see:

• https://issues.redhat.com/browse/MTV-2256
• [*https://redhat-internal.slack.com/archives/C014ZTV21L2/p1744875832173089*]