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.
Created attachment 1456347[details]
VM XML
Description of problem:
We fail booting VM with vhost-user. Seems libvirt fails translate the socket path of vhost-user.
Version-Release number of selected component (if applicable):
3.10.0-916.el7.x86_64
libvirt-4.5.0-1.el7.x86_64
qemu-kvm-rhev-2.12.0-6.el7.x86_64
How reproducible:
100%
Steps to Reproduce:
1. Boot VM with vhost-user socket, full XML is attached.
<interface type='vhostuser'>
<mac address='18:66:da:5f:dd:22'/>
<source type='unix' path='/tmp/vhostuser0.sock' mode='server'/>
<model type='virtio'/>
<driver name='vhost' queues='2' rx_queue_size='512'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/>
</interface>
<interface type='vhostuser'>
<mac address='18:66:da:5f:dd:23'/>
<source type='unix' path='/tmp/vhostuser1.sock' mode='server'/>
<model type='virtio'/>
<driver name='vhost' queues='2' rx_queue_size='512'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/>
</interface>
2. Boot VM, fail. The qemu command line shows that "path=" is not translated. This option is important to vhost-user.
# virsh start rhel7.6_nonrt
error: Failed to start domain rhel7.6_nonrt
error: internal error: qemu unexpectedly closed the monitor: 2018-07-04T00:52:53.619540Z qemu-kvm: -chardev socket,id=charnet1,fd=30,server: info: QEMU waiting for connection on: disconnected:unix:/tmp/vhostuser0.sock,server
2018-07-04T00:52:54.498544Z qemu-kvm: -chardev socket,id=charnet2,fd=31,server: info: QEMU waiting for connection on: disconnected:unix:/tmp/vhostuser1.sock,server
2018-07-04T00:52:54.500301Z qemu-kvm: chardev "charnet1" does not support FD passing
Actual results:
VM with vhost-user fail boot up.
Expected results:
VM with vhost-user should boot up.
Additional info:
1. This is not qemu bug, as qemu command line works well as expected.
2. This should be libvirt regression bug, as libvirt-4.4.0-2.el7.x86_64 works well.
Libvirt switched to using FD passing for all UNIX sockets.
Unfortunately it appears QEMU has a bug which causes this to break vhostuser. I've sent a fix for the QEMU bug:
https://lists.gnu.org/archive/html/qemu-devel/2018-07/msg01147.html
but we'll need to workaround it in libvirt too
(In reply to Daniel Berrange from comment #4)
> Libvirt switched to using FD passing for all UNIX sockets.
>
> Unfortunately it appears QEMU has a bug which causes this to break
> vhostuser. I've sent a fix for the QEMU bug:
>
> https://lists.gnu.org/archive/html/qemu-devel/2018-07/msg01147.html
>
> but we'll need to workaround it in libvirt too
Thanks Daniel.
From QE perspective, a BZ in qemu-kvm-rhev component is needed, we file bug[1] to track this issue:
[1]Bug 1598269 - vhost-user socket path is not recognized by libvirt - [QEMU side]
Best Regards,
Pei
Update:
Versions:
libvirt-4.5.0-2.el7.x86_64
Results:
This bug can not be reproduced anymore with above version. Guest with vhost-user can boot up and works well as expected.
Thanks Daniel for your efforts.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHSA-2018:3113
Created attachment 1456347 [details] VM XML Description of problem: We fail booting VM with vhost-user. Seems libvirt fails translate the socket path of vhost-user. Version-Release number of selected component (if applicable): 3.10.0-916.el7.x86_64 libvirt-4.5.0-1.el7.x86_64 qemu-kvm-rhev-2.12.0-6.el7.x86_64 How reproducible: 100% Steps to Reproduce: 1. Boot VM with vhost-user socket, full XML is attached. <interface type='vhostuser'> <mac address='18:66:da:5f:dd:22'/> <source type='unix' path='/tmp/vhostuser0.sock' mode='server'/> <model type='virtio'/> <driver name='vhost' queues='2' rx_queue_size='512'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </interface> <interface type='vhostuser'> <mac address='18:66:da:5f:dd:23'/> <source type='unix' path='/tmp/vhostuser1.sock' mode='server'/> <model type='virtio'/> <driver name='vhost' queues='2' rx_queue_size='512'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/> </interface> 2. Boot VM, fail. The qemu command line shows that "path=" is not translated. This option is important to vhost-user. # virsh start rhel7.6_nonrt error: Failed to start domain rhel7.6_nonrt error: internal error: qemu unexpectedly closed the monitor: 2018-07-04T00:52:53.619540Z qemu-kvm: -chardev socket,id=charnet1,fd=30,server: info: QEMU waiting for connection on: disconnected:unix:/tmp/vhostuser0.sock,server 2018-07-04T00:52:54.498544Z qemu-kvm: -chardev socket,id=charnet2,fd=31,server: info: QEMU waiting for connection on: disconnected:unix:/tmp/vhostuser1.sock,server 2018-07-04T00:52:54.500301Z qemu-kvm: chardev "charnet1" does not support FD passing Actual results: VM with vhost-user fail boot up. Expected results: VM with vhost-user should boot up. Additional info: 1. This is not qemu bug, as qemu command line works well as expected. 2. This should be libvirt regression bug, as libvirt-4.4.0-2.el7.x86_64 works well.