RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1078809 - can not boot qemu-kvm-rhev with rbd image
Summary: can not boot qemu-kvm-rhev with rbd image
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: qemu-kvm
Version: 7.0
Hardware: x86_64
OS: Linux
urgent
urgent
Target Milestone: rc
: ---
Assignee: Kevin Wolf
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks: 1080820
TreeView+ depends on / blocked
 
Reported: 2014-03-20 10:45 UTC by Jun Li
Modified: 2014-07-25 10:34 UTC (History)
12 users (show)

Fixed In Version: qemu-kvm-rhev-1.5.3-56.el7
Doc Type: Bug Fix
Doc Text:
Previously, qemu-kvm-rhev failed to boot with rbd image, and returned an "Unknown Protocol" error. Now, the rbd driver is compiled in qemu-kvm-rhev, and an unsuccessful boot produces more meaningful error messages.
Clone Of:
Environment:
Last Closed: 2014-06-13 09:26:02 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2014:0985 0 normal SHIPPED_LIVE qemu-kvm bug fix and enhancement update 2014-07-29 23:34:16 UTC

Description Jun Li 2014-03-20 10:45:36 UTC 
Description of problem:
Currently, qemu-kvm should not support rbd; qemu-kvm-rhev should support rbd.
When boot qemu-kvm-rhev with rbd, got the "Unknown protocol" error.

Version-Release number of selected component (if applicable):
qemu-kvm-rhev-1.5.3-52.el7.x86_64

How reproducible:
100%

Steps to Reproduce:
1.boot qemu-kvm-rhev with rbd as following cli:
# /usr/libexec/qemu-kvm -drive file=rbd:10.66.7.1:6789/win8.1-juli.qcow2,if=none,id=img -device virtio-blk-pci,drive=img,id=sys-img -monitor stdio
2.
3.

Actual results:
After step 1:
# /usr/libexec/qemu-kvm -drive file=rbd:10.66.7.1:6789/win8.1-juli.qcow2,if=none,id=img -device virtio-blk-pci,drive=img,id=sys-img -monitor stdio
qemu-kvm: -drive file=rbd:10.66.7.1:6789/win8.1-juli.qcow2,if=none,id=img: could not open disk image rbd:10.66.7.1:6789/win8.1-juli.qcow2: Unknown protocol

Expected results:
can boot successfully. Or if can not connect the rbd server, please give some friendly hint.

Additional info:
Also test with gluster server, when can not connect the server, it will print "Gluster connection failed".
# /usr/libexec/qemu-kvm -drive file=gluster://10.66.4.2:24009/gv0/win8.1-juli.raw,if=none,id=img -device virtio-blk-pci,drive=img,id=sys-img -monitor stdio
qemu-kvm: -drive file=gluster://10.66.4.2:24009/gv0/win8.1-juli.raw,if=none,id=img: Gluster connection failed for server=10.66.4.2 port=24009 volume=gv0 image=win8.1-juli.raw transport=tcp
Comment 1 juzhang 2014-03-20 10:52:31 UTC 
This bz might block Bug 989608 - [7.0 FEAT] qemu runtime support for librbd backend (ceph)
Comment 2 Kevin Wolf 2014-03-20 10:54:49 UTC 
Confirmed, due to bugs in the configure script, the rbd block driver isn't
actually compiled in, even though it was requested on the command line.

