[SOLVED] Virtualbox in 14.2

phenixia2003 · 07-07-2016, 11:09 AM

Hello,

Quote:

Originally Posted by Jeebizz

Except I have Slackware on a 120GB SSD , and there are only 2 partitions that I set up, a /boot and /:

Code:

slackmachine@SquirtzMcgurtz:~$ df -h
Filesystem      Size  Used Avail Use% Mounted on
/dev/root       119G   15G  105G  13% /
devtmpfs         16G     0   16G   0% /dev
tmpfs            16G  1.1M   16G   1% /run
tmpfs            16G  116K   16G   1% /dev/shm
cgroup_root      16G     0   16G   0% /sys/fs/cgroup
/dev/sda1       119M   19M  100M  16% /boot
/dev/sdb1       1.9T  1.8T   51G  98% /home
cgmfs           100K     0  100K   0% /run/cgmanager/fs
slackuser@slackmachine:~$

Code:

slackuser@slackmachine:~$ mount
/dev/sda2 on / type jfs (rw,discard)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
tmpfs on /dev/shm type tmpfs (rw)
/dev/sda1 on /boot type jfs (rw,discard)
/dev/sdb1 on /home type jfs (rw)
gvfsd-fuse on /home/slackuser/.gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,user=slackuser)
slackuser@slackmachine:~$

You've plenty of space available, so, I was wrong about the cause of the error message.

I doubt about that, but maybe there is something wrong with jfs ...

Otherwise, try to run /sbin/rcvboxdrv setup multiple times and check if you get always the same error (ie. No such file or directory) in /var/log/vbox-install.log.

--
SeB

rockinroyle · 07-07-2016, 11:32 AM

Quote:

Originally Posted by Jeebizz

Except I have Slackware on a 120GB SSD , and there are only 2 partitions that I set up, a /boot and /:

Code:

slackmachine@SquirtzMcgurtz:~$ df -h
Filesystem      Size  Used Avail Use% Mounted on
/dev/root       119G   15G  105G  13% /
devtmpfs         16G     0   16G   0% /dev
tmpfs            16G  1.1M   16G   1% /run
tmpfs            16G  116K   16G   1% /dev/shm
cgroup_root      16G     0   16G   0% /sys/fs/cgroup
/dev/sda1       119M   19M  100M  16% /boot
/dev/sdb1       1.9T  1.8T   51G  98% /home
cgmfs           100K     0  100K   0% /run/cgmanager/fs
slackuser@slackmachine:~$

Code:

slackuser@slackmachine:~$ mount
/dev/sda2 on / type jfs (rw,discard)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
tmpfs on /dev/shm type tmpfs (rw)
/dev/sda1 on /boot type jfs (rw,discard)
/dev/sdb1 on /home type jfs (rw)
gvfsd-fuse on /home/slackuser/.gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,user=slackuser)
slackuser@slackmachine:~$

I notice you only have 51G of storage left in /home? I could be mistaken but doesn't virtual box by default install the virtual disk image for guest os in /home/"user"/VirtualBox\ VMs/ ? If program runs but you dynamically allocated more than 51G to a guest os's virtual disk image I think you'd have issues?

phenixia2003 · 07-07-2016, 11:35 AM

Hello,

I've installed virtualbox in a slackware vm with jfs as filesystem and all went ok. So, this is not the filesystem. Maybe the hdd has some trouble. smartctl -a /dev/sda could give some clue.

--
SeB

Noryungi · 07-07-2016, 11:40 AM

It seems you are missing the code necessary to recompile the vbox driver:

Code:

gcc: error: /tmp/vbox.0/vboxdrv.mod.c: No such file or directory
gcc: fatal error: no input files
compilation terminated.

I would strongly advise you to either download the necessary code or re-install the whole thing from scratch.

ChuangTzu · 07-07-2016, 02:59 PM

Quote:

Originally Posted by willysr

i tried both from SBo and VirtualBox and both are ok here

virtualbox running fine here with clean upgrade/install to 14.2.

Paulo2 · 07-07-2016, 04:54 PM

New .run installer doesn't have /etc/rc.d files anymore, they are in /etc/init.d
Try

Code:

# /etc/init.d/vboxdrv setup

Jeebizz · 07-07-2016, 05:32 PM

Didn't work. Also my /home is on a 2TB hd (but obviously filled with useless crap

) , I hope to remedy that when I get an external 8TB, but again, that should not affect this either. I am still open to other suggestions, before I format and reinstall 14.2 - and yes I did a full install also.

netfoot · 07-11-2016, 06:54 PM

I'm having trouble getting VirtualBox to run under 14.2 as well.

I tried to create the various packages using SlackBuild. I was able to build

virtualbox-kernel-5.0.14_3.10.17-x86_64-1_SBo.tgz
virtualbox-extension-pack-5.0.14-x86_64-1_SBo.tgz

but the actual virtualizer itself, fails to build. I get an error saying

Quote:

Checking for Open Watcom:
** Open Watcom was not found!
Checking for iasl:
** iasl (variable IASL) not found!
Check /tmp/SBo/VirtualBox-5.0.14/configure.log for details

The logfile contains:

Quote:

# Log file generated by
#
# './configure --disable-kmods --enable-vde --enable-vnc --with-makeself=/usr/bin/echo --enable-hardening --disable-vmmraw --disable-java'
#

***** Checking environment *****
Determined build machine: linux.amd64, target machine: linux.amd64

***** Checking kBuild *****
found

