From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Fitzhardinge Subject: Re: Which disk backend to use in domU? Date: Mon, 14 Jun 2010 11:49:45 +0100 Message-ID: <4C160949.7050007@goop.org> References: <1382341628.4833695.1276117331660.JavaMail.root@vms170009.mailsrvcs.net> <1742609046.4840453.1276126053830.JavaMail.root@vms170009.mailsrvcs.net> <4C1025C0.2070808@goop.org> <28857720.post@talk.nabble.com> <4C127584.6070801@dataproof.fi> <4C12781A.7060603@dataproof.fi> <28858517.post@talk.nabble.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <28858517.post@talk.nabble.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Neobiker Cc: xen-devel@lists.xensource.com, Daniel Stodden List-Id: xen-devel@lists.xenproject.org On 06/11/2010 07:11 PM, Neobiker wrote: > Hi > > Valtteri Kiviniemi-2 wrote: > >> Hi, Ah, misunderstanding sorry, you were talking about disk images :) >> >> > I'm talking about this config: > disk = [ > 'phy:/dev/vm/vm01,xvda1,w', > 'phy:/dev/vm/vm01-swap,xvda2,w', > 'phy:/dev/daten/devel_debian_amd64,xvda3,w', > ] > file: is definitely unsafe; its IO gets buffered in the dom0 pagecache, which means the guests writes aren't really writes. I believe phy: has similar problems, whereas tap:aio: implemented direct IO. But someone more storagey can confirm. J