Reproduced with:
virt-manager-3.2.0-10.el9.noarch
libvirt-7.9.0-1.el9.s390x


# virt-install --hostdev mdev_ee3a80f2_54f3_4c78_b20a_9c37af6ccbc4_matrix --memory 2048 --disk /var/lib/libvirt/images/some.qcow2 --import
...
ERROR    internal error: Cannot parse uuid attribute of element <address>

Need to backport upstream commit 0c146b250384ddddcefd2cc0d76b9e808377ebe5

Due to the machine that meet the test conditions is reserved by someone. I change the itm to 17, Thanks.

Hongzhou, I've been able to verify this already on one of our machines. I'm setting VERIFIED. Please shout if you disagree

Verified with:
virt-manager-3.2.0-11.el9.noarch
Compose ID RHEL-9.0.0-20211217.1

1. virt-install w/ --hostdev mdev succeeded
2. # virt-install --hostdev mdev_ee4541f7_7908_4450_bd41_2838aaef9373_0_0_0062 --print-xml --memory 2048 --disk none
<domain type="kvm">
  <name>vm1</name>
  <uuid>73f196c3-d9c4-4ace-b4c0-0bac9b7097bc</uuid>
  <memory>2097152</memory>
  <currentMemory>2097152</currentMemory>
  <vcpu>1</vcpu>
  <os>
    <type arch="s390x" machine="s390-ccw-virtio">hvm</type>
    <boot dev="hd"/>
  </os>
  <clock offset="utc"/>
  <devices>
    <emulator>/usr/libexec/qemu-kvm</emulator>
    <interface type="network">
      <source network="default"/>
      <mac address="52:54:00:c6:6b:b5"/>
      <model type="virtio"/>
    </interface>
    <console type="pty">
      <target type="sclp"/>
    </console>
    <channel type="unix">
      <source mode="bind"/>
      <target type="virtio" name="org.qemu.guest_agent.0"/>
    </channel>
    <hostdev mode="subsystem" type="mdev" managed="no" model="vfio-ccw">
      <source>
        <address uuid="ee4541f7-7908-4450-bd41-2838aaef9373"/>
      </source>
    </hostdev>
  </devices>
</domain>

Hello Sebastian, Thanks for doing it.

Verified on x86_64 with:
virt-manager-3.2.0-11.el9.noarch
virt-install-3.2.0-11.el9.noarch
libvirt-7.10.0-1.el9.x86_64
qemu-kvm-6.2.0-1.el9.x86_64

1. Prepare a mdev

$uuid=b95426b9-ebe5-49ab-bdfb-f4c79d3bc876
/sys/class/mdev_bus/0000:84:00.0/b95426b9-ebe5-49ab-bdfb-f4c79d3bc876

# virsh nodedev-list --cap mdev
>
mdev_b95426b9_ebe5_49ab_bdfb_f4c79d3bc876_0000_84_00_0

2. run virt-install with --hostdev mdev
#virt-install --hostdev mdev_b95426b9_ebe5_49ab_bdfb_f4c79d3bc876_0000_84_00_0 --print-xml --memory 2048 --disk none
>
<domain type="kvm">
  <name>vm1</name>
  <uuid>aae773ce-0a43-4299-9a12-89b11d60ea05</uuid>
  <memory>2097152</memory>
  <currentMemory>2097152</currentMemory>
  <vcpu>1</vcpu>
  <os>
    <type arch="x86_64" machine="pc-i440fx-rhel7.6.0">hvm</type>
    <boot dev="hd"/>
  </os>
  <features>
    <acpi/>
    <apic/>
  </features>
  <cpu mode="host-model"/>
  <clock offset="utc">
    <timer name="rtc" tickpolicy="catchup"/>
    <timer name="pit" tickpolicy="delay"/>
    <timer name="hpet" present="no"/>
  </clock>
  <pm>
    <suspend-to-mem enabled="no"/>
    <suspend-to-disk enabled="no"/>
  </pm>
  <devices>
    <emulator>/usr/libexec/qemu-kvm</emulator>
    <controller type="usb" model="ich9-ehci1"/>
    <controller type="usb" model="ich9-uhci1">
      <master startport="0"/>
    </controller>
    <controller type="usb" model="ich9-uhci2">
      <master startport="2"/>
    </controller>
    <controller type="usb" model="ich9-uhci3">
      <master startport="4"/>
    </controller>
    <interface type="network">
      <source network="default"/>
      <mac address="52:54:00:95:b1:6b"/>
      <model type="e1000"/>
    </interface>
    <console type="pty"/>
    <input type="tablet" bus="usb"/>
    <graphics type="vnc" port="-1"/>
    <video>
      <model type="vga"/>
    </video>
    <hostdev mode="subsystem" type="mdev" managed="yes" model="vfio-pci" display="off" ramfb="off">
      <source>
        <address uuid="b95426b9-ebe5-49ab-bdfb-f4c79d3bc876"/>
      </source>
    </hostdev>
  </devices>
</domain>


Comment: All the results are as expected.

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: virt-manager), 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:2515