Discussion:
Virtulisation
(too old to reply)
Peter Chant
2018-06-21 07:22:48 UTC
Permalink
Raw Message
Does anyone have a working virtulisation solution and if so what? I
don't mean lxc, docker or other containers.

I'm running Slackware 14.2. I can't get Virtualbox to build. Qemu
builds but I have no graphics output on X. I rebuilt it and it built
SDL2, but still no output.

Given that my install is old I did a fresh install of current (dual
boot) and I can't get Virtualbox built there either. I've also tried a
binary direct from oracle, which gives an error there, despite kernel
modules being loaded.

I've not tried qemu yet on current.

Dual (triple?) booting to Mint and running MX Linux in a virtual machine
worked fine and was amazingly snappy. I want to repeat this on slackware.

Running, at present, a 4.16.16 kernel, config originally based on one of
the slackware ones.

Pete
Giovanni
2018-06-21 14:37:42 UTC
Permalink
Raw Message
Post by Peter Chant
Does anyone have a working virtulisation solution and if so what? I
don't mean lxc, docker or other containers.
I'm running Slackware 14.2. I can't get Virtualbox to build. Qemu
builds but I have no graphics output on X. I rebuilt it and it built
SDL2, but still no output.
Given that my install is old I did a fresh install of current (dual
boot) and I can't get Virtualbox built there either. I've also tried a
binary direct from oracle, which gives an error there, despite kernel
modules being loaded.
I've not tried qemu yet on current.
Dual (triple?) booting to Mint and running MX Linux in a virtual machine
worked fine and was amazingly snappy. I want to repeat this on slackware.
Running, at present, a 4.16.16 kernel, config originally based on one of
the slackware ones.
Pete
I got virtualbox working by compiling it from the slackbuild scripts
available at 'https://slackbuilds.org/'

The only problem is that you need to have the kernel build environment
on your machine.

Ciao
Giovanni
--
A computer is like an air conditioner,
it stops working when you open Windows.
< http://giovanni.homelinux.net/ >
Peter Chant
2018-06-21 21:47:50 UTC
Permalink
Raw Message
Post by Giovanni
I got virtualbox working by compiling it from the slackbuild scripts
available at 'https://slackbuilds.org/'
The only problem is that you need to have the kernel build environment
on your machine.
I've got it. However, no luck with the slackbuild on current. Trying
it on my 14.2 install if fails. I've tried it in this 14.2 install,
from within current and within the lxc -current container used to build
the kernel.

I suppose I could wipe a spare drive and try a completely vanila
install. But fundamentally I need it working with the kernel I am running.

Example fail:

