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:
[runtime -> vbox_labyrinth -> vbox] Error: ioctl operation=33
[runtime -> vbox_labyrinth -> vbox] Error: void ioctl(SUPCALLVMMR0&) called (/data/depot/genodelabs/src/vbox6/2024-04-11/src/virtualbox6/sup.cc:666), not implemented, eip=0x1a46715
My only guess is that something about the way I've configured the VM triggers this, but I haven't been able to dig deeper. Does anyone have any thoughts on this?
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/thr...)
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.
Cheers,
Alex.