On Tue, 22 Dec 2015, Ian Jackson wrote:
> If QEMU supports xsrestrict, pass xsrestrict=on to it (by default).
>
> XXX We need to do this only if xenstored supports it, and AFAICT there
> is not a particularly easy way to test this. Should we open a new
> test xenstore connection to query this inf
Ian Campbell writes ("Re: [PATCH 28/28] libxl: xsrestrict QEMU"):
> On Tue, 2015-12-22 at 18:45 +, Ian Jackson wrote:
> > If QEMU supports xsrestrict, pass xsrestrict=on to it (by default).
> >
> > XXX We need to do this only if xenstored supports it, and AFAICT there
> > is not a particularly
If QEMU supports xsrestrict, pass xsrestrict=on to it (by default).
XXX We need to do this only if xenstored supports it, and AFAICT there
is not a particularly easy way to test this. Should we open a new
test xenstore connection to query this information ? We could do this
once per libxl ctx.
