vboxbuilder: not working under 5.0

[donald]

Hello BKG
Which DE do you use and do you have the updated xzm module - please compare:

Code: Select all

guest@porteus:~$ uname -rm
5.18.8-porteus x86_64
guest@porteus:~$ cat /etc/porteus/*
001-core.xzm:20230430
002-xorg.xzm:20230430
002-xtra.xzm:20221211
003-xfce.xzm:20220925
initrd.xz:20220928

you also need ( md5sum + name )
4ad2c0217ec914cb02aab3b77fd55fe5 05-devel.xzm
834f70df7aafad867e03c8351b2434ab 06-crippled_sources-5.18.8-64bit.xzm

note:
V-box 7 did not run without a Qt module if xfce is used.
I had qt5-base-5.9.5-x86_64-jss.xzm at hand which did the job.

However, Trying to avoid writing a full tutorial (in a foreign language)
and you said you already have a V-box module -- let's start simple.
what happens when you type VirtualBox (enter) in a terminal?

in short:
get the 05 and 06 xzms and put them into modules folder > reboot
> run V-box builder ( wait - it will tell you when to click OK - it may
take some time).
The V-box module (xzm) will be in /tmp - copy it into modules > reboot.
The system will now build the driver.

If all goes well clean the /tmp directory. (V-box remnants)

[BKG]

More updates, I switched to porteus v.4 and it seemed to work with all the steps to a point where i run the sh vbox.run downloaded file, but it now stuck with building boundings in the cli. I tried to reopen the terminal and gives me an error. so now i can't open the terminal. I renooted and its stuck in boot.

[BKG]

@donald, thanks for the steps . will reinstall v.5 and try tonnight.

[BKG]

@donald, finaly some progress! I was not able to get to this before. Not sure why .

I reinstalled the porteus v.5 and redone the vbox builder with crippled sources. see below:
to compare to your cat /etc/porteus* i have below
guest@porteus:~$ uname -rm
5.18.8-porteus x86_64
guest@porteus:~$ cat /etc/porteus/*
001-core.xzm:20220630
002-xorg.xzm:20220630
002-xtra.xzm:20220630
003-xfce.xzm:20220505
initrd.xz:20220509

-I moved 05 and 06 to porteus USB sdb1/***/modules and rebooted and started the vbox builder and chose the .run file which was previously downloaded to /tmp
-It started to build the .run file and confirmed it was built successfuly. and that it is in /tmp
-moved the vbox.xzm module to /modules restarted -> modules loaded -> vbox sh service started
-in terminal typed VirtualBox and it return error because of inability to initialize QT (like you mentione earlier about QT and xfce) and also return the line saying the platform pluggins are xcb.

Should I download - qt5-base-5.9.5-x86_64-jss.xzm or xcb?

Thanks.

[donald]

you need some Qt stuff - I had this one at hand
http://www.mediafire.com/file/n6m2vta9w ... 64-jss.xzm
and V-box runs.

[BKG]

@donald it worked! another mile stone next step is to set the system so it boots into RAM and autostarts the vbox with the guest , but this is a different task. For this one thanks a million for the walkthrough and QT share.

[donald]

Great

btw
05-devel and 06-crippled_sources are no longer needed and can be moved from modules
to optional.
(you might need them for other tasks)

The v-box and QT module should be all you need to run v-box.

One obstacle:
Once loaded 05-devel can not be deactivated
(06-crippled_sources can).

solution:
Boot in always fresh mode so the module wont activate at start-up.

[fulalas]

You don't need the whole Qt package in order to run VirtualBox, only these:

Code: Select all

xcb-util-image
xcb-util-keysyms
xcb-util-renderutil
xcb-util-wm

They can all be found in Slackware official repository (download the .txz ones and convert them to .xzm using right click): http://ftp.slackware.com/pub/slackware/ ... kware64/x/

next step is to set the system so it boots into RAM and autostarts the vbox with the guest

To autoload VirtualBox during boot, just place its .xzm module into /porteus/modules. If you want to have the VirtualBox guest addition running in Porteus from inside the VM, you need to build it from inside the VM, which means you'll need both devel and crippled modules again, but this time in the VM. Once the guest addition module is built you need to copy it to your VM /porteus/modules and make sure this VM has persistence working, then you can finally reboot and enjoy

[donald]

You don't need the whole Qt package in order to run VirtualBox, only these:

Code: Select all

xcb-util-image
xcb-util-keysyms
xcb-util-renderutil
xcb-util-wm

Thanks

EDIT

....you'll need both devel and crippled modules again, but this time in the VM

If one has no idea how to get them there..
For example:
create an iso containing both modules > insert into the virtual CD-Drive and copy them over,
e.g. optional folder > eject the CD > activate both modules > insert VBoxGuestAdditions.iso (devices guest additions)
> open CD in filemanager > open terminal and run autorun.sh

how to make the iso:
create a folder, lets say dev in your home folder (host), copy both modules in > run:
mkisofs -o dev.iso /home/guest/dev

[BKG]

Thanks all for all your help. I had to drop this project for now. Win10 runs fine in vbox for some time and then breaks. And then I can no longer start vbox. I did not try to run in RAM at all.

[BKG]

Hi all, new update - I redid the install and this time ran vbox and cretaed vdi on the separate SSD and everything seems to work well!
Also for what I use the vbox it is already working fine and I don't know if i need guest additions. The end goal is:

autoboot porteus(without selection) into RAM -> start vbox headless -> autostart VM host

Thanks.