Package: qemu-system-x86 Version: 2.1+dfsg-2~bpo70+2 Severity: important File: /usr/bin/qemu-system-i386
Dear Maintainer, I am planning to use KVM with VM virtual disks stored in a Ceph cluster, using wheezy-backports package. Ceph packages are present in wheezy-backports repository, so I don't understand why RBD support is systematicaly disabled as in changelog for version 2.1+dfsg-2~bpo70+2. Could you keep RBD support on future releases in wheezy-backports? Best regards, Alexis Lahouze. -- System Information: Debian Release: 7.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages qemu-system-x86 depends on: ii ipxe-qemu 1.0.0+git-20120202.f6840ba-3 ii libaio1 0.3.109-3 ii libasound2 1.0.25-4 ii libbluetooth3 4.99-2 ii libbrlapi0.5 4.4-10+deb7u1 ii libc6 2.13-38+deb7u3 ii libcurl3-gnutls 7.26.0-1+wheezy9 ii libfdt1 1.3.0-4 ii libgcc1 1:4.7.2-5 ii libglib2.0-0 2.33.12+really2.32.4-5 ii libgnutls26 2.12.20-8+deb7u2 ii libiscsi2 1.12.0-2~bpo70+1 ii libjpeg8 8d-1+deb7u1 ii libncurses5 5.9-10 ii libpixman-1-0 0.26.0-4+deb7u1 ii libpng12-0 1.2.49-1 ii libpulse0 4.0-6~bpo7+1 ii libsasl2-2 2.1.25.dfsg1-6+deb7u1 ii libsdl1.2debian 1.2.15-5 ii libspice-server1 0.12.4-0nocelt2~bpo70+1 ii libssh2-1 1.4.2-1.1 ii libtinfo5 5.9-10 ii libusb-1.0-0 2:1.0.19-1~bpo70+1 ii libusbredirparser1 0.6-2~bpo70+1 ii libuuid1 2.20.1-5.3 ii libvdeplug2 2.3.2-4 ii libx11-6 2:1.5.0-1+deb7u1 ii libxen-4.1 4.1.4-3+deb7u2 ii libxenstore3.0 4.1.4-3+deb7u2 ii qemu-system-common 2.1+dfsg-2~bpo70+2 ii seabios 1.7.5-1~bpo70+1 ii zlib1g 1:1.2.7.dfsg-13 Versions of packages qemu-system-x86 recommends: ii qemu-utils 2.1+dfsg-2~bpo70+2 Versions of packages qemu-system-x86 suggests: ii kmod 9-3 pn ovmf <none> pn samba <none> pn sgabios <none> ii vde2 2.3.2-4 -- no debconf information -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
