How to install/configure Virtualbox?

bigphil · Post by **bigphil** » Mon Mar 24, 2025 5:36 pm

Hi all,
I'm running Fossapup64 9.5 and attempting to install Virtualbox from Quickpet.
I wasn't sure which version to use as their wasn't one for Fossa so I downloaded the Focal version.
It also stated to download devx and kernel sources which were .SFS files so I loaded them.
I then installed the .deb and it stated enter rcvboxdrv setup in a terminal.
However I got the following response -

: vbox.png(1).png (115.29 KiB) Viewed 408 times

Here's what was in setup.log -

'Building the main VirtualBox module.
Building the net filter module.
Building the net adapter module.
Building the PCI pass-through module.
Error building the module:
make: *** No rule to make target 'install'. Stop.'

However when I clicked on the menu entry it fired up -

: vbox.png.png (118.09 KiB) Viewed 408 times

So
1 - did it install OK if not then why not?
2 - how do you set it up to point to the WindozeXP CD as all I can see is a ISO image selection box?

Any help would be greatly appreciated.
Phil.

Post by **rockedge** » Mon Mar 24, 2025 6:30 pm

@bigphil,
do you have the kernel sources SFS for your version of kernel loaded into the Fossapup64 system you are running?

The errors indicate that the virtual drive driver did not build to completion. VirtualBox will run but be unable to access any virtual drives, it will be nonfunctional.

For the VirtualBox virtual drives/partitions driver to be built successfully you will need the correct kernel sources loaded into Fossapup64 before running the rcvboxdrv script.

After the VirtualBox setup builds the kernel driver correctly you can then unload the kernel sources SFS.

hikohan · Post by **hikohan** » Tue Mar 25, 2025 9:15 am

By my setup log for you.

VirtualBox Setup

Before install, make sure your dist. SFS Kernel Source & Dev compiler are online.

1. Download Virtualbox .deb

Downloaded the latest version of Virtualbox DEB match your Puppy, Install

(Fossa64pup is 20.04 FOCAL version.)

2. Download a "Guest Additions" ISO

from download.virtualbox.org/virtualbox/

Select the subdirectory that matches the VirtualBox version you have just installed.

3. Edit /etc/group for Virtualbox permission

Add the following line, add user::group for vbox

Code: Select all

vboxusers::1001:root,spot,fido

4. Build Kernel support

run /sbin/vboxconfig .

after compile,

5. Run the VirtualBox setup

From the Puppy Utility menu, create a virtual machine, and then start it.

If you want to be able to access local disk & best resolution, you''ll need to install the Guest Additions CD via the VBOX/Devices menu.

Mount iso, and install Additions package.

Sorry, no one click PET for you, I would like to reserve your pleasure on Puppy Linux and some error message lint.

bigphil · Post by **bigphil** » Wed Mar 26, 2025 5:16 pm

@ hikohan

still can't get Virtualbox to run.
I'm OK until I get to operation 3 which I don't fully understand. I can't find anything in /etc that refers to Virtualbox permissions.

I also don't understand what you mean by 'Select the subdirectory that matches the VirtualBox version you have just installed'.

Phil.

hikohan · Post by **hikohan** » Thu Mar 27, 2025 12:34 am

I also don't understand what you mean by 'Select the subdirectory that matches the VirtualBox version you have just installed'.

Virtual box DEB package version HAS TO match 'Guest Additions ISO' version.

Code: Select all

The difficulty of installation is a challenge and fun.

norgo · Post by **norgo** » Thu Mar 27, 2025 12:45 am

@bigphil
kernel module package
k5.4.53

bigphil · Post by **bigphil** » Thu Mar 27, 2025 4:50 pm

Hello all,

thanks for all your help but I have now given up trying to install Virtualbox, I will have to boot into Windoze to run my windows program.
I have tried several 'flavours' of it including the .SFS in the link norgo posted.

It all goes horribly wrong when I enter the terminal command '/sbin/vboxconfig'.

Maybe sometime someone will post an idiots guide into how to install it.

Once again thanks for your help.

Phil.

norgo · Post by **norgo** » Thu Mar 27, 2025 8:04 pm

@bigphil

did a 2nd test of virtualbox 6.1.22 and matching kernel module package k5.4.53 under Fossapup64 just right now.
works out of the box for me
Important
install kernel modules at first step
after that load the virtualbox SFS
all needed services will be started automatically
all needed modifications will be applied automatically
attention
this vbox version contains a lot of modifications to be able to run under puppylinux
launch of some original scripts overwrite important preferences!
this you've already tested

bigphil · Post by **bigphil** » Fri Mar 28, 2025 11:08 am

@norgo

I followed your instructions and it appeared to work however when I attempted to start the 'installed' machine it reported -

: vboxerror.png (43.35 KiB) Viewed 205 times

What I don't understand is when I click on new and follow all the instructions it never prompts me to install WindowsXP from the installation CD.

Any ideas?

Phil.

Jasper · Post by **Jasper** » Fri Mar 28, 2025 1:17 pm

Any ideas?

