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 1897708 - [RFE] Implement support for live attach of virtiofs device
Summary: [RFE] Implement support for live attach of virtiofs device
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: libvirt
Version: 9.0
Hardware: All
OS: Linux
high
medium
Target Milestone: rc
: ---
Assignee: Ján Tomko
QA Contact: Lili Zhu
URL:
Whiteboard:
Depends On: 1897710
Blocks: 1887471
TreeView+ depends on / blocked
 
Reported: 2020-11-13 20:40 UTC by Tom Barron
Modified: 2022-05-17 13:03 UTC (History)
13 users (show)

Fixed In Version: libvirt-7.9.0-1.el9
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-05-17 12:45:05 UTC
Type: Feature Request
Target Upstream Version: 7.9.0
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github autotest tp-libvirt pull 3891 0 None Merged [filesystem_device]Add the cases of hotplug_unplug filesystem device 2022-03-09 10:14:54 UTC
Red Hat Product Errata RHBA-2022:2390 0 None None None 2022-05-17 12:45:31 UTC

Description Tom Barron 2020-11-13 20:40:00 UTC 
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.
Comment 1 Tom Barron 2020-11-13 22:02:56 UTC 
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)
Comment 3 Ademar Reis 2020-11-17 21:34:45 UTC 
*** Bug 1897710 has been marked as a duplicate of this bug. ***
Comment 4 Vivek Goyal 2021-01-21 19:01:36 UTC 
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.
Comment 5 Vivek Goyal 2021-05-03 13:28:19 UTC 
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
Comment 8 Ján Tomko 2021-10-06 07:20:04 UTC 
v1 proposed upstream:
https://listman.redhat.com/archives/libvir-list/2021-October/msg00097.html
Comment 9 Ján Tomko 2021-10-12 12:44:08 UTC 
commit b98787303498cfb8426ab27ee62247b164101242
Author:     Ján Tomko <jtomko>
CommitDate: 2021-10-12 14:41:13 +0200

    qemu: implement virtiofs hotplug
    
    https://bugzilla.redhat.com/show_bug.cgi?id=1897708
    
    Signed-off-by: Ján Tomko <jtomko>
    Reviewed-by: Peter Krempa <pkrempa>

git describe: v7.8.0-182-gb987873034
Comment 10 Lili Zhu 2021-11-08 09:56:21 UTC 
Tested with libvirt-7.9.0-1.fc36.x86_64:

1 start a guest with shared memory
 <memoryBacking>
    <access mode='shared'/>
  </memoryBacking>

2. create dir
# mkdir /path2

3. prepare xml snippet
# cat filesystem.xml 
<filesystem type='mount' accessmode='passthrough'>
      <driver type='virtiofs'/>
      <binary path='/usr/libexec/virtiofsd' xattr='on'>
        <cache mode='always'/>
        <lock posix='on' flock='on'/>
      </binary>
      <source dir='/path2'/>
      <target dir='mount_tag2'/>
      <address type='pci' domain='0x0000' bus='0x08' slot='0x00' function='0x0'/>
    </filesystem>

4. attach device
# virsh attach-device avocado-vt-vm1 filesystem.xml 
Device attached successfully

5. mount virtiofs in guest
[In guest]#mkdir /mount2; mount -t virtiofs mount_tag2 /mount2
6. try to write something
[In guest]# dd if=/dev/random of=testfile bs=1M count=1024

7. umount fs, then detach virtiofs device
# virsh detach-device avocado-vt-vm1 filesystem.xml 
Device detached successfully

8. check guest xml
# virsh dumpxml avocado-vt-vm1 |grep filesystem
(no output)
Comment 14 Lili Zhu 2021-11-18 05:52:14 UTC 
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.
Comment 16 errata-xmlrpc 2022-05-17 12:45:05 UTC 
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
Note You need to log in before you can comment on or make changes to this bug.