Hello, I've started using Sculpt OS and the integrated Falkon web browser. It frequently crashes when I have several tabs open, I believe this is because the ram it has been assigned is too small. I couldn't seem to find any mention of how to edit the ram allocated to processes in the Sculpt OS documentation?
How do I dynamically edit the allocated ram to processes such as the Falkon web browser? When I am using the Leitzentrale and I click on the Falkon web browser, I can see it shows 1.95 GiB / 2.00 GiB, I am guessing this is the allocated ram? However I am only assuming this is the allocated Ram size as it does not specify what type of storage this is, i.e Hard Drive Storage or Ram Memory.
The audio works in the browser too, I was able to play music in youtube music. However, the first couple times I tried playing any audio through Falkon, it didn’t work. I rebooted and started fresh RAM FS in an attempt to get audio working. For the first 2 or 3 times it didn’t work. I am not sure what I did differently, but on the 3rd time I tried and downloaded the Falkon browser, the audio suddenly worked. I was able to control the volume by editing the config audio XML file and saving it.
I will need to do more tests to see if the audio not working was a fluke or I was doing something incorrectly before.
Thank you, Jack Curran
Hello Jack,
Hello, I've started using Sculpt OS and the integrated Falkon web browser. It frequently crashes when I have several tabs open, I believe this is because the ram it has been assigned is too small. I couldn't seem to find any mention of how to edit the ram allocated to processes in the Sculpt OS documentation?
How do I dynamically edit the allocated ram to processes such as the Falkon web browser? When I am using the Leitzentrale and I click on the Falkon web browser, I can see it shows 1.95 GiB / 2.00 GiB, I am guessing this is the allocated ram? However I am only assuming this is the allocated Ram size as it does not specify what type of storage this is, i.e Hard Drive Storage or Ram Memory.
At the moment there is no out-of-the-box user-interface to change the RAM or CAP quota for deployed components and changing them currently involves some fiddling as you need to adjust the resource allowances manually. In this case it is especially involved as the 'falkon-jemalloc' pkg bundles mulitple components running in an statically configured sub-init.
That being said, generally speaking, you can change the quota by adding a 'ram' and 'caps' attribute to either a '<start>' or '<launcher>' node and increase the value. That is one of the reasons where creating a launcher comes in handy as sometimes the pre-configured resource requirements might not be enough in all cases and one needs to override them.
As you noticed that is true in particular when using the falkon pkg as its resource consumption is quite volatile depending on the website and number of tabs.
Of course Genode itself contains all the means for reacting to such resource requests dynamically (and this already employed for certain components, like the 'depot_rom' or 'ram_fs') but is not enabled in general to prevent components from tipping on each others toes. How to better make use of available slack-resources is still ongoing research.
[…]
I will need to do more tests to see if the audio not working was a fluke or I was doing something incorrectly before.
On most systems the current audio driver can only be started once as the device might not produce sounds when the driver was restarted. Depending on the system you might get away by starting it several times until it is audible again but that is not always a given.
Unfortunately switching presets might implicitly start and stop the driver and is best avoided (after the initial exploration or try-out phase of course) and for regular usage of Sculpt I would recommend making a preset persistent (as discussed in the documentation) and to mainly work with launchers.
We will work on remedy this limitation but there is not time-frame for that yet.
Regards Josef
Hello Jack,
in case you're comfortable with a ready-to-use Firefox in a VM appliance, have a look into my repository, + -> Add -> url with alex-ab -> Firefox (disposal)
Cheers,
Alex.
On 07.05.24 03:48, Jack Curran wrote:
Hello, I've started using Sculpt OS and the integrated Falkon web browser. It frequently crashes when I have several tabs open, I believe this is because the ram it has been assigned is too small. I couldn't seem to find any mention of how to edit the ram allocated to processes in the Sculpt OS documentation?
How do I dynamically edit the allocated ram to processes such as the Falkon web browser? When I am using the Leitzentrale and I click on the Falkon web browser, I can see it shows 1.95 GiB / 2.00 GiB, I am guessing this is the allocated ram? However I am only assuming this is the allocated Ram size as it does not specify what type of storage this is, i.e Hard Drive Storage or Ram Memory.
The audio works in the browser too, I was able to play music in youtube music. However, the first couple times I tried playing any audio through Falkon, it didn’t work. I rebooted and started fresh RAM FS in an attempt to get audio working. For the first 2 or 3 times it didn’t work. I am not sure what I did differently, but on the 3rd time I tried and downloaded the Falkon browser, the audio suddenly worked. I was able to control the volume by editing the config audio XML file and saving it.
I will need to do more tests to see if the audio not working was a fluke or I was doing something incorrectly before.
Thank you, Jack Curran _______________________________________________ users mailing list -- users@lists.genode.org To unsubscribe send an email to users-leave@lists.genode.org Archived at https://lists.genode.org/mailman3/hyperkitty/list/users@lists.genode.org/mes...
Hello Alex, sorry for the very late reply! I have only now just gotten to test this out, I got busy with other things.
I have just used your disposable Firefox VM and it works great! The audio works great too! Although, as stated by Josef, switching presets can stop the audio driver which cannot be restarted unless you reboot SculptOS I believe, so after editing things in SculptOS, the audio stopped working until I did a restart again.
I was able to use jschlatow depot firefox AV virtual machine successfully too.
I have formatted and installed my NVME drive in sculpt and chosen it as the File System instead of the RAMFS which I had been using prior. So far I believe it is working. Although I have noticed that when I restart the VM, the settings do not persist and are reset. I am not using the disposable VM for this either, I chose the VMFS which I believe is a file system for virtual machines? Is this not persistent? I don't know what FS option I have to select to have the VM changes be saved.
I would like to have a persistent Firefox VM, with a high amount of ram allocation so that it does not crash when I have lots of tabs open. I would like to be able to save the settings and files to the NVME FS instead of using the RAMFS which is what I have been using prior. I am struggling to create my own. So I require some advice.
I am trying to use Genodelabs Depot vbox6, but for whatever reason I cannot get the virtual machine to work. It won't display as a window inside the WM even though I am able to use your VM inside the WM I have also successfully used other developer's public depot VM fine.
When I configure the Genodelabs Depot vbox6 it asks for ROM Mesa GPU driver. I am thinking maybe I am doing something wrong with configuring the GPU to work, as this is one of the only options that isn't asked for in your VM settings.
Sorry for the long winded message, I hope I am conveying my message clearly.
Thank you!
Hello,
On 28.06.24 01:49, Jack Curran wrote:
I have formatted and installed my NVME drive in sculpt and chosen it as the File System instead of the RAMFS which I had been using prior. So far I believe it is working. Although I have noticed that when I restart the VM, the settings do not persist and are reset. I am not using the disposable VM for this either, I chose the VMFS which I believe is a file system for virtual machines? Is this not persistent? I don't know what FS option I have to select to have the VM changes be saved.
right, the disposal VM can't be used for in VM persistent, that was the intention of this package. Alternatively, I also provide a template VM package in my Sculpt index, which is basically the same Tinycore VM, but with persistent enabled, which you can manage freely. So for firefox, you would have to install the firefox_getlastest package of Tinycore, which does the download and packaging of the current Firefox. Just as note, according to the Tinycore philosophy, only some changes to some folders are stored persistently, see [0] [1].
[0] https://forum.tinycorelinux.net/index.php/topic,21124.0.html [1] http://tinycorelinux.net/book.html
Beside the inside VM preparation, your filesystem launcher has to point to a persistent storage. When looking at the vmfs launcher as provided with the vanilla Sculpt:
<launcher pkg="genodelabs/pkg/chroot/..."> <route> <service name="File_system"> <child name="default_fs_rw"/> </service> </route> <config> <default-policy path="/vm/debian" writeable="yes"/> </config> </launcher>
you see, that it is actually a change root, which rewrites the file system opening request to "default_fs_rw" and changes the root folder to /vm/debian instead of /. You may make a copy of this launcher, and let it point to your desired filesystem component and to the folder you want to have. "default_fs_rw" points to the current "used" filesystem (as used/shown in the Leitzentrale), which can be your ram_fs, usb or nvme. If you want to remove any uncertainty, you may change it here explicitly to your target fs component, e.g. replace it with the label as shown in component graph, e.g. for me it would be ahci-0.3.fs and for you to your nvme fs accordingly.
I would like to have a persistent Firefox VM, with a high amount of ram allocation so that it does not crash when I have lots of tabs open. I would like to be able to save the settings and files to the NVME FS instead of using the RAMFS which is what I have been using prior. I am struggling to create my own. So I require some advice.
In general, you may make a copy of the package you are interested in and increase all values to fit your needs. [3] contains a basic description, how to use your "local" depot. As depicted in the article, the local depot content is not cached, which makes it possible to easily iterate package modifications. As example, make a copy of the firefox@seoul_audio package according to [3], look into the runtime of your local package version, e.g.:
depot/local/pkg/firefox@seoul_audio/<version>/runtime:
... <runtime ram="2450M" caps="1350" binary="init"> ... <start name="seoul" caps="920"> <binary name="seoul"/> <resource name="RAM" quantum="3G"/> ...
and increase the ram and caps value as you feel comfortable.
[3] https://genodians.org/jws/2019-01-28-depot-local
I am trying to use Genodelabs Depot vbox6, but for whatever reason I cannot get the virtual machine to work. It won't display as a window inside the WM even though I am able to use your VM inside the WM I have also successfully used other developer's public depot VM fine. When I configure the Genodelabs Depot vbox6 it asks for ROM Mesa GPU driver. I am thinking maybe I am doing something wrong with configuring the GPU to work, as this is one of the only options that isn't asked for in your VM settings.
The vbox6 package from GenodeLabs requires all potential ever needed services (even so, you may not intend to use all). You may route them to the "blackhole" component or, if supported, to the right GPU driver, e.g. snippet for the launcher files
<service name="Gpu"> <child name="intel_gpu"/> </service> <service name="ROM" label="mesa_gpu_drv.lib.so"> <child name="mesa_gpu-intel"/> </service>
<service name="Gpu"> <child name="black_hole"/> </service> <service name="ROM" label="mesa_gpu_drv.lib.so"> <child name="black_hole"/> </service>
The mesa_gpu-intel and blackhole package is part of the Genode Labs index.
Cheers,
Alex.