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 1630143 - virsh domiflist return NULL for the vhostuser interface source
Summary: virsh domiflist return NULL for the vhostuser interface source
Keywords:
Status: CLOSED DUPLICATE of bug 1630164
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: libvirt
Version: 7.6
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Michal Privoznik
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-09-18 05:37 UTC by chhu
Modified: 2018-09-18 08:57 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-09-18 08:57:01 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description chhu 2018-09-18 05:37:05 UTC
Description of problem:
virsh domiflist return NULL for the vhostuser interface source

Version-Release number of selected component (if applicable):
libvirt-4.5.0-9.el7.x86_64
qemu-kvm-rhev-2.12.0-15.el7.x86_64


Test steps:
1. Prepare guest with xml:

  <memoryBacking>
    <hugepages>
      <page size='2048' unit='KiB'/>
    </hugepages>
  </memoryBacking>
  ......
  <cpu mode='custom' match='exact' check='full'>
    <model fallback='forbid'>Broadwell</model>
    ......
    <numa>
      <cell id='0' cpus='0-1' memory='1048576' unit='KiB' memAccess='shared'/>
    </numa>
  </cpu>
  ......
    <interface type='vhostuser'>
      <mac address='52:54:00:93:51:dd'/>
      <source type='unix' path='/var/run/openvswitch/vhost-user1' mode='client'/>
      <model type='virtio'/>
      <alias name='net0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/>
    </interface>

2. Start the guests with vhostuser interface

# virsh start vhostuser1
Domain vhostuser1 started

# virsh list --all
 Id    Name                           State
----------------------------------------------------
 25    vhostuser1                     running

3. Check the virsh domiflist: no source is listed

# virsh domiflist vhostuser1
Interface  Type       Source     Model       MAC
-------------------------------------------------------
vhost-user1 vhostuser  -          virtio      52:54:00:93:51:dd

Actual results:
In step3, the virsh domiflist return NULL for source

Expected results:
In step3, the virsh domiflist return the vhostuser source

Comment 3 Michal Privoznik 2018-09-18 08:57:01 UTC
This is the same bug as 1630164 which deals with both Source and Interface name. Closing is as a duplicate.

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


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