Phil.

Maybe a thank you to the members who help you might be appreciated?

The error message indicates that you already have a Virtual Machine registered with the same identity (UUID).

You cannot register multiple VM's with the same UUID.

If you have an existing VM, then you need to delete it ............... it would explain why you have not been asked to 'Install' the OS.

wizard · Post by **wizard** » Fri Mar 28, 2025 1:51 pm

@bigphil

Running fossaPup64 9.5, using virtualbox-6.1_6.1.34-150636.1~Ubuntu~eoan_amd64.deb, installs and runs without any issues.

wizard

Geek3579 · Post by **Geek3579** » Sat Mar 29, 2025 7:34 am

I'm a bit late to respond to the earlier posts, but here goes...
This is from years ago with Tahrpup, but I believe its still good.

After installing Guest additions, I run the following two commands:

1) adduser vboxusers
you will then be asked to enter a new password - note, no display of password is provided

Sample successful terminal operation is as follows: ( with some line spaces added)

root# adduser vboxusers
adduser: /home/vboxusers: No such file or directory
Changing password for vboxusers
New password: <enter your password>
Retype password: <enter your password again>
Password for vboxusers changed by root

2) /sbin/vboxconfig
This will take some time, but will return to the terminal control.
A non-terminating process means an error, eg an incorrect kernel-source, in which case the computer must be restarted by holding down the power button.

Sample successful terminal operation is as follows: (ignore errors - some line spaces added)

root# /sbin/vboxconfig
ln: failed to create symbolic link ‘/etc/rc.d/rc0.d/K80vboxdrv’: No such file or directory
...MANY SIMILAR LINES here...
ln: failed to create symbolic link ‘/etc/rc.d/rc6.d/K65vboxweb-service’: No such file or directory
vboxdrv.sh: Building VirtualBox kernel modules.
vboxdrv.sh: Starting VirtualBox services.
vboxdrv.sh: Starting VirtualBox services.
root#

bigphil · Post by **bigphil** » Sun Mar 30, 2025 2:17 pm

Thanks for all your help but I have now given up.

I did a fresh install of Fossapu64, did exactly as norgo said in his post above and, much to my relief, it prompted me to install windoze, which I did from a known working disk.

However when I went to power up the machine it reported -

: Screenshot.png (37.53 KiB) Viewed 115 times

Unless anyone can come up with a simple answer I will admit defeat and continue booting into windoze to run the software.

Phil.

wizard · Post by **wizard** » Sun Mar 30, 2025 2:23 pm

@bigphil

Try checking your bios/setup to be sure virtualization is enabled.

wizard

norgo · Post by **norgo** » Sun Mar 30, 2025 9:08 pm

@bigphil
Only for understanding
You did an installation of windows-xp in virtualbox.
After successful installation you safed a copy as virtual disk image [ vdi ].

If you try to load this vdi ( after power down of your computer ) it fails.
Is this correct?

Does your vdi image contain two files with file extension vbox and vbox-prev ?
These files contain a lot of vbox preferences and the UUID of your diskimage.

I wouldn't blame it on virtualbox.
I'm using exactly the same version and have no problems at all.

Another solution could be the usage of qemu.
It's possible to convert the existing vdi disk image into qcow2
This is really working fine.
If you want to try it out, here the command to convert

Code: Select all

qemu-img convert -f vdi -O qcow2 windowsxp.vdi windowsxp.qcow2

bigphil · Post by **bigphil** » Mon Mar 31, 2025 10:34 am

curious er and curious er - I installed Virtualbox on my other machine, loaded WindowsXP and it all worked. So I copied the complete install of Fossa and loaded it on the machine I want Virtualbox on and, guess what, it didn't work displaying the exact error message as before.
So it's something to do with the machine.

@wizard I can't find the bios entry for virtualization on the machine Virtualbox doesn't work on but the machine that it does work on virtualization is there and enabled.

any ideas?

Phil

norgo · Post by **norgo** » Mon Mar 31, 2025 11:23 am

please install and run qemu_ready
what's the output?

wizard · Post by **wizard** » Mon Mar 31, 2025 1:12 pm

@bigphil

Make, model, and what CPU is installed in the non-working computer?

wizard

bigphil · Post by **bigphil** » Mon Mar 31, 2025 1:59 pm

@wizard

the non working computer is an Acer Aspire 5332 Laptop, Intel Celeron Cpu 1.8GHZ, 3GB memory.

Phil.

wizard · Post by **wizard** » Mon Mar 31, 2025 2:14 pm

@bigphil

Lots of Celerons do not support virtualization, which would explain your problem. If you can tie down the CPU to it's model number we can verify on the Intel site.

wizard

edit: Just did a little checking, based on your msg the 1.8ghz Celeron is likely a T3000. That's a dual core, 64bit, and it does not support virtualization

bigphil · Post by **bigphil** » Mon Mar 31, 2025 2:57 pm

@wizard

I have confirmed it is the T3000, oh well no Virtualbox on there then.

Thanks for your help.

Phil

Puppy Linux Discussion Forum