From: Avi Kivity <avi@qumranet.com>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: nadim khemir <nadim@khemir.net>,
kvm-devel@lists.sourceforge.net, qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [kvm-devel] Feedback and errors
Date: Fri, 02 May 2008 18:02:33 +0300 [thread overview]
Message-ID: <481B2D09.9080601@qumranet.com> (raw)
In-Reply-To: <20080502144527.GH5681@redhat.com>
Daniel P. Berrange wrote:
>> 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.
>
Running a newer qemu with an older libvirt would pose a problem, yes.
But we shouldn't ignore unmanaged deployments.
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
next prev parent reply other threads:[~2008-05-02 15:02 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 [this message]
2008-05-02 15:23 ` Jamie Lokier
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=481B2D09.9080601@qumranet.com \
--to=avi@qumranet.com \
--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).