Bug 1780498

Summary: Guest fails to recover receiving packets after vhost-user reconnect
Product: Red Hat Enterprise Linux Advanced Virtualization Reporter: Pei Zhang <pezhang>
Component: qemu-kvmAssignee: Adrián Moreno <amorenoz>
qemu-kvm sub component: General QA Contact: Pei Zhang <pezhang>
Status: CLOSED ERRATA Docs Contact:
Severity: high    
Priority: high CC: aadam, ailan, amorenoz, chayang, ddepaula, jinzhao, juzhang, virt-maint
Version: 8.2Keywords: Regression, TestOnly
Target Milestone: rc   
Target Release: 8.2   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: qemu-kvm-4.2.0-4.module+el8.2.0+5220+e82621dc Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1738768 Environment:
Last Closed: 2020-04-28 15:33:39 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1738768    
Bug Blocks:    

Comment 1 Pei Zhang 2019-12-06 08:27:44 UTC
Versions:
4.18.0-160.el8.x86_64
qemu-kvm-4.2.0-1.module+el8.2.0+4793+b09dd2fb.x86_64

Comment 2 Pei Zhang 2019-12-06 08:30:35 UTC
Hi Adrian,

RHEL8.2-AV also require your patch fix. So I filed this bz to track it. Thanks.


Best regards,

Pei

Comment 3 Adrián Moreno 2019-12-16 14:52:49 UTC
Hi Pei

qemu has been rebased to 4.2 in RHEL8.2-AV as per BZ 1783250. It should contain the patch.

Thanks

Comment 4 Danilo de Paula 2019-12-18 15:53:16 UTC
(In reply to Adrián Moreno from comment #3)
> Hi Pei
> 
> qemu has been rebased to 4.2 in RHEL8.2-AV as per BZ 1783250. It should
> contain the patch.
> 
> Thanks

In that case, please next time set the BZ to POST and define Fixed-In: field to 'qemu-4.2'

Comment 5 Adrián Moreno 2019-12-18 16:55:10 UTC
(In reply to Danilo Cesar de Paula from comment #4)
> (In reply to Adrián Moreno from comment #3)
> > Hi Pei
> > 
> > qemu has been rebased to 4.2 in RHEL8.2-AV as per BZ 1783250. It should
> > contain the patch.
> > 
> > Thanks
> 
> In that case, please next time set the BZ to POST and define Fixed-In: field
> to 'qemu-4.2'

Thanks Danilo.

Comment 6 Pei Zhang 2020-01-07 04:54:32 UTC
Verify this bug following https://bugzilla.redhat.com/show_bug.cgi?id=1738768#c14. 

Verify with qemu-kvm-4.2.0-4.module+el8.2.0+5220+e82621dc.x86_64:

After re-connect vhost-user by re-start ovs, the testpmd RX can receive packets. But all receiving packets show errors after ovs vhost-user reconnect, this is a new issue which Bug 1782528 is tracking.

testpmd> show port stats all 

  ######################## NIC statistics for port 0  ########################
  RX-packets: 1287827    RX-missed: 0          RX-bytes:  77269620
  RX-errors: 864440716
  RX-nombuf:  0         
  TX-packets: 1098456    TX-errors: 0          TX-bytes:  65907360

  Throughput (since last show)
  Rx-pps:            0          Rx-bps:            0
  Tx-pps:            0          Tx-bps:            0
  ############################################################################

  ######################## NIC statistics for port 1  ########################
  RX-packets: 1099637    RX-missed: 0          RX-bytes:  65978220
  RX-errors: 864322174
  RX-nombuf:  0         
  TX-packets: 1286667    TX-errors: 0          TX-bytes:  77200020

  Throughput (since last show)
  Rx-pps:            0          Rx-bps:            0
  Tx-pps:            0          Tx-bps:            0
  ############################################################################



So move this bug to 'VERIFIED'.

Comment 8 Ademar Reis 2020-02-05 23:10:11 UTC
QEMU has been recently split into sub-components and as a one-time operation to avoid breakage of tools, we are setting the QEMU sub-component of this BZ to "General". Please review and change the sub-component if necessary the next time you review this BZ. Thanks

Comment 10 errata-xmlrpc 2020-04-28 15:33:39 UTC
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/RHEA-2020:1587