make[2]: Entering directory
'/var/lib/lxc/slc-build2/rootfs/usr/src/linux-4.16.16'
CC [M] /tmp_hdd/SBo/virtualbox-kernel-5.0.40/vboxdrv/linux/SUPDrv-linux.o
In file included from ./include/linux/atomic.h:5:0,
from ./include/linux/jump_label.h:189,
from ./arch/x86/include/asm/string_64.h:6,
from ./arch/x86/include/asm/string.h:5,
from ./include/linux/string.h:20,
from
/tmp_hdd/SBo/virtualbox-kernel-5.0.40/vboxdrv/include/iprt/string.h:37,
from
/tmp_hdd/SBo/virtualbox-kernel-5.0.40/vboxdrv/linux/../SUPDrvInternal.h:43,
from
/tmp_hdd/SBo/virtualbox-kernel-5.0.40/vboxdrv/linux/SUPDrv-linux.c:32:
./arch/x86/include/asm/atomic.h: In function 'atomic_try_cmpxchg':
./arch/x86/include/asm/atomic.h:193:2: error: undefined named operand 'new'
return try_cmpxchg(&v->counter, old, new);
^
./arch/x86/include/asm/atomic.h:193:2: error: undefined named operand 'new'
./arch/x86/include/asm/atomic.h:193:2: error: undefined named operand 'new'
./arch/x86/include/asm/atomic.h:193:2: error: undefined named operand 'new'
In file included from ./arch/x86/include/asm/atomic.h:276:0,
from ./include/linux/atomic.h:5,
from ./include/linux/jump_label.h:189,
from ./arch/x86/include/asm/string_64.h:6,
from ./arch/x86/include/asm/string.h:5,
from ./include/linux/string.h:20,
from
/tmp_hdd/SBo/virtualbox-kernel-5.0.40/vboxdrv/include/iprt/string.h:37,
from
/tmp_hdd/SBo/virtualbox-kernel-5.0.40/vboxdrv/linux/../SUPDrvInternal.h:43,
from
/tmp_hdd/SBo/virtualbox-kernel-5.0.40/vboxdrv/linux/SUPDrv-linux.c:32:
./arch/x86/include/asm/atomic64_64.h: In function 'atomic64_try_cmpxchg':
./arch/x86/include/asm/atomic64_64.h:183:2: error: undefined named
operand 'new'
return try_cmpxchg(&v->counter, old, new);
^
./arch/x86/include/asm/atomic64_64.h:183:2: error: undefined named
operand 'new'
./arch/x86/include/asm/atomic64_64.h:183:2: error: undefined named
operand 'new'
./arch/x86/include/asm/atomic64_64.h:183:2: error: undefined named
operand 'new'
scripts/Makefile.build:324: recipe for target
'/tmp_hdd/SBo/virtualbox-kernel-5.0.40/vboxdrv/linux/SUPDrv-linux.o' failed
make[3]: ***
[/tmp_hdd/SBo/virtualbox-kernel-5.0.40/vboxdrv/linux/SUPDrv-linux.o] Error 1
Makefile:1561: recipe for target
'_module_/tmp_hdd/SBo/virtualbox-kernel-5.0.40/vboxdrv' failed
make[2]: *** [_module_/tmp_hdd/SBo/virtualbox-kernel-5.0.40/vboxdrv] Error 2
make[2]: Leaving directory
'/var/lib/lxc/slc-build2/rootfs/usr/src/linux-4.16.16'
Makefile:299: recipe for target 'vboxdrv' failed
make[1]: *** [vboxdrv] Error 2
make[1]: Leaving directory '/tmp_hdd/SBo/virtualbox-kernel-5.0.40/vboxdrv'
Makefile:39: recipe for target 'all' failed
make: *** [all] Error 2
Alexander Grotewohl
2018-06-23 14:38:49 UTC
Permalink
Raw Message
Post by Peter Chant
Post by Giovanni
I got virtualbox working by compiling it from the slackbuild scripts
available at 'https://slackbuilds.org/'
The only problem is that you need to have the kernel build environment
on your machine.
I've got it. However, no luck with the slackbuild on current. Trying
it on my 14.2 install if fails. I've tried it in this 14.2 install,
from within current and within the lxc -current container used to build
the kernel.
I suppose I could wipe a spare drive and try a completely vanila
install. But fundamentally I need it working with the kernel I am running.
make[2]: Entering directory
'/var/lib/lxc/slc-build2/rootfs/usr/src/linux-4.16.16'
CC [M] /tmp_hdd/SBo/virtualbox-kernel-5.0.40/vboxdrv/linux/SUPDrv-linux.o
In file included from ./include/linux/atomic.h:5:0,
from ./include/linux/jump_label.h:189,
from ./arch/x86/include/asm/string_64.h:6,
from ./arch/x86/include/asm/string.h:5,
from ./include/linux/string.h:20,
from
/tmp_hdd/SBo/virtualbox-kernel-5.0.40/vboxdrv/include/iprt/string.h:37,
from
/tmp_hdd/SBo/virtualbox-kernel-5.0.40/vboxdrv/linux/../SUPDrvInternal.h:43,
from
./arch/x86/include/asm/atomic.h:193:2: error: undefined named operand 'new'
return try_cmpxchg(&v->counter, old, new);
^
./arch/x86/include/asm/atomic.h:193:2: error: undefined named operand 'new'
./arch/x86/include/asm/atomic.h:193:2: error: undefined named operand 'new'
./arch/x86/include/asm/atomic.h:193:2: error: undefined named operand 'new'
In file included from ./arch/x86/include/asm/atomic.h:276:0,
from ./include/linux/atomic.h:5,
from ./include/linux/jump_label.h:189,
from ./arch/x86/include/asm/string_64.h:6,
from ./arch/x86/include/asm/string.h:5,
from ./include/linux/string.h:20,
from
/tmp_hdd/SBo/virtualbox-kernel-5.0.40/vboxdrv/include/iprt/string.h:37,
from
/tmp_hdd/SBo/virtualbox-kernel-5.0.40/vboxdrv/linux/../SUPDrvInternal.h:43,
from
./arch/x86/include/asm/atomic64_64.h:183:2: error: undefined named
operand 'new'
return try_cmpxchg(&v->counter, old, new);
^
./arch/x86/include/asm/atomic64_64.h:183:2: error: undefined named
operand 'new'
./arch/x86/include/asm/atomic64_64.h:183:2: error: undefined named
operand 'new'
./arch/x86/include/asm/atomic64_64.h:183:2: error: undefined named
operand 'new'
scripts/Makefile.build:324: recipe for target
'/tmp_hdd/SBo/virtualbox-kernel-5.0.40/vboxdrv/linux/SUPDrv-linux.o' failed
make[3]: ***
[/tmp_hdd/SBo/virtualbox-kernel-5.0.40/vboxdrv/linux/SUPDrv-linux.o] Error 1
Makefile:1561: recipe for target
'_module_/tmp_hdd/SBo/virtualbox-kernel-5.0.40/vboxdrv' failed
make[2]: *** [_module_/tmp_hdd/SBo/virtualbox-kernel-5.0.40/vboxdrv] Error 2
make[2]: Leaving directory
'/var/lib/lxc/slc-build2/rootfs/usr/src/linux-4.16.16'
Makefile:299: recipe for target 'vboxdrv' failed
make[1]: *** [vboxdrv] Error 2
make[1]: Leaving directory '/tmp_hdd/SBo/virtualbox-kernel-5.0.40/vboxdrv'
Makefile:39: recipe for target 'all' failed
make: *** [all] Error 2
Why the special kernel? It's pretty likely that's the problem. And as an
aside, slackbuilds are not for -current.
Peter Chant
2018-06-24 13:36:10 UTC
Permalink
Raw Message
Post by Alexander Grotewohl
Why the special kernel? It's pretty likely that's the problem. And as an
aside, slackbuilds are not for -current.
I'm using btrfs and if I have problems then the btrfs mailing list is
much more forthcoming if you have a recent kernel.


