VirtualBox Kernel Module no longer builds under -current kernel update of 17-Nov-2017

willysr · 11-18-2017, 06:59 PM

I tested that patch for 5.2.0, not for 5.1.31, FYI

Aeterna · 11-18-2017, 11:58 PM

Quote:

Originally Posted by brobr

Ok, I checked dmesg and also had the vboxpci symbol not found error:

Code:

bash-4.4$ dmesg | grep vboxpci
[   29.387902] vboxpci: Unknown symbol vfs_write (err 0)
bash-4.4$ sudo dmesg | grep vbox
[   29.164508] vboxdrv: loading out-of-tree module taints kernel.
[   29.167423] vboxdrv: Found 8 processor cores
[   29.183188] vboxdrv: TSC mode is Invariant, tentative frequency 2807999980 Hz
[   29.183188] vboxdrv: Successfully loaded version 5.1.31 (interface 0x002a0000)
[   29.387902] vboxpci: Unknown symbol vfs_write (err 0)

Then only applied this part of Willy's patch changing vfs_write (the changes for /vboxnetflt/linux/VBoxNetFlt-linux.c did not need to be made for 5.1.31)

rerun setup and checked dmesg again:

Code:

bash-4.4$ /etc/init.d/vboxdrv setup
vboxdrv.sh: Stopping VirtualBox services.
vboxdrv.sh: Building VirtualBox kernel modules.
vboxdrv.sh: Starting VirtualBox services.

bash-4.4$ dmesg | grep vboxpci
[28288.373195] vboxdrv: Found 8 processor cores
[28288.389318] vboxdrv: TSC mode is Invariant, tentative frequency 2808000074 Hz
[28288.389319] vboxdrv: Successfully loaded version 5.1.31 (interface 0x002a0000)
[28288.600171] vboxpci: IOMMU not found (not registered)
[28295.540547] vboxdrv: ffffffffc0d27020 VMMR0.r0
[28295.619362] vboxdrv: ffffffffc0988020 VBoxDDR0.r0

HTH

thank you brobr

Quote:

[28288.600171] vboxpci: IOMMU not found (not registered)

this means that you don't have virtualization enabled in BIOS?

After applying your patch I see

Quote:

sudo dmesg | grep vbo
[ 13.655437] vboxdrv: loading out-of-tree module taints kernel.
[ 13.657976] vboxdrv: Found 8 processor cores
[ 13.674202] vboxdrv: TSC mode is Invariant, tentative frequency 2693762403 Hz
[ 13.674203] vboxdrv: Successfully loaded version 5.1.31 (interface 0x002a0000)
[ 13.880785] vboxpci: IOMMU found

Unless you disabled VT-d?

Geremia · 11-19-2017, 12:11 AM

When building VirtualBox 5.2.10 on Slackware-current with 4.14.0 kernel (with the SlackBuild), I had to comment out the patch lines and couldn't build VBoxFUSE, but everything else worked (esp. with Willy's patch for the kernel modules).

Paulo2 · 11-19-2017, 09:11 AM

Quote:

Originally Posted by willysr

I have a working patch here https://github.com/willysr/SlackHack...box/5.2.0/4.14

Thanks willysr, works like a charm

Code:

# sh VirtualBox-5.2.0-118431-Linux_amd64.run 
Verifying archive integrity... All good.
Uncompressing VirtualBox for Linux installation.............
VirtualBox Version 5.2.0 r118431 (2017-10-18T06:14:42Z) installer
Installing VirtualBox to /opt/VirtualBox
Python found: python, installing bindings...
vboxdrv.sh: failed: Look at /var/log/vbox-install.log to find out what went wrong.

There were problems setting up VirtualBox.  To re-start the set-up process, run
  /sbin/vboxconfig
as root.

VirtualBox has been installed successfully.

You will find useful information about using VirtualBox in the user manual
  /opt/VirtualBox/UserManual.pdf
and in the user FAQ
  http://www.virtualbox.org/wiki/User_FAQ

We hope that you enjoy using VirtualBox.

The installation log file is at /var/log/vbox-install.log.

Code:

# cd /usr/src/vboxhost-5.2.0
# mv /home/paulo/Downloads/linux-4.14-host.patch .
# patch -p1 < linux-4.14-host.patch 
patching file vboxnetflt/linux/VBoxNetFlt-linux.c
Hunk #1 succeeded at 737 (offset 15 lines).
Hunk #2 succeeded at 1270 (offset 164 lines).
Hunk #3 succeeded at 1520 with fuzz 2 (offset 121 lines).
patching file vboxpci/linux/VBoxPci-linux.c
# /etc/init.d/vboxdrv setup
vboxdrv.sh: Stopping VirtualBox services.
vboxdrv.sh: Building VirtualBox kernel modules.
vboxdrv.sh: Starting VirtualBox services.

brobr · 11-19-2017, 10:15 AM

Quote:

Originally Posted by Aeterna

this means that you don't have virtualization enabled in BIOS?

Hi Aeterna, thanks for noticing this. My processor should support this

Quote:

from: https://ark.intel.com/products/97185/[processor]
..
Intel® Virtualization Technology (VT-x) ‡ Yes
Intel® Virtualization Technology for Directed I/O (VT-d) ‡ Yes
..

But the small print suggests the motherboard/computer might not:

Quote:

