Am Freitag, 4. August 2017 11:56:38 CEST schrieb Norman Feske:
I have tested it quickly, I checkout staging
(commit 005820bb7bf6cb8b833b4227b8377984df5f9ceb) and build the launcher
scenario. Now the scenario is started. Thanks Norman for your quick fix.
While giving the scenario a quick spin, I observed another cap-quota
issue, which is caused by the too low default value of 50 - the value
used for all <start> notes that lack an explicit 'caps' attribute. By
setting this value to 100, the scenario starts up with NOVA on Qemu
(tested on the current staging branch). However, apparently the launcher
component also needs a few quota adjustments. I just fixed the
corresponding parts in the commit  on the staging branch. May you
give it a try?
The 'drivers' subsystem  is an init instance with 7
children (as of now). Hence, assigning 1000 caps to the subsystem seems
to be reasonable.
Ok, drivers 'subsystem', that is what I missed. I haven't realized that the
'drivers.config' is a subsystem configuration.
Ok, limit means also the 'free cap ressouces' for the component and this
be transfered to other 'server components'. 'used' is only showing the
of RPC objects, dataspaces, signal handlers of the actual/current
not also from the other 'server component'. Now I got it.
The limit of a component decreases each time it creates a session to a
service where it transfers some of its own quota limit to the server.
Initially, the limit of 'drivers' is 300. But as soon as 'drivers'
creates sessions to the outside, its limit decreases step by step. You
can think of the limit as the balance of a bank account. It you transfer
money to another account, the balance decreases. The "used" value is the
fraction of the quota that the component turned into actual resources
(like RPC objects, dataspaces, signal handlers). To stay with the
analogy, these are the purchased goods.
I hope the above explanation sounds logical.
Yes, many thanks for your detailed explanation. I think, I understood now.
Thanks for bringing up this
topic on the mailing list. You may not be the only one confused by the
messages. Finally, let me compliment you for using the "diag" feature
and for including all important details of your scenario at the start of
No, problem. I'm also a C++ developer in my company and I get sometimes
'problems/crash dumps' from my colleagues/customer to fix them without
any infos (build/version number, etc) :-).
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
genode-main mailing list