Hi,
On 08/03/2025 00:53, Stefano Stabellini wrote:
On Fri, 7 Mar 2025, Julien Grall wrote:
init-dom0less only initializes non- introduced domains, so hwdom doesn't get
its "domid" xenstore node populated. That leads to other errors.
So I think with Denis's patch, this isn't strictly needed. It does help
existing toolstack code work today.
I don't think the toolstack is ready for a split between control/hardware
domain. That said, shouldn't the toolstack run in the control domain? Same for
xenstored (unless you have a xenstored domain)?
Yes, the toolstack (if present) would be in the control domain.
xenstored doesn't have to be in the control domain and in fact it might
not be advisable to place it there today.
The main difference between the toolstack and xenstored is that the
toolstack only talks to Xen, while xenstored talks to all other VMs,
which is dangerous in many configurations.
It is not really clear which toolstack you are referring to.
Someone using vanilla Xen upstream will end up to use "xl" which has to
talk to xenstored and also indirectly to each domain (e.g.
shutdown/suspend node in xenstored). So for this setup, "xenstored" is
not optional and I would argue should be part of the control domain (or
in a xenstore stubdomain which IIRC is not supported on Arm today).
Cheers,
--
Julien Grall
