From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Jackson Subject: Re: [PATCH v5 6/8] libxl: introduce libxl__alloc_vdev Date: Fri, 4 May 2012 18:16:17 +0100 Message-ID: <20388.3809.683062.947217@mariner.uk.xensource.com> References: <1336130000-27261-6-git-send-email-stefano.stabellini@eu.citrix.com> <1336143599.7535.17.camel@zakaz.uk.xensource.com> <20388.2028.216374.311465@mariner.uk.xensource.com> <1336151303.3735.3.camel@dagon.hellion.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1336151303.3735.3.camel@dagon.hellion.org.uk> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Ian Campbell Cc: "xen-devel@lists.xensource.com" , Stefano Stabellini List-Id: xen-devel@lists.xenproject.org Ian Campbell writes ("Re: [PATCH v5 6/8] libxl: introduce libxl__alloc_vdev"): > Right. I think I really should have made this comment on the previous > patch, What I was trying to suggest is that using the Linux specific > "xvda" in the example in the config file "xvda" is not currently thought to be necessarily Linux-specific. See docs/misc/vbd-interface.text. Perhaps that needs to be revisited, but in general it's perfectly possible to pass "xvda" in a domain config file for a BSD guest, or whatever. And Linux writing "xvdfoo" in the config file doesn't always make Linux call the device /dev/xvdfoo. Ian.