From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: Feedback and errors Date: Fri, 02 May 2008 18:02:33 +0300 Message-ID: <481B2D09.9080601@qumranet.com> References: <200804282258.08426.nadim@khemir.net> <481AF262.4080305@qumranet.com> <20080502144527.GH5681@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: nadim khemir , kvm-devel@lists.sourceforge.net, qemu-devel@nongnu.org To: "Daniel P. Berrange" Return-path: In-Reply-To: <20080502144527.GH5681@redhat.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: kvm-devel-bounces@lists.sourceforge.net Errors-To: kvm-devel-bounces@lists.sourceforge.net List-Id: kvm.vger.kernel.org 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. ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone