On Fri, 2016-01-08 at 14:45 +, Ian Jackson wrote:
> Ian Campbell writes ("Re: [PATCH 25/28] libxl: emuids: Perhaps change dm
> xs control path"):
> > On Fri, 2016-01-08 at 14:12 +, Ian Jackson wrote:
> > > * In xenstore we record which qemus a domain has. This is
> > > necessary
> > >
Ian Campbell writes ("Re: [PATCH 25/28] libxl: emuids: Perhaps change dm xs
control path"):
> On Fri, 2016-01-08 at 14:12 +, Ian Jackson wrote:
> > * In xenstore we record which qemus a domain has. This is necessary
> > * for correct teardown. And, we also record whether the xenstore
> >
On Fri, 2016-01-08 at 14:12 +, Ian Jackson wrote:
> Ian Campbell writes ("Re: [PATCH 25/28] libxl: emuids: Perhaps change dm
> xs control path"):
> > So, do I understand correctly that the states (combinations of bits)
> > are:
>
> No.
>
> > Describing SPLIT as an "ID" is a bit odd (it's a ki
Ian Campbell writes ("Re: [PATCH 25/28] libxl: emuids: Perhaps change dm xs
control path"):
> So, do I understand correctly that the states (combinations of bits) are:
No.
> Describing SPLIT as an "ID" is a bit odd (it's a kind of meta thing) but I
> suppose I can see why it is done this way. An
We are going to want to run two qemus, which will mean them having
different xs control paths. But sometimes we will run only one qemu
to do both jobs, in which case there has to be one xs control path,
because otherwise the single qemu will only see in xenstore either the
HVM DM work to do, or th
