Bug 1095666 - [RFE] Support read only VirtIO-SCSI direct LUNs in oVirt
Summary: [RFE] Support read only VirtIO-SCSI direct LUNs in oVirt
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: RFEs
Version: ---
Hardware: Unspecified
OS: Unspecified
low
medium
Target Milestone: ---
: ---
Assignee: shani
QA Contact: Avihai
URL:
Whiteboard:
Depends On: 995415 1082673 1095663 1097754 1110396
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-05-08 10:28 UTC by Allon Mureinik
Modified: 2020-04-01 14:51 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2020-04-01 14:48:34 UTC
oVirt Team: Storage
Embargoed:
ylavi: ovirt-4.3?
ylavi: planning_ack?
ylavi: devel_ack?
ylavi: testing_ack?

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1539837 0 high CLOSED [RFE][tracker][Cinder] - Improve integration and support with storage using cinderlib 2022-04-24 19:47:51 UTC

Internal Links: 1539837

Description Allon Mureinik 2014-05-08 10:28:14 UTC 
Description of problem:
The described configuration, read only VirtIO-SCSI direct LUNs, is currently not supported by QEMU.
It was disabled as response to bug 1082673, and bug 1095663 was opened on QEMU to track adding this support.
Once it's supported, oVirt should consume this new QEMU version, and allow using such a configuration (essentially, reverting the fix for bug 1082673).

Version-Release number of selected component (if applicable):
3.4.0
Comment 1 Sandro Bonazzola 2015-09-04 09:02:25 UTC 
This is an automated message.
This Bugzilla report has been opened on a version which is not maintained anymore.
Please check if this bug is still relevant in oVirt 3.5.4.
If it's not relevant anymore, please close it (you may use EOL or CURRENT RELEASE resolution)
If it's an RFE please update the version to 4.0 if still relevant.
Comment 3 Yaniv Lavi 2016-12-14 16:18:57 UTC 
This bug had requires_doc_text flag, yet no documentation text was provided. Please add the documentation text and only then set this flag.
Comment 4 Yaniv Kaul 2017-06-20 09:16:13 UTC 
The qemu-kvm bug, https://bugzilla.redhat.com/show_bug.cgi?id=995415 was fixed in 7.3. 
We can remove the limitation introduced in https://bugzilla.redhat.com/show_bug.cgi?id=1082673 now?
Comment 5 Allon Mureinik 2017-06-20 09:52:03 UTC 
(In reply to Yaniv Kaul from comment #4)
> The qemu-kvm bug, https://bugzilla.redhat.com/show_bug.cgi?id=995415 was
> fixed in 7.3. 
> We can remove the limitation introduced in
> https://bugzilla.redhat.com/show_bug.cgi?id=1082673 now?

Yes, but only in versions that strictly require qemu-kvm[-[rh]ev]>=2.5 - i.e., in 4.1 clusters and above.
Comment 7 Red Hat Bugzilla Rules Engine 2018-05-16 10:55:04 UTC 
This request has been proposed for two releases. This is invalid flag usage. The ovirt-future release flag has been cleared. If you wish to change the release flag, you must clear one release flag and then set the other release flag to ?.
Comment 8 Sandro Bonazzola 2019-01-28 09:44:14 UTC 
This bug has not been marked as blocker for oVirt 4.3.0.
Since we are releasing it tomorrow, January 29th, this bug has been re-targeted to 4.3.1.
Comment 9 Michal Skrivanek 2020-03-18 15:49:44 UTC 
This bug didn't get any attention for a while, we didn't have the capacity to make any progress. If you deeply care about it or want to work on it please assign/target accordingly
Comment 10 Michal Skrivanek 2020-03-18 15:52:22 UTC 
This bug didn't get any attention for a while, we didn't have the capacity to make any progress. If you deeply care about it or want to work on it please assign/target accordingly
Comment 11 Michal Skrivanek 2020-04-01 14:48:34 UTC 
ok, closing. Please reopen if still relevant/you want to work on it.
Comment 12 Michal Skrivanek 2020-04-01 14:51:41 UTC 
ok, closing. Please reopen if still relevant/you want to work on it.
Note You need to log in before you can comment on or make changes to this bug.