[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] Re: [et-mgmt-tools] Image Corruption Possible with qemu

From: Alexander Graf
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
User-agent: Thunderbird (X11/20070613)

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 via email to

[Prev in Thread] Current Thread [Next in Thread]