Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:

Under Windows the failover feature has more flows than under Linux. This involves at least driver disable/enable/update of the NETKVM driver, the same of VFIO driver, protocol installation/uninstallation that not exist under Linux. Current design defines specific behavior of failover for Windows: if the NETKVM adapter is not bound to the VF (protocol installed and MAC addresses are the same) the NETKVM does not indicate link-up (regardless of virtio-net link status in QEMU). 

This BZ is to ensure the test plan comply with thte design and that various flows are tested (depending, of course, on the type of testing - sanity, regression etc)

Additional point is set of supported SRIOV adapters: Linux supports all the adapters automatically, for Windows we have predefined set of adapters which can be configured to include/exclude specific adapters. This probably also should be reflected in the testing methodology.

And additional point is performance testing. Probably these is also open question of jumbo packets testing.