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

Miguel Bernal Marin

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?
As yo said "software-defined-cockpit" bundle has needed bits to work
without desktop bundle. That's why it was created.

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 "" and "") but a more automatic mechanism would be nice.
We need to ask to "ioc-cbc-tools" to improve their tool/systemd services,
to start only when on supported HW.

3. The service-os bundle includes "mcelog", but it does not seem to run/be functional by default. How can I start it?
It should be started by

[1] service-os:
[2] software-defined-cockpit:


Miguel Bernal Marin Open Source Technology Center Intel Corporation

Join to automatically receive all group messages.