Re: [Xen-devel] Driver domains communication protocol proposal

[Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>]

George Dunlap writes ("Re: [Xen-devel] Driver domains communication protocol 
proposal"):
> On Wed, Apr 4, 2012 at 4:46 PM, Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx> wrote:
> >  vdi
> >     This host's intent to access a specific target.
> >     Non-persistent, created on request by toolstack, enumerable.
> >     Possible states: inactive/active.
> >     Abstract operations: prepare, activate, deactivate, unprepare.
> 
> VDI as used by XenServer seems to mean "virtual disk instance", and as
> such is actually persistent.  I don't quite understand what it's
> supposed to mean here, and how it differs from VBD (which in XenServer
> terminology means "virtual block device").

One "vdi" in this sense can support multiple "vbd"s.  A "vbd"
represents an attachment to a domain (or some other kind of provision
for use) whereas a "vdi" is a preparatory thing.

Feel free to suggest different terminology.

Ian.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel