All of lore.kernel.org
 help / color / mirror / Atom feed
From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>,
	George Dunlap <George.Dunlap@eu.citrix.com>
Cc: Anthony PERARD <anthony.perard@citrix.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
	Wei Liu <wei.liu2@citrix.com>,
	Ian Campbell <ian.campbell@citrix.com>,
	Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: [PATCH] libxl: No emulated disk driver for xvdX disk
Date: Tue, 27 Oct 2015 09:25:52 -0400	[thread overview]
Message-ID: <562F7B60.9040506@oracle.com> (raw)
In-Reply-To: <22063.31205.869213.960160@mariner.uk.xensource.com>

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
>> <stefano.stabellini@eu.citrix.com> 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

  reply	other threads:[~2015-10-27 13:25 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-14 11:05 [PATCH] libxl: No emulated disk driver for xvdX disk Anthony PERARD
2015-10-16 14:01 ` Ian Jackson
2015-10-22 15:54   ` Ian Campbell
2015-10-26 21:53   ` Boris Ostrovsky
2015-10-26 21:53   ` Boris Ostrovsky
2015-10-27 11:11     ` Stefano Stabellini
2015-10-27 11:31       ` George Dunlap
2015-10-27 13:19         ` Ian Jackson
2015-10-27 13:25           ` Boris Ostrovsky [this message]
2015-10-27 14:26             ` Ian Jackson
2015-10-27 14:35               ` Boris Ostrovsky
2015-10-27 14:43                 ` Ian Jackson
2015-10-27 14:52                   ` George Dunlap
2015-10-27 14:34           ` George Dunlap

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=562F7B60.9040506@oracle.com \
    --to=boris.ostrovsky@oracle.com \
    --cc=George.Dunlap@eu.citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=anthony.perard@citrix.com \
    --cc=ian.campbell@citrix.com \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xen.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.