I tried installing -current to see if 14.2 was too old to support
virtualbox. As you can see I'm having trouble with that. However, all
the slackbuilds I tried were fine - but I do realise breakage is possible.

Pete
root
2018-06-21 15:04:40 UTC
Permalink
Raw Message
Post by Peter Chant
Does anyone have a working virtulisation solution and if so what? I
don't mean lxc, docker or other containers.
I'm running Slackware 14.2. I can't get Virtualbox to build. Qemu
builds but I have no graphics output on X. I rebuilt it and it built
SDL2, but still no output.
Given that my install is old I did a fresh install of current (dual
boot) and I can't get Virtualbox built there either. I've also tried a
binary direct from oracle, which gives an error there, despite kernel
modules being loaded.
I've not tried qemu yet on current.
Dual (triple?) booting to Mint and running MX Linux in a virtual machine
worked fine and was amazingly snappy. I want to repeat this on slackware.
Running, at present, a 4.16.16 kernel, config originally based on one of
the slackware ones.
Pete
It been quite I while since I used Virtualbox, but I seem to remember
you get a binary directory directly :
http://www.oracle.com/technetwork/server-storage/virtualbox/downloads/index.html
dillinger
2018-06-21 15:50:20 UTC
Permalink
Raw Message
Post by root
Post by Peter Chant
Does anyone have a working virtulisation solution and if so what? I
don't mean lxc, docker or other containers.
I'm running Slackware 14.2. I can't get Virtualbox to build. Qemu
builds but I have no graphics output on X. I rebuilt it and it built
SDL2, but still no output.
Given that my install is old I did a fresh install of current (dual
boot) and I can't get Virtualbox built there either. I've also tried a
binary direct from oracle, which gives an error there, despite kernel
modules being loaded.
I've not tried qemu yet on current.
Dual (triple?) booting to Mint and running MX Linux in a virtual machine
worked fine and was amazingly snappy. I want to repeat this on slackware.
Running, at present, a 4.16.16 kernel, config originally based on one of
the slackware ones.
Pete
It been quite I while since I used Virtualbox, but I seem to remember
http://www.oracle.com/technetwork/server-storage/virtualbox/downloads/index.html
True, for Slackware you need the "run installer" at the bottom of the
list. But it does want to build kernel modules for your kernel, so you
have to have the kernel source installed when you run the installer.
Peter Chant
2018-06-21 23:07:30 UTC
Permalink
Raw Message
Post by dillinger
Post by root
It been quite I while since I used Virtualbox, but I seem to remember
http://www.oracle.com/technetwork/server-storage/virtualbox/downloads/index.html
True, for Slackware you need the "run installer" at the bottom of the
list. But it does want to build kernel modules for your kernel, so you
have to have the kernel source installed when you run the installer.
Yes. On currengt it builds the kernel modules and the Gui runs fine.
But on starting a virtual machine it bangs out with an error message.

