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.
Bug 2057748 - [RFE]Support multiqueue and mtu for vdpa interface type
Summary: [RFE]Support multiqueue and mtu for vdpa interface type
Keywords:
Status: CLOSED DUPLICATE of bug 2024406
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: libvirt
Version: 8.6
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Virtualization Maintenance
QA Contact: yalzhang@redhat.com
URL:
Whiteboard:
: 2057746 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-02-24 02:10 UTC by yalzhang@redhat.com
Modified: 2022-10-19 03:13 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-02-24 12:32:09 UTC
Type: Feature Request
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-113368 0 None None None 2022-02-24 02:26:53 UTC

Description yalzhang@redhat.com 2022-02-24 02:10:44 UTC
Description of problem:
kernel and qemu now support multiqueue and mtu for vdpa type interface, libvirt does not support the settings 

Version-Release number of selected component (if applicable):
libvirt-8.0.0-4.module+el8.6.0+14186+211b270d.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Start vm with vdpa interface with multiqueue setting:
# virsh edit avocado-vt-vm1
...
 <interface type='vdpa'>
      <mac address='52:54:00:3f:fb:21'/>
      <source dev='/dev/vhost-vdpa-0'/>
      <model type='virtio'/>
      <driver queues='4'/>
      <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/>
    </interface>

# virsh start avocado-vt-vm1
error: Failed to start domain 'avocado-vt-vm1'
error: unsupported configuration: interface 52:54:00:3f:fb:21 - multiqueue is not supported for network interfaces of type vdpa

2. Set with mtu:
# virsh edit avocado-vt-vm1
<interface type='vdpa'>
      <mac address='52:54:00:3f:fb:21'/>
      <source dev='/dev/vhost-vdpa-0'/>
      <model type='virtio'/>
<mtu size='5000'/>
      <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/>
    </interface>
error: unsupported configuration: setting MTU on interface type vdpa is not supported yet
Failed. Try again? [y,n,i,f,?]:
error: unsupported configuration: setting MTU on interface type vdpa is not supported yet
Failed. Try again? [y,n,f,?]:

Comment 2 yalzhang@redhat.com 2022-02-24 11:02:59 UTC
*** Bug 2057746 has been marked as a duplicate of this bug. ***

Comment 4 Jaroslav Suchanek 2022-02-24 12:32:09 UTC

*** This bug has been marked as a duplicate of bug 2024406 ***


Note You need to log in before you can comment on or make changes to this bug.