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: Mon, 26 Oct 2015 17:53:51 -0400 Message-ID: <562EA0EF.8050808@oracle.com> References: <1444820717-25565-1-git-send-email-anthony.perard@citrix.com> <22049.834.580885.592862@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: <22049.834.580885.592862@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 , Anthony PERARD Cc: xen-devel@lists.xen.org, Wei Liu , Ian Campbell , Stefano Stabellini List-Id: xen-devel@lists.xenproject.org On 10/16/2015 10:01 AM, Ian Jackson wrote: > Anthony PERARD writes ("[PATCH] libxl: No emulated disk driver for xvdX disk"): >> When a guest configuration list xvdX for its disks, there is no need to >> provide an emulated driver for the same target. >> >> Such configuration can work with the OVMF firmware, as it supports PV >> disk. > Acked-by: Ian Jackson > > I have checked this with the docs, and this change makes the libxl > behave as documented and as I intended when I wrote the doc. > This commit prevents a guest from seeing disks that specify xvdX ("disk = [ '/root/virt/fedora.img,raw,xvda,rw' ]", for example). TBH, I am not sure I understand how this is supposed to work --- how is the guest expected to discover the disk? -boris