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:
Checked in guest, if with vhost-user/dpdk as netdev, the offloads of virtio-net all are disabled(off) except gro by default, and cannot enable them by ethtool.

If the guest try to communicate with other systems not only with other vhostuser guests, is it possible to use the offloads?

Version-Release number of selected component (if applicable):
qemu-kvm-rhev-2.3.0-23.el7.x86_64
openvswitch-dpdk-2.4.0-0.10346.git97bab959.1.el7.x86_64
dpdk-2.0.0-9.el7.x86_64
kernel-3.10.0-316.el7.x86_64 (guest/host)

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

In a guest with vhost-user backend (does not matter if it's dpdpk guest driver, virtio-net guest driver, or other) all traffic goes through this backend (it just replaces the normal vhost). 
Hence, there is no effect for the traffic peer (other guest, other net host) on that: everything goes through the vhost-user.
In a normal ovs/dpdk setup (as one example of a vhost-user use case) vhost-user resides in the ovs userspace process, and is terminated on the ovs port. From there on the traffic goes through switching and ends up in another ovs port: it can be normal guest, vhost-user guest or outbound network port.

Currently, vhost-user does not support offloads. It is planed to add it in the future.

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days