Package: libvirt-clients Version: 6.0.0-4 Severity: minor I've got a Windows 10 VM with a SATA CDROM and a removable USB storage device:
<disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/var/lib/libvirt/images/virtio-win-0.1.173.iso'/> <target dev='sda' bus='sata'/> <readonly/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='unsafe'/> <source file='/tmp/win-usb-fs.dos'/> <target dev='sdb' bus='usb' removable='on'/> <address type='usb' bus='0' port='3'/> </disk> I can eject or insert new media for the CDrom device just fine, but for the USB device I always get Error: No disk found whose source path or target is sdb "virsh domblklist" gives me the expected output: vdb /var/lib/libvirt/images/win10.qcow2 sdb /tmp/win-usb-fs.dos sda /var/lib/libvirt/images/virtio-win-0.1.173.iso But neither the path (/tmp/win-usb-fs.dos), the device (sdb), nor the alias (usb-disk1) works, the error message is always the same. Happened with libvirt-clients=5.6.0-2 also, the upgrade didn't help. Thanks! -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.4.0-4-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_WARN Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8), LANGUAGE=de_AT:de (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libvirt-clients depends on: ii libc6 2.30-2 ii libgcc-s1 10-20200312-2 ii libglib2.0-0 2.64.1-1 ii libreadline8 8.0-4 ii libvirt0 6.0.0-4 ii libxml2 2.9.10+dfsg-4 ii sensible-utils 0.0.12+nmu1 libvirt-clients recommends no packages. Versions of packages libvirt-clients suggests: ii libvirt-daemon 6.0.0-4 -- no debconf information --