-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
rhel-10.1
-
No
-
None
-
rhel-virt-core-libvirt-2
-
ssg_virtualization
-
5
-
False
-
False
-
-
None
-
None
-
None
-
None
-
Unspecified
-
Unspecified
-
Unspecified
-
None
What were you trying to do that didn't work?
Can not do virtiofs migration after restart virtqemud
Please provide the package NVR for which the bug is seen:
libvirt-11.3.0-1.el10.x86_64
qemu-kvm-10.0.0-1.el10.x86_64
virtiofsd-1.13.0-1.el10.x86_64
How reproducible is this bug?:
100%
Steps to reproduce
1. Check the virtiofsd capabilities
# /usr/libexec/virtiofsd --print-capabilities
{
"type": "fs",
"features": [
"migrate-precopy",
"separate-options"
]
}
2. Prepare a guest with virtiofs device
# virsh dumpxml avocado-vt-vm1 --xpath //filesystem <filesystem type="mount" accessmode="passthrough"> <driver type="virtiofs" queue="1024"/> <binary path="/usr/libexec/virtiofsd" xattr="on"/> <source dir="/path"/> <target dir="mount_tag"/> <alias name="fs0"/> <address type="pci" domain="0x0000" bus="0x07" slot="0x00" function="0x0"/> </filesystem>
3. Start the guest
# virsh start avocado-vt-vm1 Domain 'avocado-vt-vm1' started
4. Restart virtqemud
# systemctl restart virtqemud
5. Try to do guest migration
# virsh migrate avocado-vt-vm1 qemu+ssh://$target_hostname/system --live --verbose error: Operation not supported: migration with this virtiofs device is not supported
6. Destroy the guest, the start the guest again
# virsh destroy avocado-vt-vm1 Domain 'avocado-vt-vm1' destroyed # virsh start avocado-vt-vm1 Domain 'avocado-vt-vm1' started
7. Without restart virtqemud, try to migrate the guest
# virsh migrate avocado-vt-vm1 qemu+ssh://$target_hostname/system --live --verbose Migration: [100.00 %] # echo $? 0
Actual results
Without restart virtqemud before migration, guest can be migrated.
Expected results
Can do virtiofs migration after restart virtqemud