qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jamie Lokier <jamie@shareable.org>
To: Avi Kivity <avi@redhat.com>
Cc: Christoph Hellwig <hch@lst.de>, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Regression opening read-only cdroms
Date: Tue, 16 Jun 2009 18:51:12 +0100	[thread overview]
Message-ID: <20090616175112.GB11893@shareable.org> (raw)
In-Reply-To: <4A37C58C.3000003@redhat.com>

Avi Kivity wrote:
> On 06/16/2009 06:54 PM, Jamie Lokier wrote:
> >read-only disk images don't make much sense.
> >   
> >
> >And yet "chmod 444 image; qemu ..." works.
> >If you're booting from a disk you don't need to write to, obviously.
> >Generally it'll need to be mounted read-only in the guest.
> >   
> 
> It will eventually fail.  Open the ext3 log, update atime, or 
> something.  The guest expects the disk to be writeable.

No.  Obviously if you _want_ to run a guest with the disk mounted
writable, you'll use snapshot=on instead because that's what it's for.

Otherwise, a read-only disk should works fine using virtio/SCSI/USB,
as the guest will mount it read-only, as those interfaces all have a
read-only media flag which Linux guests (at least) look at.

Which is the desired behaviour.

-- Jamie

  reply	other threads:[~2009-06-16 17:51 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-16 12:00 [Qemu-devel] Regression opening read-only cdroms Avi Kivity
2009-06-16 14:33 ` Jamie Lokier
2009-06-16 14:54   ` Stefano Stabellini
2009-06-16 14:54     ` Jamie Lokier
2009-06-16 16:28       ` Anthony Liguori
2009-06-16 17:14         ` Stefano Stabellini
2009-06-16 17:46           ` Jamie Lokier
2009-06-16 17:54             ` Avi Kivity
2009-06-16 18:56               ` Jamie Lokier
2009-06-16 19:02                 ` Jamie Lokier
2009-06-16 21:11         ` Gerd Hoffmann
2009-06-17  6:27           ` Avi Kivity
2009-06-16 15:16   ` Avi Kivity
2009-06-16 15:54     ` Jamie Lokier
2009-06-16 16:17       ` Avi Kivity
2009-06-16 17:51         ` Jamie Lokier [this message]
2009-06-16 17:58           ` Avi Kivity
2009-06-18 12:37   ` Richard W.M. Jones
2009-06-24 20:23     ` Jamie Lokier
2009-06-24 22:43       ` Richard W.M. Jones
2009-06-25  0:50         ` Jamie Lokier
2009-06-25  8:17           ` Richard W.M. Jones
2009-06-16 16:28 ` Blue Swirl
2009-06-16 18:37   ` Blue Swirl
2009-06-16 21:16     ` Christoph Hellwig

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090616175112.GB11893@shareable.org \
    --to=jamie@shareable.org \
    --cc=avi@redhat.com \
    --cc=hch@lst.de \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).