On 5/18/24 10:51 AM, Alexander Boettcher wrote:
Hello,
On 18.05.24 07:44, John J. Karcher wrote:
I'm so close that I can taste it...
I set up launchers for a couple of my existing VirtualBox VMs, including giving each its own vm_fs. I also converted my disk files from dynamic to fixed. The window opens up, but the contents stay black, and the following items are put in the log:
[snip]
I can only suggest to compare your .vbox6 file to depot/genodelabs/raw/ vbox6/<date>/machine.vbox6. It happened more than one time that a subtle mistake make vbox6 unhappy for some of us. (as example https:// lists.genode.org/mailman3/hyperkitty/list/users@lists.genode.org/thread/ ISG37EHECREYJCF4WOKLFPAV2NMHXSG7)
After some trial-and-error, I discovered that using the "USBTablet" for the pointing device causes this ioctl 33 error - switching to "PS2Mouse" causes it to work fine! Good to note for anyone else trying this.
This is very exciting! I just need to figure out how to share files, which I currently do using an NFS share on the Linux host. I'd like to avoid VBox shared folders, since I want it to work with Seoul also, so I might just have to boot my "host" Linux OS directly from the partition, until I can migrate that function somewhere else.
I then tried to use Seoul, but my ignorance got in the way of this one. How do I configure the "vdi_block" component to point to my disk file (not named "block.vdi")?
Renaming your vdi to block.vdi would be the easiest way (and potentially adjusting your .vbox file to point to your renamed block.vdi file).
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>
If I use "block.vdi" for the label, it doesn't complain, but it can't find the file. If I use it as above, it fails to load because of missing "block.vdi". ("vm_fs_abc" points to the correct directory, and works with VBox.)
Am I on the right track? Do I need to add a <config> node or something?
Thanks a million! -- John J. Karcher devuser@alternateapproach.com