From: "Daniel P. Berrange" <berrange@redhat.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: RFC: Making QEMU honour 'readonly' flag for disks
Date: Thu, 24 Jul 2008 14:41:47 +0100 [thread overview]
Message-ID: <20080724134147.GC1138@redhat.com> (raw)
In-Reply-To: <18568.34189.57005.491667@mariner.uk.xensource.com>
On Thu, Jul 24, 2008 at 02:37:17PM +0100, Ian Jackson wrote:
> Daniel P. Berrange writes ("[Xen-devel] RFC: Making QEMU honour 'readonly' flag for disks"):
> > This proof of concept patch I've done against the RHEL-5 Xen tree introduces
> > a new 'drv_read_only' flag to QEMU's BlockDriverState struct, and if set to
> > non-zero, will cause the individual block backend drivers inside QEMU to
> > always open with O_RDONLY, and never try O_RDWR. Ultimately this would be
> > hooked up to the '-drive' parameter via a extra flag ',ro' in its args.
> > It then makes xenstore.c set this flag based on the 'mode' parameter for
> > the disk in xenstore.
>
> I think this is a good idea but you should discuss it with upstream to
> try to minimise the difference between the patch that goes into our
> tree and the one that goes into upstream.
Ok, I'll do a generic patch for upstream QEMU and then a xenstore integration
add on.
Daniel
--
|: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :|
|: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|
next prev parent reply other threads:[~2008-07-24 13:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-24 11:36 RFC: Making QEMU honour 'readonly' flag for disks Daniel P. Berrange
2008-07-24 13:37 ` Ian Jackson
2008-07-24 13:41 ` Daniel P. Berrange [this message]
2008-07-24 13:43 ` Ian Jackson
2008-07-30 9:01 ` Ian Jackson
2008-07-30 9:16 ` Daniel P. Berrange
2008-07-31 11:45 ` Daniel P. Berrange
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=20080724134147.GC1138@redhat.com \
--to=berrange@redhat.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=xen-devel@lists.xensource.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.