***** Checking gcc *****
found version 5.3.0

***** Checking Open Watcom *****
** Open Watcom was not found!

***** Checking iasl *****
** iasl (variable IASL) not found!

Seems the Watcom compiler is needed to build the virtualizer. There is no "Open Watcom" SlackBuild, and it appears that the community looks upon this package with disfavour. I've downloaded the open-watcom-c-linux-1.9 binary installer from ftp://ftp.openwatcom.org/pub. Should I just go ahead and run it?

And what is this IASL business?

Don't remember these difficulties when I installed on 14.1.....

glorsplitz · 07-11-2016, 07:37 PM

go to https://www.virtualbox.org/wiki/Downloads

click "VirtualBox 5.0.24 for Linux hosts"

then "All distributions (built on EL5 and therefore do not require recent system libraries) i386 | AMD64"

right click i386 link OR AMD64 link, save as

then back to first link look for
VirtualBox 5.0.24 Oracle VM VirtualBox Extension Pack All supported platforms
right click "All supported platforms", save as

in konsole in folder where saved to, as root:sh VirtualBox-5.0.24-108355-Linux_amd64.bin

when that's done, from where extensions link was saved, as root:
vboxmanage extpack install --replace Oracle_VM_VirtualBox_Extension_Pack-5.0.24-108355.vbox-extpack

netfoot · 07-11-2016, 07:45 PM

And lo! "Welcome to VirtualBox!"

Thanks for showing me the way.

bassmadrigal · 07-11-2016, 08:35 PM

Quote:

Originally Posted by netfoot

I'm having trouble getting VirtualBox to run under 14.2 as well.

I tried to create the various packages using SlackBuild. I was able to build

virtualbox-kernel-5.0.14_3.10.17-x86_64-1_SBo.tgz
virtualbox-extension-pack-5.0.14-x86_64-1_SBo.tgz

but the actual virtualizer itself, fails to build. I get an error saying

The logfile contains:

Seems the Watcom compiler is needed to build the virtualizer. There is no "Open Watcom" SlackBuild, and it appears that the community looks upon this package with disfavour. I've downloaded the open-watcom-c-linux-1.9 binary installer from ftp://ftp.openwatcom.org/pub. Should I just go ahead and run it?

And what is this IASL business?

Don't remember these difficulties when I installed on 14.1.....

You're probably missing acpica, which is a required dependency of virtualbox. That is what adds support for iasl. There are no hard requirements for watcom and virtualbox runs fine without it (at least in my experience).

I was able to build virtualbox on a fresh 64bit 14.2 install without any problems. I just used sqg to generate a queue file (which just contains virtualbox-kernel, acpica, and finally virtualbox) and then had sbopkg build all the files.

It is running a VM of 64bit 14.2 right now that is working to build all my packages needed to eventually move my main system over to 14.2.

bormant · 07-12-2016, 04:21 AM

Quote:

Originally Posted by netfoot

I'm having trouble getting VirtualBox to run under 14.2 as well.

I tried to create the various packages using SlackBuild. I was able to build

virtualbox-kernel-5.0.14_3.10.17-x86_64-1_SBo.tgz
virtualbox-extension-pack-5.0.14-x86_64-1_SBo.tgz

Slackware 14.2 is shipped with 4.4.14 kernel.
Seems you still runing 3.10.17 kernel from 14.1, please test the output of 'uname -r'.
Are you upgrade/install new kernel-* packages version 4.4.14:

Code:

$ ( cd /var/adm/packages ; ls kernel-* )

If yes,
- for MBR: are you rerun 'lilo' (may be after some edits on /etc/lilo.conf) to update the boot code?
- for UEFI: are you copy kernel to EFI partition?

netfoot · 07-12-2016, 07:21 AM

Quote:

Originally Posted by bormant

Slackware 14.2 is shipped with 4.4.14 kernel.
Seems you still runing 3.10.17 kernel from 14.1, please test the output of 'uname -r'.

4.4.14

Quote:

Are you upgrade/install new kernel-* packages version 4.4.14:

Code:

$ ( cd /var/adm/packages ; ls kernel-* )

kernel-firmware-20160628git-noarch-1 kernel-headers-4.4.14-x86-1 kernel-modules-4.4.14-x86_64-1
kernel-generic-4.4.14-x86_64-1 kernel-huge-4.4.14-x86_64-1 kernel-source-4.4.14-noarch-1

Quote:

If yes,
- for MBR: are you rerun 'lilo' (may be after some edits on /etc/lilo.conf) to update the boot code?
- for UEFI: are you copy kernel to EFI partition?

After the upgrade to 14.2, I followed the instructions listed here, to (re)installed GRUB2. I thought that was sufficient?

Didier Spaier · 07-12-2016, 08:39 AM

It seems that you forgot to rebuild the VirtualBox kernel modules for your running (4.4.14) kernel then. To check, please provide the output of

Code:

 bash-4.3$ ls -l /lib/modules/4.4.14/misc/

If it is empty, or gives an error message like this one:

Code:

ls: cannot access '/lib/modules/4.4.14/misc: No such file or directory

you need to rebuild the VirtualBox kernel modules against 4.4.14 and install them.

bormant · 07-12-2016, 09:21 AM

Quote:

Originally Posted by netfoot

I thought that was sufficient?

Sure.
virtualbox-kernel-5.0.14_4.4.14-x86_64-1_SBo.txz http://rgho.st/8pY8tGdrh