Version-Release number of selected component (if applicable):
libvirt libvirt-10.0.0-1.el9.s390x
qemu-kvm qemu-kvm-8.2.0-2.el9.s390x
kernel kernel-5.14.0-408.el9.s390x
 
How reproducible:
100%
 
Steps to Reproduce:
1. prepare a guest 
[root@ibm-xx .libvirt-ci-venv-ci-runtest-61DoYh]# virsh dumpxml avocado-vt-vm1 --xpath //disk
<disk type="file" device="disk">
  <driver name="qemu" type="qcow2"/>
  <source file="/var/lib/avocado/data/avocado-vt/images/jeos-27-s390x.qcow2"/>
  <backingStore/>
  <target dev="vda" bus="virtio"/>
  <boot order="1"/>
  <address type="ccw" cssid="0xfe" ssid="0x0" devno="0x0000"/>
</disk>
 
[root@xx .libvirt-ci-venv-ci-runtest-61DoYh]# virsh dumpxml avocado-vt-vm1 --xpath //memoryBacking
<memoryBacking>
  <access mode="shared"/>
</memoryBacking>
 
2. start this guest
[root@xx .libvirt-ci-venv-ci-runtest-61DoYh]# virsh list 
 Id   Name             State
--------------------------------
 1    avocado-vt-vm1   running
 
 
3. Prepare filesystem device xml with boot order attribute:
 
[root@ibm-z-510 .libvirt-ci-venv-ci-runtest-61DoYh]# cat filesystem_device.xml
<filesystem type="mount" accessmode="passthrough">
<target dir="mount_tag" />
<source dir="/tmp" />
<binary path="/usr/libexec/virtiofsd" />
<boot order="2" />
<driver type="virtiofs" />
</filesystem
 
4. Attach filesystem device to guest
[root@ibm-z-510 .libvirt-ci-venv-ci-runtest-61DoYh]# virsh attach-device avocado-vt-vm1  filesystem_device.xml
error: Failed to attach device from filesystem_device.xml
error: internal error: unable to execute QEMU command 'device_add': Property 'vhost-user-fs-ccw.bootindex' not found
 
 
Expected result:
filesystem device can be attached successfully
 
Actual result:
Failed to attach device with error:Property 'vhost-user-fs-ccw.bootindex' not found