You are not logged in.

Pages: 1

#1 2015-10-31 08:44:07

Suncatcher
Banned
Registered: 2015-03-30
Posts: 36

[SOLVED] Virtualbox service doesn't start

After the last upgrade of Arch and further update of vbox packages I get this output of vboxservice status

vboxservice.service - VirtualBox Guest Service
   Loaded: loaded (/usr/lib/systemd/system/vboxservice.service; enabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since Sat 2015-10-31 10:35:50 MSK; 29min ago
  Process: 268 ExecStart=/usr/bin/VBoxService -f (code=exited, status=1/FAILURE)
  Process: 262 ExecStartPre=/usr/bin/modprobe vboxsf (code=exited, status=1/FAILURE)
  Process: 257 ExecStartPre=/usr/bin/modprobe vboxvideo (code=exited, status=1/FAILURE)
  Process: 253 ExecStartPre=/usr/bin/modprobe vboxguest (code=exited, status=1/FAILURE)
Main PID: 268 (code=exited, status=1/FAILURE)

Oct 31 10:35:49 localhost systemd[1]: Starting VirtualBox Guest Service...
Oct 31 10:35:49 localhost modprobe[253]: modprobe: ERROR: could not insert 'vboxguest': Exec format error
Oct 31 10:35:49 localhost modprobe[257]: modprobe: ERROR: could not insert 'vboxvideo': Exec format error
Oct 31 10:35:49 localhost modprobe[262]: modprobe: ERROR: could not insert 'vboxsf': Exec format error
Oct 31 10:35:49 localhost systemd[1]: Started VirtualBox Guest Service.
Oct 31 10:35:50 localhost VBoxService[268]: VBoxService: error: VbglR3Init failed with rc=VERR_FILE_NOT_FOUND
Oct 31 10:35:50 localhost systemd[1]: vboxservice.service: Main process exited, code=exited, status=1/FAILURE
Oct 31 10:35:50 localhost systemd[1]: vboxservice.service: Unit entered failed state.
Oct 31 10:35:50 localhost systemd[1]: vboxservice.service: Failed with result 'exit-code'.

How can I fix this?

Last edited by Suncatcher (2015-10-31 14:25:57)

Offline

#2 2015-10-31 11:21:36

olive
Member
From: Belgium
Registered: 2008-06-22
Posts: 1,490

Re: [SOLVED] Virtualbox service doesn't start

Be sure your system is up to date. Try to modprobe the modules by hand (vboxguest, vboxvideo, vboxsf) and see what happen. If that does not work, then this is a bug in the package that provide non compatible module. Report the bug. As a temporary workaround, you can simply install the linux-lts kernel and virtualbox-guest-modules-lts.

Also, uninstall virtualbox-guest-dkms if you have it. The purpose of which is to automatically recompile the modules if you don't use the official kernel. If it is indeed the case, then I presume you have an incompatibility between your running kernel and the modules and fixing it might not be trivial. Anyway, in this last case, you should recompile the module by hand and see what happen.

Last edited by olive (2015-10-31 11:26:36)

Offline

#3 2015-10-31 11:56:11

Suncatcher
Banned
Registered: 2015-03-30
Posts: 36

Re: [SOLVED] Virtualbox service doesn't start

olive wrote:

Try to modprobe the modules by hand (vboxguest, vboxvideo, vboxsf) and see what happen

I get this

modprobe: ERROR: could not insert 'vboxsf': Exec format error
modprobe: ERROR: could not insert 'vboxvideo': Exec format error
modprobe: ERROR: could not insert 'vboxguest': Exec format error

And if I review the systemd journal I see this

Oct 31 10:35:44 localhost kernel: ACPI: RSDP 0x00000000000E0000 000024 (v02 VBOX  )
Oct 31 10:35:45 localhost kernel: ACPI: XSDT 0x00000000DFFF0030 00003C (v01 VBOX   VBOXXSDT 00000001 ASL  00000061)
Oct 31 10:35:45 localhost kernel: ACPI: FACP 0x00000000DFFF00F0 0000F4 (v04 VBOX   VBOXFACP 00000001 ASL  00000061)
Oct 31 10:35:45 localhost kernel: ACPI: DSDT 0x00000000DFFF0470 001BF1 (v01 VBOX   VBOXBIOS 00000002 INTL 20100528)
Oct 31 10:35:45 localhost kernel: ACPI: APIC 0x00000000DFFF0240 00005C (v02 VBOX   VBOXAPIC 00000001 ASL  00000061)
Oct 31 10:35:45 localhost kernel: ACPI: SSDT 0x00000000DFFF02A0 0001CC (v01 VBOX   VBOXCPUT 00000002 INTL 20100528)
Oct 31 10:35:45 localhost kernel: ata2.00: ATAPI: VBOX CD-ROM, 1.0, max UDMA/133
Oct 31 10:35:45 localhost kernel: scsi 1:0:0:0: CD-ROM            VBOX     CD-ROM           1.0  PQ: 0 ANSI: 5
Oct 31 10:35:45 localhost kernel: ata3.00: ATA-6: VBOX HARDDISK, 1.0, max UDMA/133
Oct 31 10:35:45 localhost kernel: scsi 2:0:0:0: Direct-Access     ATA      VBOX HARDDISK    1.0  PQ: 0 ANSI: 5
Oct 31 10:35:46 localhost kernel: vboxguest: disagrees about version of symbol module_layout
Oct 31 10:35:46 localhost kernel: vboxvideo: disagrees about version of symbol module_layout
Oct 31 10:35:46 localhost systemd[1]: Found device VBOX_HARDDISK Home.
Oct 31 10:35:49 localhost kernel: vboxguest: disagrees about version of symbol module_layout
Oct 31 10:35:49 localhost modprobe[253]: modprobe: ERROR: could not insert 'vboxguest': Exec format error
Oct 31 10:35:49 localhost kernel: vboxvideo: disagrees about version of symbol module_layout
Oct 31 10:35:49 localhost modprobe[257]: modprobe: ERROR: could not insert 'vboxvideo': Exec format error
Oct 31 10:35:49 localhost modprobe[262]: modprobe: ERROR: could not insert 'vboxsf': Exec format error
Oct 31 10:35:49 localhost kernel: vboxguest: disagrees about version of symbol module_layout
Oct 31 10:35:50 localhost VBoxService[268]: VBoxService: error: VbglR3Init failed with rc=VERR_FILE_NOT_FOUND
Oct 31 10:35:50 localhost systemd[1]: vboxservice.service: Main process exited, code=exited, status=1/FAILURE
Oct 31 10:35:50 localhost systemd[1]: vboxservice.service: Unit entered failed state.
Oct 31 10:35:50 localhost systemd[1]: vboxservice.service: Failed with result 'exit-code'.
Oct 31 14:22:51 localhost kernel: ACPI: RSDP 0x00000000000E0000 000024 (v02 VBOX  )
Oct 31 14:22:51 localhost kernel: ACPI: XSDT 0x00000000DFFF0030 00003C (v01 VBOX   VBOXXSDT 00000001 ASL  00000061)
Oct 31 14:22:51 localhost kernel: ACPI: FACP 0x00000000DFFF00F0 0000F4 (v04 VBOX   VBOXFACP 00000001 ASL  00000061)
Oct 31 14:22:51 localhost kernel: ACPI: DSDT 0x00000000DFFF0470 001BF1 (v01 VBOX   VBOXBIOS 00000002 INTL 20100528)
Oct 31 14:22:51 localhost kernel: ACPI: APIC 0x00000000DFFF0240 00005C (v02 VBOX   VBOXAPIC 00000001 ASL  00000061)
Oct 31 14:22:51 localhost kernel: ACPI: SSDT 0x00000000DFFF02A0 0001CC (v01 VBOX   VBOXCPUT 00000002 INTL 20100528)
Oct 31 14:22:52 localhost kernel: ata2.00: ATAPI: VBOX CD-ROM, 1.0, max UDMA/133
Oct 31 14:22:52 localhost kernel: scsi 1:0:0:0: CD-ROM            VBOX     CD-ROM           1.0  PQ: 0 ANSI: 5
Oct 31 14:22:52 localhost kernel: ata3.00: ATA-6: VBOX HARDDISK, 1.0, max UDMA/133
Oct 31 14:22:52 localhost kernel: scsi 2:0:0:0: Direct-Access     ATA      VBOX HARDDISK    1.0  PQ: 0 ANSI: 5
Oct 31 14:22:52 localhost kernel: vboxguest: disagrees about version of symbol module_layout
Oct 31 14:22:52 localhost kernel: vboxvideo: disagrees about version of symbol module_layout
Oct 31 14:22:52 localhost systemd[1]: Found device VBOX_HARDDISK Home.
Oct 31 14:22:54 localhost modprobe[247]: modprobe: ERROR: could not insert 'vboxguest': Exec format error
Oct 31 14:22:54 localhost kernel: vboxguest: disagrees about version of symbol module_layout
Oct 31 14:22:55 localhost modprobe[270]: modprobe: ERROR: could not insert 'vboxvideo': Exec format error
Oct 31 14:22:55 localhost kernel: vboxvideo: disagrees about version of symbol module_layout
Oct 31 14:22:55 localhost modprobe[272]: modprobe: ERROR: could not insert 'vboxsf': Exec format error
Oct 31 14:22:55 localhost kernel: vboxguest: disagrees about version of symbol module_layout
Oct 31 14:22:55 localhost VBoxService[276]: VBoxService: error: VbglR3Init failed with rc=VERR_FILE_NOT_FOUND
Oct 31 14:22:55 localhost systemd[1]: vboxservice.service: Main process exited, code=exited, status=1/FAILURE
Oct 31 14:22:55 localhost systemd[1]: vboxservice.service: Unit entered failed state.
Oct 31 14:22:55 localhost systemd[1]: vboxservice.service: Failed with result 'exit-code'.
Oct 31 14:27:46 localhost login[449]: FAILED LOGIN 1 FROM tty1 FOR modprobe vboxsf, Authentication failure
Oct 31 14:27:56 localhost kernel: vboxguest: disagrees about version of symbol module_layout
Oct 31 14:28:03 localhost kernel: vboxguest: disagrees about version of symbol module_layout
Oct 31 14:29:01 localhost kernel: vboxguest: disagrees about version of symbol module_layout
Oct 31 14:42:02 localhost kernel: vboxvideo: disagrees about version of symbol module_layout
Oct 31 14:42:28 localhost kernel: vboxguest: disagrees about version of symbol module_layout
Oct 31 14:42:39 localhost kernel: vboxguest: disagrees about version of symbol module_layout
Oct 31 14:43:39 localhost kernel: vboxguest: disagrees about version of symbol module_layout
Oct 31 14:45:14 localhost kernel: vboxvideo: disagrees about version of symbol module_layout
Oct 31 14:45:44 localhost kernel: vboxguest: disagrees about version of symbol module_layout

It seems that modules versions are incompatible. But how that could happened?

Offline

#4 2015-10-31 11:59:26

WorMzy
Forum Moderator
From: Scotland
Registered: 2010-06-16
Posts: 11,896
Website

Re: [SOLVED] Virtualbox service doesn't start

Can you post the output of

$ modinfo vboxsf
$ uname -a

Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD

Making lemonade from lemons since 2015.

Offline

#5 2015-10-31 12:09:19

olive
Member
From: Belgium
Registered: 2008-06-22
Posts: 1,490

Re: [SOLVED] Virtualbox service doesn't start

I have tried myself (Virtualbox as guest under Windows 10) and it works for me. Linux is at version 4.2.5-1 and virtualbox-guest-modules at 5.0.8-2. Try to reinstall the last one (better, remove it, possibly with -dd; make sure there are no leftover modules in your system and reinstall it). Also check you have not leftover modules. (sudo find / -mount -name 'vboxguest.ko*' or proceed more intelligently if you have a slower or very big disk).

Last edited by olive (2015-10-31 12:10:42)

Offline

#6 2015-10-31 12:58:39

Suncatcher
Banned
Registered: 2015-03-30
Posts: 36

Re: [SOLVED] Virtualbox service doesn't start

$ modinfo vboxsf

filename:       /lib/modules/4.2.2-1-ARCH/extramodules/vboxsf.ko.gz
version:        5.0.8_OSE (interface 0x00010004)
license:        GPL
author:         Oracle Corporation
description:    Oracle VM VirtualBox VFS Module for Host File System Access
srcversion:     B239D6E7BAC40A3B658E4EC
depends:        vboxguest
vermagic:       4.2.4-1-ARCH SMP preempt mod_unload modversions
parm:           follow_symlinks:Let host resolve symlinks rather than showing them (int)

$ uname -a

Linux localhost 4.2.2-1-ARCH #1 SMP PREEMPT Tue Sep 29 22:21:33 CEST 2015 x86_64 GNU/Linux

Offline

#7 2015-10-31 14:22:12

WorMzy
Forum Moderator
From: Scotland
Registered: 2010-06-16
Posts: 11,896
Website

Re: [SOLVED] Virtualbox service doesn't start

The problem is that your modules have 4.2.4 vermagic, but your kernel is 4.2.2. I'm not sure how you managed that, but I suspect you may have been running partial upgrades.

Do a full system update and reboot afterwards, then try again.

Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD

Making lemonade from lemons since 2015.

Offline

#8 2015-10-31 14:25:38

Suncatcher
Banned
Registered: 2015-03-30
Posts: 36

Re: [SOLVED] Virtualbox service doesn't start

WorMzy wrote:

Do a full system update and reboot afterwards, then try again.

Yes, I 've already done that and the issue has gone. Thanks.

Offline

Pages: 1

Board footer

Powered by FluxBB