On -14.2 /sbin/vboxconfig fails to build the prerequisite kernel modules.

/bin/sh: ./scripts/recordmcount: No such file or directory
scripts/Makefile.build:324: recipe for target '/tmp/vbox.0/SUPDrv.o' failed
make[2]: *** [/tmp/vbox.0/SUPDrv.o] Error 1
make[2]: *** wait: No child processes. Stop.
Makefile:1561: recipe for target '_module_/tmp/vbox.0' failed
make[1]: *** [_module_/tmp/vbox.0] Error 2
/tmp/vbox.0/Makefile.include.footer:101: recipe for target 'vboxdrv' failed
make: *** [vboxdrv] Error 2


This thing is fighting me hard.
dillinger
2018-06-22 01:08:42 UTC
Permalink
Raw Message
Post by Peter Chant
Post by dillinger
Post by root
It been quite I while since I used Virtualbox, but I seem to remember
http://www.oracle.com/technetwork/server-storage/virtualbox/downloads/index.html
True, for Slackware you need the "run installer" at the bottom of the
list. But it does want to build kernel modules for your kernel, so you
have to have the kernel source installed when you run the installer.
Yes. On currengt it builds the kernel modules and the Gui runs fine.
But on starting a virtual machine it bangs out with an error message.
On -14.2 /sbin/vboxconfig fails to build the prerequisite kernel modules.
/bin/sh: ./scripts/recordmcount: No such file or directory
scripts/Makefile.build:324: recipe for target '/tmp/vbox.0/SUPDrv.o' failed
make[2]: *** [/tmp/vbox.0/SUPDrv.o] Error 1
make[2]: *** wait: No child processes. Stop.
Makefile:1561: recipe for target '_module_/tmp/vbox.0' failed
make[1]: *** [_module_/tmp/vbox.0] Error 2
/tmp/vbox.0/Makefile.include.footer:101: recipe for target 'vboxdrv' failed
make: *** [vboxdrv] Error 2
This thing is fighting me hard.
recordmcount is part of the kernel source, at least it is on 14.2.

