Package: qemu-system-x86
Version: 1:5.2+dfsg-2
Severity: important

I have my VM images on individually encrypted LVs so that I can
individually lock and unlock VMs. This is what my block device looks
like:
[1/5386]mh@drop:~ $ ls -al /dev/mapper/centos 
lrwxrwxrwx 1 root root 8 Dez 19 15:47 /dev/mapper/centos -> ../dm-13
[2/5387]mh@drop:~ $ ls -al /dev/dm-13 
brw-rw---- 1 root root 254, 13 Dez 19 15:47 /dev/dm-13
[3/5388]mh@drop:~ $ 

When I create a storage device in virt-manager, this results in the
following XML:
    <disk type='file' device='disk'>
      <driver name='qemu' type='raw'/>
      <source file='/dev/mapper/centos' index='1'/>
      <backingStore/>
      <target dev='vda' bus='virtio'/>
      <alias name='virtio-disk0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x08' 
function='0x0'/>
    </disk>

This VM won't start any more with qemu 5.2, saying "Opening a block
device as a file using the file drive is deprecated". It unfortunately
doesn't give a hint how block devices are to be opened, and it looks
like libvirt/virt-manager don't know either.

I don't know whether this is a libvirt, a virt-manager or a qemu issue,
but it should be properly reassigned and fixed (and conflicts added (and
conflicts added). In the man time, going back to qemu 5.1 has fixed the
issue for me.

Greetings
Marc


-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.10.1-zgws1 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), LANGUAGE=en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages qemu-system-x86 depends on:
ii  ipxe-qemu             1.0.0+git-20190125.36a4c85-5
ii  libaio1               0.3.112-8
ii  libc6                 2.31-6
ii  libcapstone4          4.0.2-3
ii  libfdt1               1.6.0-1
ii  libgcc-s1             10.2.1-1
ii  libglib2.0-0          2.66.4-1
ii  libgnutls30           3.7.0-3
ii  libibverbs1           32.0-1+b1
ii  libjpeg62-turbo       1:2.0.5-1.1
ii  libnettle8            3.6-2
ii  libnuma1              2.0.12-1+b1
ii  libpixman-1-0         0.40.0-1
ii  libpmem1              1.10-1
ii  libpng16-16           1.6.37-3
ii  librdmacm1            32.0-1+b1
ii  libsasl2-2            2.1.27+dfsg-2
ii  libseccomp2           2.5.0-3+b1
ii  libslirp0             4.3.1-1
ii  libudev1              247.1-4
ii  liburing1             0.7-2
ii  libusb-1.0-0          2:1.0.24-2
ii  libvdeplug2           4.0.1-2
ii  libxendevicemodel1    4.14.0+88-g1d1d1f5391-2
ii  libxenevtchn1         4.14.0+88-g1d1d1f5391-2
ii  libxenforeignmemory1  4.14.0+88-g1d1d1f5391-2
ii  libxengnttab1         4.14.0+88-g1d1d1f5391-2
ii  libxenmisc4.14        4.14.0+88-g1d1d1f5391-2
ii  libxenstore3.0        4.14.0+88-g1d1d1f5391-2
ii  libxentoolcore1       4.14.0+88-g1d1d1f5391-2
ii  qemu-system-common    1:5.2+dfsg-2
ii  qemu-system-data      1:5.2+dfsg-2
ii  seabios               1.14.0-2
ii  zlib1g                1:1.2.11.dfsg-2

Versions of packages qemu-system-x86 recommends:
ii  ovmf             2020.11-2
pn  qemu-system-gui  <none>
ii  qemu-utils       1:5.2+dfsg-2

Versions of packages qemu-system-x86 suggests:
ii  qemu-block-extra            1:5.2+dfsg-2
ii  qemu-system-data [sgabios]  1:5.2+dfsg-2
pn  samba                       <none>
pn  vde2                        <none>

-- no debconf information

Reply via email to