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.
Descriptionyalzhang@redhat.com
2022-02-17 07:52:29 UTC
Description of problem:
VM with virtio filesystem can not start successfully with virtiofsd
Version-Release number of selected component (if applicable):
virtiofsd-1.1.0-1.el9.x86_64
How reproducible:
100%
Steps to Reproduce:
1. On a rhel 9 host, install libvirt and qemu-kvm package, virtiofsd will be installed as dependency;
2. Start a vm with filesystem setting, it will fail:
# mkdir /path1
# virsh dumpxml rhel9
...
<filesystem type='mount' accessmode='passthrough'>
<driver type='virtiofs'/>
<binary path='/usr/libexec/virtiofsd' xattr='on'>
<cache mode='none'/>
<lock posix='on' flock='on'/>
</binary>
<source dir='/path1'/>
<target dir='mount_tag'/>
<address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/>
</filesystem>
...
# virsh start rhel9
error: Failed to start domain 'rhel9'
error: internal error: virtiofsd died unexpectedly
# cat rhel9-fs0-virtiofsd.log
error: Invalid compat argument '-o flock'
(Refer to bug 2055284#c5, remote locks is not properly supported in virtiofsd.)
Actual results:
VM with virtio filesystem setting can not start with virtiofsd
Expected results:
virtiofsd process should drop '-o flock' or reject enabling it, and VM should start successfully
Additional info:
Comment 7yalzhang@redhat.com
2022-02-23 03:35:25 UTC
Hi Sergio, do we plan to support remote POSIX locks in rhel 9.0? If it is a future feature and not in the 9.0 plan, we may need to do another direction: 1) to remove the compat argument '-o flock' when start virtiofsd process; 2) let virtiofsd works as qemu-virtiofsd to ignore it and to ahead to start the process anyway.
As currently we have transfered from qemu-virtiofsd to virtifsd already(virtiofsd will be installed automatically instead of qemu-virtiofsd), and it caused the regression in comment 0. Please help to evaluate it, Thank you!
Comment 8yalzhang@redhat.com
2022-02-24 08:19:41 UTC
I found the virtiofsd process is generated by libvirt, file Bug 2057882 on libvirt to track this regression issue. Libvirt can drop the '-o flock' option since it can not support.