[Pkg-libvirt-maintainers] Bug#991564: libvirt-daemon: USB cdrom removable=on: drive property not set

chriz debian_bugs at valaskjalf.eu
Tue Jul 27 18:28:11 BST 2021


Package: libvirt-daemon
Version: 7.0.0-3
Severity: normal
X-Debbugs-Cc: debian_bug at valaskjalf.eu

Dear Maintainer,

when trying to add a USB CDROM drive which is empty, the VM doesn't
start anymore.
This is regardless if the removable check is set or not.

Error starting domain: internal error: qemu unexpectedly closed the
monitor: 2021-07-27T16:55:41.147567Z qemu-system-aarch64: -device
usb-storage,bus=usb.0,port=1,id=usb-disk1,removable=on: drive property
not set

Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/asyncjob.py", line 65, in
cb_wrapper
    callback(asyncjob, *args, **kwargs)
  File "/usr/share/virt-manager/virtManager/asyncjob.py", line 101, in tmpcb
    callback(*args, **kwargs)
  File "/usr/share/virt-manager/virtManager/object/libvirtobject.py",
line 57, in newfn
    ret = fn(self, *args, **kwargs)
  File "/usr/share/virt-manager/virtManager/object/domain.py", line
1329, in startup
    self._backend.create()
  File "/usr/lib/python3/dist-packages/libvirt.py", line 1353, in create
    raise libvirtError('virDomainCreate() failed')
libvirt.libvirtError: internal error: qemu unexpectedly closed the
monitor: 2021-07-27T16:55:41.147567Z qemu-system-aarch64: -device
usb-storage,bus=usb.0,port=1,id=usb-disk1,removable=on: drive property
not set


When adding an iso to the drive, the VM can normally be started.


I get this error from virt-manager, but when opening the configuration
with virsh, I can see the flag is properly added to the config:
        <disk type='file' device='cdrom'>
                <driver name='qemu' type='raw'/>
                <target dev='sdb' bus='usb' removable='on'/>
                <readonly/>
                <address type='usb' bus='0' port='1'/>
        </disk>
When unchecking the removable check, the config correctly shows
removable='off' accordingly.

I can't tell, when the bug appeared, because I have not been using a USB
cdrom so far.

virt-manager is from testing (version 1:3.2.0-3)

-- System Information:
Debian Release: 11.0
  APT prefers testing
  APT policy: (700, 'testing'), (550, 'unstable'), (500, 'testing-security')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-7-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en_GB
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libvirt-daemon depends on:
ii  libblkid1                   2.36.1-7
ii  libc6                       2.31-13
ii  libdevmapper1.02.1          2:1.02.175-2.1
ii  libgcc-s1                   10.2.1-6
ii  libglib2.0-0                2.66.8-1
ii  libnetcf1                   1:0.2.8-1.1
ii  libparted2                  3.4-1
ii  libpcap0.8                  1.10.0-2
ii  libpciaccess0               0.16-1
ii  libselinux1                 3.1-3
ii  libudev1                    247.3-6
ii  libvirt-daemon-driver-qemu  7.0.0-3
ii  libvirt0                    7.0.0-3
ii  libxml2                     2.9.10+dfsg-6.7

Versions of packages libvirt-daemon recommends:
ii  libvirt-daemon-driver-lxc   7.0.0-3
ii  libvirt-daemon-driver-vbox  7.0.0-3
ii  libvirt-daemon-driver-xen   7.0.0-3
ii  libxml2-utils               2.9.10+dfsg-6.7
ii  netcat-openbsd              1.217-3
ii  qemu-system                 1:5.2+dfsg-11
ii  qemu-system-x86 [qemu-kvm]  1:5.2+dfsg-11

Versions of packages libvirt-daemon suggests:
pn  libvirt-daemon-driver-storage-gluster       <none>
pn  libvirt-daemon-driver-storage-iscsi-direct  <none>
pn  libvirt-daemon-driver-storage-rbd           <none>
pn  libvirt-daemon-driver-storage-zfs           <none>
ii  libvirt-daemon-system                       7.0.0-3
pn  numad                                       <none>

-- no debconf information



More information about the Pkg-libvirt-maintainers mailing list