Bug 537163
Summary: | QEMU has no means to request a read-only disk with -drive | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Daniel Berrangé <berrange> |
Component: | qemu | Assignee: | Justin M. Forbes <jforbes> |
Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 12 | CC: | adamplumb, berrange, clalance, crobinso, dave, dwalsh, dwmw2, gcosta, itamar, jaswinder, jforbes, ken, k.georgiou, loganjerry, markmc, mgrepl, pal666, quintela, robatino, veillard, virt-maint, ziaro40 |
Target Milestone: | --- | Keywords: | Triaged |
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | setroubleshoot_trace_hash:6e45b905c83145aab17ee23fcd5b81e4c5d803fa44e195edba55c2a4a7d00624 | ||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2010-12-04 03:21:44 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 536760 |
Description
Daniel Berrangé
2009-11-12 17:25:42 UTC
Um, Dan - could you provide some more info on exactly what you need done on the qemu side? Upstream commit 59f2689d introduces a readonly option for -drive. Is this what you're looking for? (Though I haven't checked if it really works as expected) The core requirement is that we have a 'readonly' flag for -drive, and when that is given, QEMU must *never* open a file with O_WRONLY or O_RDWR, it must only use O_RDONLY. Any attempt to open it for write will trigger this SELinux violation. Optionally it can set some flag against that drive such that the guest sees that it is read only, but that's merely a nice-to-have. It looks like 59f2689d should satisfy that, but will need to test it to be sure *** Bug 532478 has been marked as a duplicate of this bug. *** *** Bug 543105 has been marked as a duplicate of this bug. *** *** Bug 543117 has been marked as a duplicate of this bug. *** *** Bug 549502 has been marked as a duplicate of this bug. *** This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component. This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '12'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 12's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 12 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. |