On Tue, Feb 06, 2018 at 03:08:45PM +0200, Oleksandr Grytsov wrote:
> On Tue, Feb 6, 2018 at 2:36 PM, Wei Liu <wei.l...@citrix.com> wrote:
> 
> > On Thu, Dec 14, 2017 at 04:14:12PM +0200, Oleksandr Grytsov wrote:
> > > From: Oleksandr Grytsov <oleksandr_gryt...@epam.com>
> > >
> > > We have following arm-based setup:
> > >
> > > - Dom0 with xen and xen tools;
> > > - Dom1 with device backends (but it is not the driver domain);
> >
> > What is your definition of a "driver domain"? What does it do in this
> > case?
> >
> > I seem to have seen people use this term in different contexts to mean
> > slightly different things. I need to figure out what you actually mean
> > first.
> >
> >
> I see in the libxl/xl sources that closing PV devices is done differently
> in case backends are in Dom0 and are in other domain. It is called as
> driver domain in the sources. So, I don't have clear understanding
> what does it mean. In our setup backends are in Dom1 and xl is in Dom0.
> And I see that xl dosn't close PV device on domain reboot or shutdown.

Do you run xl devd in your backend domain?

Wei.

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

Reply via email to