‡ This feature may not be available on all computing systems....

With dmicode I cannot see any bios setting for Vt-d:

Code:

bash-4.4# dmidecode 
# dmidecode 3.0
..
BIOS Information
..
	Characteristics:
		PCI is supported
		BIOS is upgradeable
		BIOS shadowing is allowed
		Boot from CD is supported
		Selectable boot is supported
		BIOS ROM is socketed
		EDD is supported
		Print screen service is supported (int 5h)
		8042 keyboard services are supported (int 9h)
		Printer services are supported (int 17h)
		ACPI is supported
		USB legacy is supported
		BIOS boot specification is supported
		Targeted content distribution is supported
		UEFI is supported
	BIOS Revision: 5.12

My laptop only has on-board graphics and there is no free pci-device (like an unused graphics card) I could attach to a VM for which IOMMU (as far as I understand this) is needed.

I never really needed to bother with this part of virtualization...as I get USB pass-through for thumb-drives, internet and only need windows in a vm to run some propriatory software related to some machines we use at my work place.

Aeterna · 11-19-2017, 01:01 PM

Quote:

Originally Posted by brobr

Hi Aeterna, thanks for noticing this. My processor should support this

But the small print suggests the motherboard/computer might not:

With dmicode I cannot see any bios setting for Vt-d:

Code:

bash-4.4# dmidecode 
# dmidecode 3.0
..
BIOS Information
..
	Characteristics:
		PCI is supported
		BIOS is upgradeable
		BIOS shadowing is allowed
		Boot from CD is supported
		Selectable boot is supported
		BIOS ROM is socketed
		EDD is supported
		Print screen service is supported (int 5h)
		8042 keyboard services are supported (int 9h)
		Printer services are supported (int 17h)
		ACPI is supported
		USB legacy is supported
		BIOS boot specification is supported
		Targeted content distribution is supported
		UEFI is supported
	BIOS Revision: 5.12

My laptop only has on-board graphics and there is no free pci-device (like an unused graphics card) I could attach to a VM for which IOMMU (as far as I understand this) is needed.

I never really needed to bother with this part of virtualization...as I get USB pass-through for thumb-drives, internet and only need windows in a vm to run some propriatory software related to some machines we use at my work place.

I do not see any difference with vboxpci/IOMMU on or off either. The only time I was seriously interested in IOMMU was when I was considering Qubes installation, however since Qubes does not have sane way of upgrading yet, I decided to stay with VBox.

joseaaa · 12-07-2017, 06:43 PM

Quote:

Originally Posted by willysr

I have a working patch here

thanks, im about to try this, how do i apply this patch? im pretty new to this...
I had vbox working on kali 2017.1 6 months ago, but i cant seem to make it work now, really frustrating, and not much info online, its all about kali machine...
ive tried everything, and when i try apt install linux headers u name r, its says unable to locate package 4.13.0.

which distribution for the vbox repo do you use: stretch? or jessie, or wheezy

any help is appreciated.

Paulo2 · 12-08-2017, 12:07 PM

VirtualBox 5.2.2 works ok with the new -current testing kernel 4.14.4

Drakeo · 12-08-2017, 12:30 PM

let it build then fail then reboot and use it. 4 files that it builds. first one runs everything it builds. The others are for networking and stuff.
Unless you running a vpn server or need a seperate device for networking you will be fine all the way up to 4.14.4 kernel. if you do not want to reboot then
modprobe vboxdrv and have fun. Untill they patch them for the 4.14 you are stuck with everything working and shared file. But not network devices.

Drakeo · 12-08-2017, 12:33 PM

Quote:

Originally Posted by Paulo2

VirtualBox 5.2.2 works ok with the new -current testing kernel 4.14.4

you got the guest extensions to build ? all 4

dugan · 12-08-2017, 01:44 PM

I built the guest additions kernel module just fine last night, after upgrading to the latest 4.9.

Drakeo · 12-08-2017, 01:45 PM

Quote:

Originally Posted by dugan

I built the guest additions kernel module just fine last night, after upgrading to the latest 4.9.

Thanks for the update 4.9 has been building fine a long time think we are discussing 4.14

cwizardone · 12-08-2017, 02:19 PM

Quote:

Originally Posted by Paulo2

VirtualBox 5.2.2 works ok with the new -current testing kernel 4.14.4

Ditto.
I found it best to first use the uninstall.sh file in
/opt/VirtualBox and once the new kernel is installed, re-install VirtualBox. Works fine and it is not necessary to re-install the extension (if you already had it installed).

Paulo2 · 12-08-2017, 02:30 PM

Quote:

Originally Posted by Drakeo

you got the guest extensions to build ? all 4

The additions iso file? Or the extension pack?
Both installs ok.
I install from the .run file, not from SBo.
Inside a Debian VM (I use it regularly), guest extensions are built ok, I guess.
There isn't any error message.

Paulo2 · 12-08-2017, 02:33 PM

Quote:

Originally Posted by cwizardone

Ditto.
I found it best to first use the uninstall.sh file in
/opt/VirtualBox and once the new kernel is installed, re-install VirtualBox. Works fine and it is not necessary to re-install the extension (if you already had it installed).

That is what I do too.
I just installed the additions iso file to see if it would install ok to post an answer for Drakeo.
The Debian VM was still with some 5.1 additional "things" but was working ok, at least the video driver.