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:

Based on https://bugzilla.redhat.com/show_bug.cgi?id=1403896 there is a high packet loss on Windows after live migration.

Support for the VIRTIO_NET_F_GUEST_ANNOUNCE feature is needed in Windows driver to handle live migration.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

https://github.com/virtio-win/kvm-guest-drivers-windows/pull/102

Created attachment 1268602 [details]
Test 29.03 (3.04) summary

*** Bug 1403896 has been marked as a duplicate of this bug. ***

Back to modified as I added this by mistake.

Is this BZ implemented in the 139 build that I got from MS?

(In reply to Danilo Cesar de Paula from comment #91)
> Is this BZ implemented in the 139 build that I got from MS?

Yes

Hi Yan and Pierre-André

if this bug can be counted as verified as there is still customer issues?

Thanks
Yu Wang

Hi Yu,

Yes, we are still investigating this bug with customer.

Regards,
Pierre-André

Can you confirm that? I'm closing the errata buglist.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2017:2341