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 10:35:00 -0400 Message-ID: <562F8B94.4050104@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> <562F7B60.9040506@oracle.com> <22063.35235.76072.701255@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.35235.76072.701255@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 Cc: Wei Liu , Ian Campbell , Stefano Stabellini , George Dunlap , "xen-devel@lists.xen.org" , Anthony PERARD List-Id: xen-devel@lists.xenproject.org On 10/27/2015 10:26 AM, Ian Jackson wrote: > Boris Ostrovsky writes ("Re: [Xen-devel] [PATCH] libxl: No emulated disk driver for xvdX disk"): >> On 10/27/2015 09:19 AM, Ian Jackson wrote: >>> 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? > So you want us to change the spec to match the implementation ? > (I haven't looked what happens with trad qemu.) > > If we change the spec, how would a user request an xvda with no > emulated device ? Can we allow specifying xvdX when we know that seabios is going to be used? -boris