** Also affects: cloud-archive
Importance: Undecided
Status: New
** Changed in: cloud-archive
Status: New => Fix Released
** Changed in: cloud-archive
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
This bug was fixed in the package libvirt - 1.2.16-2ubuntu10
---
libvirt (1.2.16-2ubuntu10) wily; urgency=medium
* Add qemu-block-extra libraries to libvirt apparmor profile (LP:
#1495895)
-- Ryan Harper Wed, 16 Sep 2015 13:20:48
-0500
** Changed in: libvirt (Ubuntu)
Sta
This bug was fixed in the package qemu - 1:2.3+dfsg-5ubuntu6
---
qemu (1:2.3+dfsg-5ubuntu6) wily; urgency=medium
* Make qemu-system-common and qemu-utils depend on qemu-block-extra
to fix errors with missing block backends. (LP: #1495895)
* Cherry pick fixes for vmdk stream-op
Martin
Re the qemu changes; the issue will be for upgrades - for example, in
vivid, the qemu binaries include rbd support - however an upgrade and
reboot to wily with the situation as it is now (or even with
Recommends/Suggests) would result in instances which cannot access block
devices that they
Can you please clarify the status here for sponsoring?
qemu_system_common_depend_on_qemu_block_extra.debdiff seems a bit harsh
-- the whole point of splitting out a separate binary is that you
*don't* have to have it installed all the time, no? So maybe a
Recommends: or Suggests:? But AFAIUI this i
debdiff includes an updated apparmor profile for libvirt-qemu for
libraries provided by qemu-block-extra
** Patch added: "libvirt_qemu_block_extra_apparmor_update.debdiff"
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1495895/+attachment/4466889/+files/libvirt_qemu_block_extra_apparmor_u
This bug requires a fix to libvirt's apparmor profile as well.
** Also affects: libvirt (Ubuntu)
Importance: Undecided
Status: New
** Changed in: libvirt (Ubuntu)
Importance: Undecided => High
** Changed in: libvirt (Ubuntu)
Status: New => Confirmed
** Changed in: qemu (Ubun
OK, updating the libvirt-qemu apparmor abstraction resolves this issue:
# diff -u libvirt-qemu.orig libvirt-qemu
--- libvirt-qemu.orig 2015-09-16 18:14:46.013741000 +
+++ libvirt-qemu2015-09-16 18:14:34.001741000 +
@@ -144,6 +144,10 @@
# for rbd
/etc/ceph/ceph.conf r,
+
Looks like parsing is all fine. I recreated the error by enabling debug
and seeing the qemu hmp command passed, then I launched my own instance
and surfaced the HMP monitor, when I repeated the drive_add command it
complained, unknown protocol rbd; this is the result of qemu being
launched by lib
it appears that qemu wants additional escaping of colons when specifying
the port in mon_host options.
mon_host=10.5.29.172\:6789fails to parse
mon_host=10.5.29.172\\:6789 parses correct.
Looking at why that changed (or if libvirt stopped adding additional
escaping...).
--
You received thi
Starting the debugging.
First, we must have qemu-block-extra. After adding that we can check
that qemu itself supports rbd with:
qemu-system-x86_64 -drive format=? 2>&1 | grep rbd
Next, we see libvirt barfing on the missing block device it tried to add
and spits out the disk it was going to use
I think there is something else going on; clearly qemu-block-extra is
needed if you're attempting to connect to an rbd device. For example
we can attempt to connect to an rbd pool with path data/wily. I don't
actually have an rbd pool up. If qemu doesn't have block_rbd from qemu-
block-extra i
Do you have the libvirt log and the qemu command line used to run the
guest?
** Changed in: qemu (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/
I've tried installing qemu-block-extras, but I'm still seeing the same
error; I have tried restarting the instance (stop/start to ensure a new
qemu process is created) and restarting libvirt but no-go right now.
** Changed in: qemu (Ubuntu)
Status: Incomplete => New
--
You received this b
The attachment "qemu_system_common_depend_on_qemu_block_extra.debdiff"
seems to be a debdiff. The ubuntu-sponsors team has been subscribed to
the bug report so that they can review and hopefully sponsor the
debdiff. If the attachment isn't a patch, please remove the "patch"
flag from the attachme
Have qemu-system-common and qemu-utils depend on qemu-block-extra
otherwise the packaging change changes expected behavior; namely before
the packaging change users could install qemu-system-x86 (and others
arches) and expect to use curl or rbd as a qemu block backend. After
the packaging change u
Looks like the rbd driver has been broken out into a separate package[1]
qemu-block-extra
If you install that does that fix your issue?
1. qemu (1:2.2+dfsg-6exp) unstable; urgency=medium
Since Debian release 2.2+dfsg-6exp, a new package named qemu-block-extra
has been created and some les
we're definitely missing librbd linking in wily which was present
before. Looking at the build scripts, it it appears for linux-amd64 we
emit the enable-rbd, so the next question is why we didn't actually
compile and link against it.
** Changed in: qemu (Ubuntu)
Importance: Undecided => High
** Description changed:
Attaching rbd devices to libvirt/qemu managed instances currently fails
with:
2015-09-15 09:47:09.369+: 31908: error :
qemuMonitorJSONCheckError:381 : internal error: unable to execute QEMU
command 'device_add': Property 'virtio-blk-device.drive' can't find
19 matches
Mail list logo
