|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [DOCDAY PATCH] docs: initial documentation for xenstore paths
On Thu, 2012-08-09 at 14:38 +0100, Ian Jackson wrote:
> Ian Campbell writes ("Re: [DOCDAY PATCH] docs: initial documentation for
> xenstore paths"):
> > On Mon, 2012-07-30 at 15:03 +0100, Ian Campbell wrote:
> > > This is based upon my inspection of a system with a single PV domain
> > > running
> > > and is therefore very incomplete.
> > >
> > > There are several things I'm not sure of here, mostly marked with XXX in
> > > the
> > > text.
> > >
> > > In particular:
> > >
> > > - We seem to expose various things to the guest which really it has no
> > > need to
> > > know (at least not via xenstore). e.g. its own domid, its device model
> > > pid,
> > > the size of the video ram, store port and gref.
>
> Maybe we need to have a "???" or "?deprecated" tag ? That would avoid
> us documenting things which we don't want people to use.
deprecated would be useful in some places.
I think we have other places where a key is visible to the guest e.g.
because hvmloader uses it, which we can't really "deprecate" as a means
of hiding them. Perhaps "internal" or "private" in addition to
deprecate?.
> > > - What is the distinction between /vm/UUID and /local/domain/DOMID
>
> I think the former should be abolished (eventually).
Is there a distinction between "domain" and "vm" which is relevant here.
Is a VM potentially composed of several domains? (e.g. the guest, the
stub domain, a. n. other helper domain etc)
Ian.
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel
|
![]() |
Lists.xenproject.org is hosted with RackSpace, monitoring our |