From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Campbell Subject: Re: [PATCH resend] libxl, hotplug/Linux: default to phy backend for raw format file, take 2 Date: Mon, 12 Jan 2015 09:31:46 +0000 Message-ID: <1421055106.26317.0.camel@citrix.com> References: <1420724813-17920-1-git-send-email-wei.liu2@citrix.com> <54AE952D.70304@m2r.biz> <20150109144233.GB32179@zion.uk.xensource.com> <1420825136.13270.45.camel@Abyss.station> <54B3909D.1040102@m2r.biz> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <54B3909D.1040102@m2r.biz> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Fabio Fantoni Cc: Wei Liu , Stefano Stabellini , Dario Faggioli , Ian Jackson , xen-devel@lists.xen.org, Roger Pau =?ISO-8859-1?Q?Monn=E9?= List-Id: xen-devel@lists.xenproject.org On Mon, 2015-01-12 at 10:15 +0100, Fabio Fantoni wrote: > In the meantime, I saw this: > http://lists.xen.org/archives/html/xen-users/2015-01/msg00047.html > Based on the post above seems that phy will have important risk of data > loss if I understand good, from Ian Campbell post: > > xl also uses qdisk for raw disk images instead of loop+blkback which > > xend used, because there are concerns that the loop driver can lead to > > data loss (by not implementing direct i/o the underlying device, and/or > > not handling flushes correct, my memory is a bit fuzzy). Stefano already corrected me on this in this very thread. Ian.