From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MGa3k-00082M-LW for qemu-devel@nongnu.org; Tue, 16 Jun 2009 10:54:48 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MGa3g-00081z-5i for qemu-devel@nongnu.org; Tue, 16 Jun 2009 10:54:48 -0400 Received: from [199.232.76.173] (port=39548 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MGa3g-00081v-0u for qemu-devel@nongnu.org; Tue, 16 Jun 2009 10:54:44 -0400 Received: from mail2.shareable.org ([80.68.89.115]:37596) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1MGa3f-000582-3i for qemu-devel@nongnu.org; Tue, 16 Jun 2009 10:54:43 -0400 Date: Tue, 16 Jun 2009 15:54:21 +0100 From: Jamie Lokier Subject: Re: [Qemu-devel] Regression opening read-only cdroms Message-ID: <20090616145421.GD29040@shareable.org> References: <4A37896C.8050208@redhat.com> <20090616143259.GA29040@shareable.org> <4A37B23F.6040604@eu.citrix.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4A37B23F.6040604@eu.citrix.com> List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Stefano Stabellini Cc: qemu-devel , Avi Kivity , Christoph Hellwig Stefano Stabellini wrote: > Jamie Lokier wrote: > > > Avi Kivity wrote: > >> qemu used to be quite happy opening read-only cdrom images, and I was > >> quite happy feeding kvm-autotest a library of read-only iso images. > > > > 1. While we're here, an _option_ to open an image read-only even when > > you have write permission would be useful, for those occasions when > > you want to boot from some valuable image and be certain you aren't > > modifying it - without having to chmod back and forth in > > Qemu-wrapper scripts, or copy the image first. > > > Indeed. > I have a patch that adds bdrv_set_read_only that set bs->read_only = 1 > so that bdrv_open2 can check if the flag is set and act accordingly. > The problem is that in xen we read whether the device should be opened > read only in the VM config file, I don't think the user can specify to > open a drive read-only in qemu. What's missing is a "ro" sub-option to "-drive". -- Jamie