All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Graf <agraf@suse.de>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: [et-mgmt-tools] Image Corruption Possible with qemu and qemu-kvm
Date: Wed, 29 Aug 2007 17:23:49 +0200	[thread overview]
Message-ID: <46D58F85.60104@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0708291557580.24091@localhost.localdomain>

Paul Jakma wrote:
> On Mon, 27 Aug 2007, Anthony Liguori wrote:
>
>> I think this is the right level myself.  Advisory locks work okay but
>> not all filesystems support them.  It's particularly nasty when you have
>> a clustered filesystem in the host.  I think it would do more harm than
>> good to have a feature like that was supposed to provide a safe-guard
>> but then frequently didn't work.
>                ^^^^^^^^^^^^^^^^^^^^^^
>
> Are you trying to say that any kind of significant portion of QEMU
> users have clustered file-systems?
>
> I think that's unlikely, and it'd be nice if QEMU by default did a
> fcntl() on writeable image files to lock itself from multiple access,
> that'd benefit the vast majority of users.
>
> Let the 0.x% of users who need to run with weird/esoteric fses cope..
>
> regards,
I'm usually running one "main" qemu instance that has read/write access
to the disk file and several others for tests that use the -snapshot
option, so I think it's very important to have an easy means of
switching this check off.

just my 2 cents,

Alexander Graf

  reply	other threads:[~2007-08-29 15:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <46D2EC13.8020005@bppiac.hu>
     [not found] ` <1188232650.25884.100.camel@localhost.localdomain>
     [not found]   ` <OFCAE928CF.4933C4AF-ONC1257344.006B3E8C-C1257344.006BB8A7@de.ibm.com>
2007-08-27 20:19     ` [Qemu-devel] Re: [et-mgmt-tools] Image Corruption Possible with qemu and qemu-kvm Sven Oehme
2007-08-27 20:27       ` Daniel P. Berrange
2007-08-27 20:37         ` Avi Kivity
2007-08-27 21:02         ` Anthony Liguori
2007-08-27 21:26           ` Daniel Veillard
2007-08-28  2:13           ` Avi Kivity
2007-08-29 12:44             ` Sven Oehme
2007-08-29 14:58           ` Paul Jakma
2007-08-29 15:23             ` Alexander Graf [this message]
2007-08-29 15:44               ` Paul Jakma
2007-09-01 15:23               ` Chris Wilson

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=46D58F85.60104@suse.de \
    --to=agraf@suse.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 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.