Please give this package a try:
http://brewweb.devel.redhat.com/brew/taskinfo?taskID=7230126
Comment 3 Kevin Wolf 2014-03-20 11:16:42 UTC 
(In reply to Kevin Wolf from comment #2)
> Please give this package a try:
> http://brewweb.devel.redhat.com/brew/taskinfo?taskID=7230126

Sorry, that was a RHEL build that doesn't contain the rbd driver anyway. This
one is the same code built for RHEV that should work with rbd:

https://brewweb.devel.redhat.com/taskinfo?taskID=7230222
Comment 5 Jun Li 2014-03-21 01:47:57 UTC 
(In reply to Kevin Wolf from comment #3)
> (In reply to Kevin Wolf from comment #2)
> > Please give this package a try:
> > http://brewweb.devel.redhat.com/brew/taskinfo?taskID=7230126
> 
> Sorry, that was a RHEL build that doesn't contain the rbd driver anyway. This
> one is the same code built for RHEV that should work with rbd:
> 
> https://brewweb.devel.redhat.com/taskinfo?taskID=7230222
Test with build url:
https://brewweb.devel.redhat.com/taskinfo?taskID=7230222

The following is the results:
# /usr/libexec/qemu-kvm -drive file=rbd:10.66.7.1:6789/win8.1-juli.qcow2,if=none,id=img -device virtio-blk-pci,drive=img,id=sys-img -monitor stdio
no monitors specified to connect to.
qemu-kvm: -drive file=rbd:10.66.7.1:6789/win8.1-juli.qcow2,if=none,id=img: error connecting
qemu-kvm: -drive file=rbd:10.66.7.1:6789/win8.1-juli.qcow2,if=none,id=img: could not open disk image rbd:10.66.7.1:6789/win8.1-juli.qcow2: Could not open 'rbd:10.66.7.1:6789/win8.1-juli.qcow2': No such file or directory
Comment 6 Jun Li 2014-03-21 02:00:30 UTC 
Also test with build url:
http://brewweb.devel.redhat.com/brew/taskinfo?taskID=7230126
---
The result is as followings:
# /usr/libexec/qemu-kvm -drive file=rbd:10.66.7.1:6789/win8.1-juli.qcow2,if=none,id=img -device virtio-blk-pci,drive=img,id=sys-img -monitor stdio
qemu-kvm: -drive file=rbd:10.66.7.1:6789/win8.1-juli.qcow2,if=none,id=img: could not open disk image rbd:10.66.7.1:6789/win8.1-juli.qcow2: Unknown protocol
Comment 7 juzhang 2014-03-21 02:28:32 UTC 
Hi Kevin,

QE both tried qemu-kvm-rhev and qemu-kvm build your provided. Qemu-kvm-rhev and qemu-kvm hit different errors. I think your build fix this issue.

If so, It is possible build the official qemu-kvm-rhev quickly? I guess Intank might need fixed build for verifying Bug 989608 - [7.0 FEAT] qemu runtime support for librbd backend (ceph).

Best Regards,
Junyi
Comment 8 Miroslav Rezanina 2014-03-21 06:39:03 UTC 
Fix included in qemu-kvm-1.5.3-56.el7
Comment 9 juzhang 2014-03-21 06:56:25 UTC 
(In reply to juzhang from comment #7)
> Hi Kevin,
> 
> QE both tried qemu-kvm-rhev and qemu-kvm build your provided. Qemu-kvm-rhev
> and qemu-kvm hit different errors. I think your build fix this issue.
> 
> If so, It is possible build the official qemu-kvm-rhev quickly? I guess
> Intank might need fixed build for verifying Bug 989608 - [7.0 FEAT] qemu
> runtime support for librbd backend (ceph).
> 
> Best Regards,
> Junyi

Remove needinfo since qemu-kvm-1.5.3-56.el7 comes out with fixed patch.

Best Regards,
Junyi
Comment 10 Jun Li 2014-03-21 09:45:46 UTC 
Verify:
test with qemu-kvm-rhev:
qemu-kvm-rhev-1.5.3-56.el7ev.x86_64
---------
# /usr/libexec/qemu-kvm -drive file=rbd:10.66.7.1:6789/win8.1-juli.qcow2,if=none,id=img -device virtio-blk-pci,drive=img,id=sys-img -monitor stdio
no monitors specified to connect to.
qemu-kvm: -drive file=rbd:10.66.7.1:6789/win8.1-juli.qcow2,if=none,id=img: error connecting
qemu-kvm: -drive file=rbd:10.66.7.1:6789/win8.1-juli.qcow2,if=none,id=img: could not open disk image rbd:10.66.7.1:6789/win8.1-juli.qcow2: Could not open 'rbd:10.66.7.1:6789/win8.1-juli.qcow2': No such file or directory
---------------
test with qemu-kvm:
qemu-kvm-1.5.3-56.el7.x86_64
# /usr/libexec/qemu-kvm -drive file=rbd:10.66.7.1:6789/win8.1-juli.qcow2,if=none,id=img -device virtio-blk-pci,drive=img,id=sys-img -monitor stdio
qemu-kvm: -drive file=rbd:10.66.7.1:6789/win8.1-juli.qcow2,if=none,id=img: could not open disk image rbd:10.66.7.1:6789/win8.1-juli.qcow2: Unknown protocol
=======================
Before above test, should make sure /usr/lib64/librbd.so.1 is existing in host. 
If not, could got following results:
Also test with qemu-kvm-rhev-1.5.3-56.el7ev.x86_64 without librbd.so.1 .
# /usr/libexec/qemu-kvm -drive file=rbd:10.66.7.1:6789/win8.1-juli.qcow2,if=none,id=img -device virtio-blk-pci,drive=img,id=sys-img -monitor stdio
qemu-kvm: -drive file=rbd:10.66.7.1:6789/win8.1-juli.qcow2,if=none,id=img: error loading librbd: /usr/lib64/qemu/librbd.so.1: cannot open shared object file: No such file or directory
qemu-kvm: -drive file=rbd:10.66.7.1:6789/win8.1-juli.qcow2,if=none,id=img: could not open disk image rbd:10.66.7.1:6789/win8.1-juli.qcow2: Could not open 'rbd:10.66.7.1:6789/win8.1-juli.qcow2': Input/output error
------
Note:
download librbd.so.1 from url: http://ceph.com/rpm-emperor/
Comment 11 juzhang 2014-03-21 09:57:58 UTC 
According to comment10, set this issue as verified.

Please note, kvm qe focus on error message promoted since about fully ceph testing is changed by intank.

Best Regards,
Junyi
Comment 12 Ludek Smid 2014-06-13 09:26:02 UTC 
This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.
Comment 13 cristi falcas 2014-07-25 09:23:58 UTC 
It seems that with the latest packages this is happening again:


[root@xxxxxx ~(keystone_admin)]$ qemu-img create -f rbd rbd:images/new-libvirt-image 2G
qemu-img: rbd:images/new-libvirt-image: Unknown file format 'rbd'

[root@xxxxxxx ~(keystone_admin)]$ rpm -qa | grep qemu
qemu-kvm-1.5.3-60.el7.x86_64
qemu-img-1.5.3-60.el7.x86_64
ipxe-roms-qemu-20130517-5.gitc4bce43.el7.noarch
qemu-kvm-common-1.5.3-60.el7.x86_64
qemu-kvm-tools-1.5.3-60.el7.x86_64
Comment 14 cristi falcas 2014-07-25 09:26:29 UTC 
Also, does anyone know if I can still find anywhere the 1.5.3-56 version?
Comment 15 cristi falcas 2014-07-25 10:34:18 UTC 
Sorry, rereading the bug description I can see that the normal packages are not supposed to have rbd included. I recompiled the ev sources locally for this.

Thank you
Note You need to log in before you can comment on or make changes to this bug.