On 16.09.2021 17:07, Luca Fancellu wrote: > I explain here my understanding on dom0less, this feature is used to start > domUs at > Xen boot in parallel, the name is misleading but it doesn’t require dom0 to > be absent. > > So if you have a dom0 kernel embed in the image, it's completely fine to > start it and it > doesn’t have to be skipped. > > Here the possible user cases: > 1) start only dom0 [dom0 modules on xen.cfg or embedded in Xen image] > 2) start only domUs, true dom0less [no dom0 modules on xen.cfg or embedded in > Xen image, domUs on DT] > 3) start dom0 and domUs [(dom0 modules on xen.cfg or embedded in Xen image) > and domUs on DT]
If that's the intention - fine. Stefano? Jan
