VirtualBox subsystem on reconfigurable init
Martijn Verschoor
verschoor at ...434...
Fri Apr 28 16:33:39 CEST 2017
Yes that’s it! It fixes both scenarios. I had not thought about the priorities.
Thanks for your prompt and adequate answer!
Met vriendelijke groet / kind regards,
Martijn Verschoor
Cyber Security Labs B.V. | Gooimeer 6-31 | 1411 DD Naarden | The Netherlands
+31 35 631 3253 (office) | +31 616 014 087 (mobile)
On 28 Apr 2017, at 16:10, Alexander Boettcher <alexander.boettcher at ...1...> wrote:
> Hello,
>
> On 28.04.2017 15:24, Martijn Verschoor wrote:
>> <start name="launcher">
>> + <binary name="init"/>
>> + <resource name="RAM" quantum="1500M"/>
>> + <config>
>
> I think this is not good. The sub-init gets started on the highest
> possible priority(band) - you need at least priority="-2" here (as it
> was for the virtualbox instance beforehand.
>
> (You may also enable in your run script cpu_monitor variable to see who
> get what part of the CPU share).
>
> Hope it helps,
>
> --
> Alexander Boettcher
> Genode Labs
>
> http://www.genode-labs.com - http://www.genode.org
>
> Genode Labs GmbH - Amtsgericht Dresden - HRB 28424 - Sitz Dresden
> Geschäftsführer: Dr.-Ing. Norman Feske, Christian Helmuth
>
> ------------------------------------------------------------------------------
> 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
> genode-main at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/genode-main
More information about the users
mailing list