From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kamala Narasimhan Subject: Re: [PATCH] xl: Special case tap/aio for disk validation Date: Thu, 27 Jan 2011 12:43:37 -0500 Message-ID: <4D41AEC9.10302@gmail.com> References: <4D407A06.1050902@gmail.com> <19777.36262.691401.791181@mariner.uk.xensource.com> <1296142527.14780.6892.camel@zakaz.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1296142527.14780.6892.camel@zakaz.uk.xensource.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: Ian Campbell Cc: Stefano Stabellini , "xen-devel@lists.xensource.com" , Ian Jackson , "Kamala Narasimhan (3P)" List-Id: xen-devel@lists.xenproject.org > Shall we pre-deprecate the someprefix: along with all the > tap:{aio,ioemu,FOO}: stuff while we are at this? IOW the syntax we want > to actually support going forward would be: > (raw|vhd|qcow2|qcow):/path/to/something > with the toolstack being at liberty to best decide how to achieve the > necessary format support? (optionally raw: as the default). All the rest > of the format is really semantically meaningless and supported only for > compatibility with existing configuration files. > That sure does simply things! When we have multiple backends that work with different file formats for users to choose from, we can revisit this. Kamala > Ian. > > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel