From mboxrd@z Thu Jan 1 00:00:00 1970 From: Boris Ostrovsky Subject: Re: [PATCH] libxl: No emulated disk driver for xvdX disk Date: Tue, 27 Oct 2015 09:25:52 -0400 Message-ID: <562F7B60.9040506@oracle.com> References: <1444820717-25565-1-git-send-email-anthony.perard@citrix.com> <22049.834.580885.592862@mariner.uk.xensource.com> <562EA0EF.8050808@oracle.com> <22063.31205.869213.960160@mariner.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <22063.31205.869213.960160@mariner.uk.xensource.com> 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 Jackson , George Dunlap Cc: Anthony PERARD , "xen-devel@lists.xen.org" , Wei Liu , Ian Campbell , Stefano Stabellini List-Id: xen-devel@lists.xenproject.org On 10/27/2015 09:19 AM, Ian Jackson wrote: > George Dunlap writes ("Re: [Xen-devel] [PATCH] libxl: No emulated disk driver for xvdX disk"): >> On Tue, Oct 27, 2015 at 11:11 AM, Stefano Stabellini >> wrote: >>> The guest can access xvdX disks via the PV block protocol, or via >>> UEFI firmare using EFI BootServices. >> But it introduces a sort of regression in some setups -- namely, >> before you could use exactly the same disk and config file for either >> a PV or HVM guest, simply adding builder=hvm (either to the file or >> the command line) to switch between the two. > The purpose of the `vdev' in the xl disk specification is to say how > the disk should be presented to the guest. > > Did you look at docs/misc/vbd-interface.txt ? > > If you want something that is accessible via the BIOS etc. in HVM > guests, why not use vdev=hda rather than vdev=xvda ? Yes, but since we've discovered that people do use xvda (and have been doing this for long time --- our test framework has been running for many years configured like that) --- do we want this to suddenly break? -boris