From: Jamie Lokier <jamie@shareable.org>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Kevin Wolf <kwolf@redhat.com>, Naphtali Sprei <nsprei@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Add readonly flag to -drive command
Date: Mon, 12 Oct 2009 16:16:44 +0100 [thread overview]
Message-ID: <20091012151644.GE13560@shareable.org> (raw)
In-Reply-To: <4AD33D6D.9020900@codemonkey.ws>
Anthony Liguori wrote:
> 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.
I agree, that's ugly - I've wasted time on a strangely broken guest in
that situation too!
Backward compatibility might be an issue with the idea to change QEMU
to complain if it can't open a file writable. Not with regular disk
images so much, but floppy/USB images. Perhaps the answer to that is
'readonly=auto', 'readonly=yes', 'readonly=no'?
Sharing images with -snapshot, and backing images with qcow2, is a
very useful feature for launching multiple test VMs in parallel, and
for making "forked" images for testing different guest OS variations,
so I'm glad to see the 'readonly' flag appearing as an option.
(You can't use qcow2 snapshots to implement "forked" images running in
parallel because you can't safely open different snapshots in the same
qcow2 file at the same time).
Taking a read-only (shared) or writeable (exclusive) lock on the file
would be a useful addition I think, to catch mistakes.
-- Jamie
next prev parent reply other threads:[~2009-10-12 15:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-12 12:47 [Qemu-devel] [PATCH] Add readonly flag to -drive command Naphtali Sprei
2009-10-12 13:24 ` Kevin Wolf
2009-10-12 13:50 ` Jamie Lokier
2009-10-12 14:07 ` Kevin Wolf
2009-10-12 14:30 ` Anthony Liguori
2009-10-12 15:16 ` Jamie Lokier [this message]
2009-10-12 16:15 ` Michael Tokarev
2009-10-13 7:36 ` Kevin Wolf
2009-10-12 14:06 ` Anthony Liguori
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=20091012151644.GE13560@shareable.org \
--to=jamie@shareable.org \
--cc=anthony@codemonkey.ws \
--cc=kwolf@redhat.com \
--cc=nsprei@redhat.com \
--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).