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.
> Additional info:
> with "-device e1000" or "-device rtl8139" in qemu-kvm command line also have
> this issue.
>
> with "-net none" in qemu-kvm command line ,pf work well in guest.
we just hit package loss when we first ping.second ping,... works well.
Is the guest configured to use dhcp or static ip address?
Is there a time factor? For instance do you get the same result from:
# ifup eth0; ping -I eth0 www.google.com
as from
# ifup eth0; sleep 30; ping -I eth0 www.google.com
If you ifdown and re-do the test, do you again experience some packets lost or is it once per boot?
I could imagine emulated devices could drop packets if the bridge forwarding delay is set wrong. In those cases, what bridge is being used and how is it configured?
I agree with Dor that it would be useful to see tcpdumps.