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:
In the guest,enable and disable multi queues in a loop,ping guest from another external host during the loop,then transfer 6 files from guest to host,some md5sum value changed.
Version-Release number of selected component (if applicable):
qemu-kvm-rhev-2.3.0-13.el7.ppc64le
kernel-3.10.0-302.el7.ppc64le
How reproducible:
3/3
Steps to Reproduce:
1.Boot the guest with multiple queues and vhost=on:
/usr/libexec/qemu-kvm...-netdev tap,id=hostnet1,script=/etc/qemu-ifup,vhost=on,queues=8 -device virtio-net-pci,netdev=hostnet1,id=net1,mac=00:54:5c:5b:5f:5a,disable-legacy=off,disable-modern=on,vectors=18,mq=on -smp 8
2.Transfer 6 files from guest to host,check the md5sum value of the files before and after transfered
3.Repeatedly change the working queues inside guest:
# for i in $(seq 5000); do for j in 1 2 1 3 1 4 1 5 1 6 1 7 1 8; do ethtool -L eth0 combined $j ; ethtool -l eth0; done; done
4.ping guest from another external host, until the 5000 times finished.
# ping $guest_ip
5.Transfer another 6 files from guest to host,and check the md5sum value of the files before and after transfered
Actual results:
After step2,all the md5sum value are same before and after file transfered from guest to host
After step4,one time no packet lost,two times 1% packet lost
After step5,some md5sum value changed after file transfered from guest to host,I test this issue 3 times ,one time 2 value changed,two times 1 value changed.
Expected results:
The md5sum value should alaways be same before and after file transfered from guest to host.
Additional info:
Are you saying that you have been unable to reproduce with current kernel and qemu? If so, I think we will have to close as INSUFFICIENT_DATA.
It's very surprising that the md5sum would change across the transfer with scp, since scp has internal checksumming. A file mismatch in this case would suggest not a network problem, but a problem either reading the disk on the source, or writing the disk on the destination. Unless the mismatch was due simply to a truncation of the files (interrupted transfer).
(In reply to David Gibson from comment #6)
> Are you saying that you have been unable to reproduce with current kernel
> and qemu? If so, I think we will have to close as INSUFFICIENT_DATA.
>
Yes，I cannot reproduce this issue with the current kernel and qemu.
> It's very surprising that the md5sum would change across the transfer with
> scp, since scp has internal checksumming. A file mismatch in this case
> would suggest not a network problem, but a problem either reading the disk
> on the source, or writing the disk on the destination. Unless the mismatch
> was due simply to a truncation of the files (interrupted transfer).
During the file transfer without any interrupt action.