How did you install 14.2, everything but the kitchen sink or less?
dillinger
2018-06-22 02:32:47 UTC
Permalink
Raw Message
Post by dillinger
Post by dillinger
Post by root
It been quite I while since I used Virtualbox, but I seem to remember
http://www.oracle.com/technetwork/server-storage/virtualbox/downloads/index.html
True, for Slackware you need the "run installer" at the bottom of the
list. But it does want to build kernel modules for your kernel, so you
have to have the kernel source installed when you run the installer.
Yes.  On currengt it builds the kernel modules and the Gui runs fine.
But on starting a virtual machine it bangs out with an error message.
On -14.2 /sbin/vboxconfig fails to build the prerequisite kernel modules.
/bin/sh: ./scripts/recordmcount: No such file or directory
scripts/Makefile.build:324: recipe for target '/tmp/vbox.0/SUPDrv.o' failed
make[2]: *** [/tmp/vbox.0/SUPDrv.o] Error 1
make[2]: *** wait: No child processes.  Stop.
Makefile:1561: recipe for target '_module_/tmp/vbox.0' failed
make[1]: *** [_module_/tmp/vbox.0] Error 2
/tmp/vbox.0/Makefile.include.footer:101: recipe for target 'vboxdrv' failed
make: *** [vboxdrv] Error 2
This thing is fighting me hard.
recordmcount is part of the kernel source, at least it is on 14.2.
How did you install 14.2, everything but the kitchen sink or less?
Sorry, how did you install -current? There may be some packages missing.
Peter Chant
2018-06-22 11:59:13 UTC
Permalink
Raw Message
Post by dillinger
Post by dillinger
Post by Peter Chant
This thing is fighting me hard.
recordmcount is part of the kernel source, at least it is on 14.2.
Thank you - perhaps this is path to the fix.
Post by dillinger
Post by dillinger
How did you install 14.2, everything but the kitchen sink or less?
Sorry, how did you install -current? There may be some packages missing.
I created a btrfs subvolume in the drive I'm using for root and used
installpkg to install into there. I installed everything. Then I
booted from a USB stick with syslinux and my own kernel.


I've just dived into that subvolume. recordmcount is present in
/usr/src/linux-4.16.16/scripts/recordmcount

I think I'm having problems that I'm likely failing to get virtualbox
running on at least two separate installs at once which does not aid
clarity.

I've just reinstalled the 4.14.50 source (slackware package) into
current and it is in there. However, comparing it with a vanilla kernel
source tree it appears to be produced as part of the kernel build
process. No use having just a fresh source tree present.

OK, switching my existing 14.2 install..

OK. Having built a 4.16.16 kernel now on _this_ machine to ensure the
file exists, though not installed it as it is already running 4.16.16.
I have the modules and ensured they are in use with modprobe I am
getting the stuff below.

Wondering if I should do a bare metal clean install of sag 14.2 and see
what happens. But I'd rather get it running on this install, or a new
-current machine. My -current install was suppeded to be that machine!
It also seemed to have similar errors to the below.



Result Code:
NS_ERROR_FAILURE (0x80004005)
Component:
SessionMachine
Interface:
ISession {7844aa05-b02e-4cdd-a04f-ade4a762e6b7}

