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:
# virsh attach-device --live <domain> filesystem.xml
yields:
error: Failed to attach device from filesystem.xml
error: Operation not supported: live attach of device 'filesystem' is not supported
whereas:
# virsh attach-device --persistent <domain> filesystem.xml
works and with subsequent 'virsh start' of the domain and an accompanying virtiofsd process sharing between host and guest works fine.
Version-Release number of selected component (if applicable):
[test@osp-storage-04 ~]$ virsh --version
6.0.0
How reproducible:
100%
Steps to Reproduce:
1. Define a domain with shared memory backing and numa topology as at https://libvirt.org/kbase/virtiofs.html
2. virsh start the guest VM
3. attempt 'virsh attach-device --live <domain> filesystem.xml' with appropriate XML device configuration as described at the just-mentioned Kbase.
Actual results:
Error message as reported.
Expected results: Successful hot-plug attach of the virtiofs files sytem to the running guest.
Would expect corresponding 'virsh detatch-device --live ...' commands to work as well.
Additional info:
We need this to work for OpenStack Nova to support virtiofs devices.
Please note that I reported libvirt 6.0.0 above testing on Red Hat Enterprise Linux release 8.4 Beta (Ootpa) but I get the same result attempting --live device-attach on 6.6.0 running on Fedora release 33 (Thirty Three)
I tried a device hot add of virtiofs device with qemu and it worked. So it looks like that lower layer pieces are in place and support will need to be added to virsh/libvirt.
To keep it simple, I booted a VM with qemu directly. First I hot removed a virtiofs device.
$(monitor) device_del myvirtiofs
And then re-added it back.
$(monitor) device_add vhost-user-fs-pci,bus=root1,id=myvirtiofs,chardev=char0,tag=myfs,queue-size=1024,cache-size=16G
And it works. All this while virtiofs daemon is already running.
Supporting vhost-user-fs-pci device hot add/remove is also important from live migration point of view. We don't have full support for live migration, so current workaround is that hot remove virtiofs device on source and then hot add it back on destination. So from that perspective also it will be nice to have this support added to libvirt.
https://listman.redhat.com/archives/virtio-fs/2021-May/msg00002.html
Verify this bug with:
libvirt-7.9.0-1.el9.x86_64
qemu-kvm-6.1.0-6.el9.x86_64
Please refer to Comment #10 for verification steps. As the testing results match with the expected reuslts, 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 (new packages: libvirt), 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/RHBA-2022:2390