On 5/24/24 2:33 AM, Alexander Boettcher wrote:
Hello,
On 24.05.24 00:59, John J. Karcher wrote:
Beside that, you may create a custom launcher and replace the
occurrence of block.vdi with your desired vdi file name. To do so,
start a vdi_block instance, copy the resulting xml vdi_block text
from config/ managed/runtime to your new launcher file. Replace in
the file the xml node "start" with "launcher", e.g. <start ...> ... /
start> -> <launcher ...> ... /launcher>. Finally, replace the
occurrences of block.vdi with another file name you desire.
I don't want to rename all my VDI files, so I did this, but I seem to
be missing something. (I am still at the kindergarten level with
these config files.)
Here is my example:
<launcher name="vdi_block_abc" pkg="alex-ab/pkg/vdi_block/2024-04-09">
<route>
<service name="File_system" label="ABC-disk1.vdi">
<child name="vm_fs_abc"/>
</service>
</route>
</launcher>
[snip]
Am I on the right track? Do I need to add a <config> node or something?
just using the Genode re-label mechanism will not work. Inside the
established file system session, the file name is actually requested,
which is not rewriteable from the outside.
So, indeed, you have to change the config of the vdi_block, that is why
I suggested to look into config/managed/_runtime_ instead of config/
managed/deploy, the former contains the config snipped.
I crafted a config on a ram_fs and it looks like follows. Additionally,
I removed the <import...> node and named the Filesystem label a bit more
obvious, just to avoid confusion. The import node is only required to
import a new empty block.vdi if it does not exists, which you don't
desire/require in your case.
<launcher pkg="alex-ab/pkg/vdi_block/2024-04-09" priority="-2">
<config file="/your.vdi" writeable="yes">
<vfs>
<fs label="fs_vdi" buffer_size="2M"/>
</vfs>
</config>
<route>
<service name="File_system" label="fs_vdi">
<child name="ram_fs"/>
</service>
</route>
</launcher>
That worked - thanks another million! Now I can run the same VM three
ways - Linux/VBox, Genode/VBox, and Gendode/Seoul - very nifty!
In Seoul, there is no audio, but that's probably because the VM isn't
configured for VirtIO audio; your pre-built VMs work fine.
FWIW, my top feature request for Seoul would probably be copy/paste,
which is universally useful, followed by shared folder support, which I
can work around.
(And sorry for the poor reading comprehension. But I left the above
long-winded quote intact because I suspect it may be useful in the
archives for someone else.)
It looks like I am only one step away from being able to switch to
Genode full-time. Consider this a warning - real "user" questions are
coming soon! ;^)
Happy Sculpting!
John J. Karcher
devu...@alternateapproach.com
_______________________________________________
users mailing list -- users@lists.genode.org
To unsubscribe send an email to users-le...@lists.genode.org
Archived at
https://lists.genode.org/mailman3/hyperkitty/list/users@lists.genode.org/message/UN4BYIMUSURQYTH3GVLQKI6CYYN5XXSO/
