Purpose of the service-os and software-defined-cockpit bundles

Geoffroy Van Cutsem

Hi folks,

I was upgrading my system to ACRN v0.2 today and wanted to ask a couple of questions regarding two bundles that we install as part of the process, namely the service-os [1] and software-defined-cockpit [2] bundles:
1. The software-defined-cockpit bundle includes various media and graphics pieces (inc. Weston), do we still need to also install the desktop bundle?
2. The software-defined-cockpit installs the ioc-cbc-tools on the system. These are not functional on standard, off-the-shelf HW such as NUCs and UP2. Is there a way we could make these only start if running on supported HW? One can 'mask' them manually (disabling is not sufficient as they include "WantedBy=basic.target" and "WantedBy=multi-user.target") but a more automatic mechanism would be nice.
3. The service-os bundle includes "mcelog", but it does not seem to run/be functional by default. How can I start it?

[1] service-os: https://github.com/clearlinux/clr-bundles/blob/master/bundles/service-os
[2] software-defined-cockpit: https://github.com/clearlinux/clr-bundles/blob/master/bundles/software-defined-cockpit


Join acrn-users@lists.projectacrn.org to automatically receive all group messages.