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.
Description of problem:
Error unclear when starting guest with wrong virtiofsd path
Version-Release number of selected component (if applicable):
libvirt-daemon-7.6.0-2.module+el8.5.0+12219+a5ea13d2.x86_64
How reproducible:
100%
Steps to Reproduce:
1. check the virtiofsd.json file
# cat /usr/share/qemu/vhost-user/50-qemu-virtiofsd.json
{
"description": "QEMU virtiofsd vhost-user-fs",
"type": "fs",
"binary": "/usr/libexec/virtiofsd" <==binary path is updated
}
2. prepare a guest with the following xml
...
<filesystem type='mount' accessmode='passthrough'>
<driver type='virtiofs'/>
<binary path='/sbin/virtiofsd'/>
<source dir='/path'/>
<target dir='mount_tag'/>
<address type='pci' domain='0x0000' bus='0x07' slot='0x00' function='0x0'/>
</filesystem>
...
3. start the guest
# virsh start avocado-vt-vm1
error: Failed to start domain 'avocado-vt-vm1'
error: internal error: virtiofsd died unexpectedly
Expected results:
Should report clear error msg to show that virtiofsd binday is not correct.
Additional info:
libvirt actually logs the error into virtiofsd.log:
libvirt: error : cannot execute binary /sbin/virtiofsd: No such file or directory
But checking if the binary exists upfront (virExec does not do that check
for relative paths) and/or reporting the errors from the log from early startup
(like we do with QEMU) would be much more helpful.
Pushed as:
commit 459f8009c29a40b48f1a28846003d1c5d7e04539
Author: Ján Tomko <jtomko>
CommitDate: 2022-02-03 14:15:04 +0100
qemu: virtiofs: check whether the supplied binary exists
Report an error upfront if the binary does not exist
or is not executable.
https://bugzilla.redhat.com/show_bug.cgi?id=1999372
Signed-off-by: Ján Tomko <jtomko>
Reviewed-by: Andrea Bolognani <abologna>
git describe: v8.0.0-276-g459f8009c2
Verified this bug with:
libvirt-8.2.0-1.el9.x86_64
The testing steps are the same with Comment #4.
The testing result matches with the expected result, mark the bug as verified.
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 (Low: libvirt security, bug fix, and enhancement update), 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-2022:8003
Description of problem: Error unclear when starting guest with wrong virtiofsd path Version-Release number of selected component (if applicable): libvirt-daemon-7.6.0-2.module+el8.5.0+12219+a5ea13d2.x86_64 How reproducible: 100% Steps to Reproduce: 1. check the virtiofsd.json file # cat /usr/share/qemu/vhost-user/50-qemu-virtiofsd.json { "description": "QEMU virtiofsd vhost-user-fs", "type": "fs", "binary": "/usr/libexec/virtiofsd" <==binary path is updated } 2. prepare a guest with the following xml ... <filesystem type='mount' accessmode='passthrough'> <driver type='virtiofs'/> <binary path='/sbin/virtiofsd'/> <source dir='/path'/> <target dir='mount_tag'/> <address type='pci' domain='0x0000' bus='0x07' slot='0x00' function='0x0'/> </filesystem> ... 3. start the guest # virsh start avocado-vt-vm1 error: Failed to start domain 'avocado-vt-vm1' error: internal error: virtiofsd died unexpectedly Expected results: Should report clear error msg to show that virtiofsd binday is not correct. Additional info: