From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MxLuo-0005U7-Kb for qemu-devel@nongnu.org; Mon, 12 Oct 2009 10:30:22 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MxLuh-0005MF-5G for qemu-devel@nongnu.org; Mon, 12 Oct 2009 10:30:22 -0400 Received: from [199.232.76.173] (port=55321 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MxLug-0005Ly-Tn for qemu-devel@nongnu.org; Mon, 12 Oct 2009 10:30:14 -0400 Received: from mail-fx0-f214.google.com ([209.85.220.214]:54899) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MxLug-0007Lj-Hj for qemu-devel@nongnu.org; Mon, 12 Oct 2009 10:30:14 -0400 Received: by fxm10 with SMTP id 10so8126843fxm.8 for ; Mon, 12 Oct 2009 07:30:13 -0700 (PDT) Message-ID: <4AD33D6D.9020900@codemonkey.ws> Date: Mon, 12 Oct 2009 09:30:05 -0500 From: Anthony Liguori MIME-Version: 1.0 Subject: Re: [Qemu-devel] [PATCH] Add readonly flag to -drive command References: <4AD32550.8040901@redhat.com> <4AD32DF6.4050100@redhat.com> <20091012135032.GA13560@shareable.org> In-Reply-To: <20091012135032.GA13560@shareable.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Jamie Lokier Cc: Kevin Wolf , Naphtali Sprei , qemu-devel@nongnu.org Jamie Lokier wrote: > Kevin Wolf wrote: > >> Am 12.10.2009 14:47, schrieb Naphtali Sprei: >> >>> In order to safely share an image between guests (as read only drive), add a 'readonly' flag >>> to the -drive command (qemu command line and monitor). >>> > > Heh. I've been sharing images between guests for ages - using "chmod -r" :-) > Were it not for backwards compatibility, I would remove that and have it error out. I've had multiple people end up with strangely broken guests because they didn't realize the image was read only. >>> Still missing passing the read only attribute to the guest, where possible. I don't know which device types supports >>> read only, and don't know how to pass this information to guests. >>> > > This was discussed in a thread some months ago. You might look it up. > SCSI, USB, and floppy can pass the information to guests - see the > Linux kernel for how the flag is read. CD-ROMs are read-only already > of course. I don't know if virtio-blk can; if not, it would be good to > add it. > virtio-blk can support read-only images now. Regards, Anthony Liguori