And the log gives:
VirtualBox VM 5.2.12 r122591 linux.amd64 (May 9 2018 12:50:22) release log
00:00:00.318245 Log opened 2018-06-22T11:53:17.173647000Z
00:00:00.318246 Build Type: release
00:00:00.318249 OS Product: Linux
00:00:00.318250 OS Release: 4.16.16
00:00:00.318250 OS Version: #1 SMP Tue Jun 19 23:50:47 BST 2018
00:00:00.318267 DMI Product Name: System Product Name
00:00:00.318271 DMI Product Version: System Version
00:00:00.318300 Host RAM: 15936MB (15.5GB) total, 10657MB (10.4GB) available
00:00:00.318304 Executable: /opt/VirtualBox/VirtualBox
00:00:00.318304 Process ID: 31610
00:00:00.318305 Package type: LINUX_64BITS_GENERIC
00:00:00.585272 Installed Extension Packs:
00:00:00.585303 None installed!
00:00:00.586002 Console: Machine state changed to 'Starting'
00:00:00.586180 Qt version: 5.6.1
00:00:00.586186 X11 Window Manager code: 3
00:00:00.591165 SUP: Loaded VMMR0.r0 (/opt/VirtualBox/VMMR0.r0) at
0xXXXXXXXXXXXXXXXX - ModuleInit at XXXXXXXXXXXXXXXX and ModuleTerm at
XXXXXXXXXXXXXXXX
00:00:00.591185 SUP: VMMR0EntryEx located at XXXXXXXXXXXXXXXX and
VMMR0EntryFast at XXXXXXXXXXXXXXXX
00:00:00.591311
00:00:00.591312 !!Assertion Failed!!
00:00:00.591312 Expression: pVM->pVMR0 == CreateVMReq.pVMR0
00:00:00.591312 Location :
/home/vbox/tinderbox/5.2-lnx64-rel/src/VBox/VMM/VMMR3/VM.cpp(620) int
vmR3CreateU(UVM*, uint32_t, int (*)(UVM*, VM*, void*), void*)
Henrik Carlqvist
2018-06-22 19:29:23 UTC
Permalink
Raw Message
Post by Peter Chant
Does anyone have a working virtulisation solution and if so what?
I have qemu version 2.6.2 running on Slackware 14.2.
Post by Peter Chant
Qemu builds but I have no graphics output on X. I rebuilt it and it
built SDL2, but still no output.
I don't remember for sure how I built qemu, maybe I have some notes about
that at work.

However, qemu can take a lot of different command line options. I am able
to start qemu both with the option "-display sdl" and the option
"-display gtk" which seems to be the default. I am even able to start
with "-display curses" which does not need any X window at all.

regards Henrik
Peter Chant
2018-06-23 08:52:27 UTC
Permalink
Raw Message
Post by Henrik Carlqvist
Post by Peter Chant
Qemu builds but I have no graphics output on X. I rebuilt it and it
built SDL2, but still no output.
I don't remember for sure how I built qemu, maybe I have some notes about
that at work.
However, qemu can take a lot of different command line options. I am able
to start qemu both with the option "-display sdl" and the option
"-display gtk" which seems to be the default. I am even able to start
with "-display curses" which does not need any X window at all.
I found the issue. Qemu defaults to 64MB ram. In 2018 nothing I tried
can boot to X with this little!

Display looks like it struggles (not as smooth) a bit compared to
native, but youtube plays fine and no noticeable lag on keyboard and mouse.

Pete
Henrik Carlqvist
2018-06-23 10:01:50 UTC
Permalink
Raw Message
Post by Peter Chant
I found the issue. Qemu defaults to 64MB ram. In 2018 nothing I tried
can boot to X with this little!
Display looks like it struggles (not as smooth) a bit compared to
native, but youtube plays fine and no noticeable lag on keyboard and mouse.
There are different graphics hardware to emulate with qemu. I haven't
tried to do any such graphics intensive like playing youtube, but I guess
I would have to use something like "-vga vmware" or "-vga virtio" for
that.

I haven't tried it myself, but qemu is even able to use a (perhaps spare)
graphics card in the host computer with passtrhough.

regards Henrik
Peter Chant
2018-06-24 13:39:58 UTC
Permalink
Raw Message
Post by Henrik Carlqvist
Post by Peter Chant
I found the issue. Qemu defaults to 64MB ram. In 2018 nothing I tried
can boot to X with this little!
Display looks like it struggles (not as smooth) a bit compared to
native, but youtube plays fine and no noticeable lag on keyboard and mouse.
There are different graphics hardware to emulate with qemu. I haven't
tried to do any such graphics intensive like playing youtube, but I guess
I would have to use something like "-vga vmware" or "-vga virtio" for
that.
Thanks. I've been playing a little with various options.
Post by Henrik Carlqvist
I haven't tried it myself, but qemu is even able to use a (perhaps spare)
graphics card in the host computer with passtrhough.
I'm aware of that - that is a thought if I find that I need to run
something frequently and need a bit more graphics power.

Pete

Loading...