Attaching RBD device after qemu upgrade fails with "Unknown protocol 'rbd'"
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
qemu (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bionic |
Confirmed
|
Medium
|
Unassigned |
Bug Description
After upgrading the following QEMU packages to latest Bionic version (1:2.11+
- qemu-system-x86
- qemu-system-common
- qemu-utils
- qemu-block-
Attaching an RBD device to a VM that was running prior to the upgrade fails with
"Unknown protocol 'rbd'
This only happens if this is the first RBD device to be attached after the upgrade. Attaching a device, then upgrading to 1:2.11+
Attaching a device to a new VM created _AFTER_ the upgrade does not trigger the problem either.
Downgrading qemu-block-
Here are two examples :
Using :
ii qemu-block-
ii qemu-system-common 1:2.11+
ii qemu-system-x86 1:2.11+
ii qemu-utils 1:2.11+
./qmp-shell -H /opt/vms/1/qmp.sock
(QEMU) drive_add auto format=
OK
With :
ii qemu-block-
ii qemu-system-common 1:2.11+
ii qemu-system-x86 1:2.11+
ii qemu-utils 1:2.11+
and an existing QEMU process running
$ apt udpate && apt -y install qemu-utils qemu-system-x86 qemu-system-common qemu-block-
Using :
ii qemu-block-
ii qemu-system-common 1:2.11+
ii qemu-system-x86 1:2.11+
ii qemu-utils 1:2.11+
./qmp-shell -H /opt/vms/1/qmp.sock
(QEMU) drive_add auto format=
Unknown protocol 'rbd'
(QEMU)
Restarting the QEMU process fixes the issue.
Changed in qemu (Ubuntu Bionic): | |
status: | New → Confirmed |
importance: | Undecided → Medium |
description: | updated |
Hi Louis,
this is a known, but complex and probably very (very) long running issue.
I recently discussed it on the KVM Forum and we had a mail thread about it.
Read the full background on bug 1847361 - I'll mark this as a dup.