qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jamie Lokier <jamie@shareable.org>
To: "Daniel P. Berrange" <berrange@redhat.com>, qemu-devel@nongnu.org
Cc: nadim khemir <nadim@khemir.net>, kvm-devel@lists.sourceforge.net
Subject: Re: [Qemu-devel] Re: [kvm-devel] Feedback and errors
Date: Fri, 2 May 2008 16:23:01 +0100	[thread overview]
Message-ID: <20080502152301.GA30679@shareable.org> (raw)
In-Reply-To: <20080502144527.GH5681@redhat.com>

Daniel P. Berrange wrote:
> > > 2/ two instances of kvm can be passed the same -hda. There is no locking 
> > > whatsoever. This messes up things seriously.
> 
> That depends entirely on what you are doing with the disk in the guest OS.
> 
> The disk could be hosting a cluster filesystem. The guest OS could be
> running on a read-only root FS. The disk could be application raw data
> storage which can be shared (eg Oracle RAC). 

That reminds me, a "read-only" option for disk images would be handy
occasionally.  Writes would return errors, rather than to an expanding
snapshot file.

And then, logically, any default locking for disk images (if you don't
disable it) would use shared locking for a read-only disk image.

> > These two are upstream qemu problems. Copying qemu-devel.
> > 
> > I guess using file locking by default would improve the situation, and 
> > we can add a -drive ...,exclusive=no option for people playing with 
> > cluster filesystems.
> 
> Turning on file locking by default will break existing apps / deployments
> using shared disks. IMHO this is a policy decision that should be solved 
> at ahigher level in the management stack where a whole world view is 
> available rather than QEMU which only knows about its own VM & host.

Imho disk locking should be on by default and easy to turn off.

Casual small scale use of QEMU doesn't use a "management stack", it
uses the command line directly invoking qemu or kvm, or a one-line
script.  In that scenario locking against running two instances _by
mistake_ is most useful (it's easy to accidentally forget you have one
running when hidden on the desktop), and least likely for someone to
use a wrapper.

The few cluster deployments using shared disks will notice very
quickly that an additional option is needed for the new QEMU version.
It won't be the first time a new version has required a change to the
command line options to keep an existing deployment working.

-- Jamie

      parent reply	other threads:[~2008-05-02 15:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200804282258.08426.nadim@khemir.net>
2008-05-02 10:52 ` [Qemu-devel] Re: [kvm-devel] Feedback and errors Avi Kivity
2008-05-02 14:32   ` Anthony Liguori
2008-05-02 15:00     ` Avi Kivity
2008-05-02 15:21       ` Anthony Liguori
2008-05-04 11:19         ` Avi Kivity
2008-05-04 22:52           ` nadim khemir
2008-05-04 12:39         ` Javier Guerra Giraldez
2008-05-02 14:45   ` Daniel P. Berrange
2008-05-02 15:02     ` Avi Kivity
2008-05-02 15:23     ` Jamie Lokier [this message]

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=20080502152301.GA30679@shareable.org \
    --to=jamie@shareable.org \
    --cc=berrange@redhat.com \
    --cc=kvm-devel@lists.sourceforge.net \
    --cc=nadim@khemir.net \
    --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).