Kernel Update breaks VirtualBox Plugin

Mr Smile · 17. Juni 2018

Hello,

after installing some (all pending) updates and rebooting, Virtual Box Plugin is broken. I get this error message when logging into omv gui.

Could not connect to host ([url]http://127.0.0.1:18083/[/url])

Code: Could not connect to host (http://127.0.0.1:18083/)

Fehler #0:
Exception: Could not connect to host (http://127.0.0.1:18083/) in /usr/share/phpvirtualbox/endpoints/lib/vboxconnector.php:220
Stack trace:
#0 /usr/share/openmediavault/engined/rpc/virtualbox.inc(136): vboxconnector->connect()
#1 [internal function]: OMV\Engined\Rpc\VirtualBox->getMachines(Array, Array)
#2 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
#3 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('getMachines', Array, Array)
#4 /usr/sbin/omv-engined(536): OMV\Rpc\Rpc::call('VirtualBox', 'getMachines', Array, Array, 1)
#5 {main}

Starting PHPVirtualBox gives me:

An error occurred communicating with your vboxwebsrv. No more requests will be sent by phpVirtualBox until the error is corrected and this page is refreshed. The details of this connection error should be displayed in a subsequent dialog box.

followed by:

Code: Could not connect to host (http://127.0.0.1:18083/)

Alles anzeigen

A new kernel has been installed recently: Debian GNU/Linux, with Linux 4.16.0-0.bpo.2-amd64.

Switching back to Debian GNU/Linux, with Linux 4.16.0-0.bpo.1-amd64 in OMV-Extras fixes the problem for now.

Would you please tell me what to do to fix that (now and in future)? And is there a way to automate this fixing for future kernel updates? (at least for minor updates like this one)

Thanks in advance.

ryecoaaron · 18. Juni 2018

Zitat von Mr Smile

Would you please tell me what to do to fix that (now and in future)? And is there a way to automate this fixing for future kernel updates? (at least for minor updates like this one)

You probably don't have the kernel headers installed for the new kernel. Not sure why. The plugin depends on linux-image-amd64 which should automatically update when you update the kernel. My systems did.

Zitat von Mr Smile

Would you please tell me what to do to fix that (now and in future)?

I think this has been discussed many, many times. I have tried to make the plugins do the right thing by depending on the meta package for the kernel and headers. The virtualbox-dkms package is supposed to be triggered on kernel upgrades to compile a new module. We didn't create these packages . If they aren't working, I really don't know what to tell you. There is *very* little the plugin can do about it. All I can suggest is test on a different system before upgrading on your main system.

Zitat von Mr Smile

(at least for minor updates like this one)

When Debian creates a different package for a kernel (even though they are both 4.16), it isn't really a minor update. Minor updates will be the same package name.

Mr Smile · 20. Juni 2018

Hmm. Didn't touch anything kernel related since installation of omv. I uninstalled VirtualBox Plugin, switched to Debian GNU/Linux, with Linux 4.16.0-0.bpo.2-amd64 again and after a reboot I reinstalled VirtualBox. And now the error is gone. Any idea why virtualbox-dkms was not triggered during kernel upgrade? This is really a very standard omv installation.

ryecoaaron · 20. Juni 2018

Zitat von Mr Smile

And now the error is gone. Any idea why virtualbox-dkms was not triggered during kernel upgrade? This is really a very standard omv installation

Unfortunately, I have no idea.

Mr Smile · 13. Juli 2018

Unfortunately this happened again. I don't know what (days before installed) update broke it this time but after a restart I had the same problem. I had no ssh access when it happened. So I decided to uninstall and install Virtualbox-Plugin again and this solved the issue. So it seems that virtualbox-dkms was not triggered again after kernel update.

Could you please help me to identify and fix the reason for that? This problem is very annoying. Thanks.

ryecoaaron · 15. Juli 2018

What kernel update did you install? Unfortunately, this is not a package we maintain. Uninstalling the plugin only worked because it uninstalled virtualbox and re-installed. dpkg-reconfigure virtualbox-dkms should work. I had added a button to the plugin to do this step but it didn't seem necessary in OMV 4.x. Maybe it needs to come back. Otherwise, I don't have a solution if dkms isn't doing its job.

Mr Smile · 28. Juli 2018

Hmmm. I actually don't know. I'm not even sure anymore that it was a kernel update that broke vbox. The installed Kernel was and is 4.16.0-0.bpo.2-amd64.

So it seems that some other past update has been responsible for this failure that became apparent after rebooting omv. I'll keep an eye on it and report back if/when it happens again.

ryecoaaron · 3. August 2018

The 4.17 kernel has been released. Please don't install it or new linux-header packages because virtualbox 4.2.10 will not compile its module on the 4.17 kernel.

odinb · 4. August 2018

Yep, discovered that AFTER upgrading!

I have this installed:

Code

root@openmediavault:/# sudo ls /boot | grep vmlinuz | cut -d'-' -f2,3
4.16.0-0.bpo.2
4.17.0-0.bpo.1
root@openmediavault:/#

Specifically these:

Code

root@openmediavault:/# dpkg -l | grep linux | awk '{print$2}'
console-setup-linux
firmware-linux
firmware-linux-free
firmware-linux-nonfree
libselinux1:amd64
linux-base
linux-compiler-gcc-6-x86
linux-headers-4.16.0-0.bpo.2-amd64
linux-headers-4.16.0-0.bpo.2-common
linux-headers-4.17.0-0.bpo.1-amd64
linux-headers-4.17.0-0.bpo.1-common
linux-headers-amd64
linux-image-4.16.0-0.bpo.2-amd64
linux-image-4.17.0-0.bpo.1-amd64
linux-image-amd64
linux-kbuild-4.16
linux-kbuild-4.17
linux-libc-dev:amd64
util-linux
root@openmediavault:/#

Alles anzeigen

odinb · 4. August 2018

From the error log (only interesting parts):

Code

DKMS make.log for virtualbox-5.2.10 for kernel 4.17.0-0.bpo.1-amd64 (x86_64)
Fri Aug  3 18:06:51 CDT 2018
make: Entering directory '/usr/src/linux-headers-4.17.0-0.bpo.1-amd64'
  CC [M]  /var/lib/dkms/virtualbox/5.2.10/build/vboxdrv/SUPDrvTracer.o
/var/lib/dkms/virtualbox/5.2.10/build/vboxdrv/.tmp_SUPDrvTracer.o: warning: objtool: .text+0x7: indirect jump found in RETPOLINE build
  CC [M]  /var/lib/dkms/virtualbox/5.2.10/build/vboxdrv/SUPLibAll.o
  CC [M]  /var/lib/dkms/virtualbox/5.2.10/build/vboxdrv/r0drv/linux/process-r0drv-linux.o
/var/lib/dkms/virtualbox/5.2.10/build/vboxdrv/r0drv/linux/.tmp_memuserkernel-r0drv-linux.o: warning: objtool: .fixup: unexpected end of section
  CC [M]  /var/lib/dkms/virtualbox/5.2.10/build/vboxdrv/r0drv/linux/rtStrFormatKernelAddress-r0drv-linux.o
  CC [M]  /var/lib/dkms/virtualbox/5.2.10/build/vboxpci/linux/SUPR0IdcClient-linux.o
/var/lib/dkms/virtualbox/5.2.10/build/vboxpci/linux/VBoxPci-linux.c: In function ‘vboxPciLinuxDevDetachHostDriver’:
/var/lib/dkms/virtualbox/5.2.10/build/vboxpci/linux/VBoxPci-linux.c:92:40: error: implicit declaration of function ‘pci_get_bus_and_slot’ [-Werror=implicit-function-declaration]
 # define PCI_DEV_GET_SLOT(bus, devfn)  pci_get_bus_and_slot(bus, devfn)
                                        ^
/var/lib/dkms/virtualbox/5.2.10/build/vboxpci/linux/VBoxPci-linux.c:397:15: note: in expansion of macro ‘PCI_DEV_GET_SLOT’
     pPciDev = PCI_DEV_GET_SLOT(uBus, uDevFn);
               ^~~~~~~~~~~~~~~~
/var/lib/dkms/virtualbox/5.2.10/build/vboxpci/linux/VBoxPci-linux.c:397:13: warning: assignment makes pointer from integer without a cast [-Wint-conversion]
     pPciDev = PCI_DEV_GET_SLOT(uBus, uDevFn);
             ^
/var/lib/dkms/virtualbox/5.2.10/build/vboxpci/linux/VBoxPci-linux.c: In function ‘vboxPciOsDevInit’:
/var/lib/dkms/virtualbox/5.2.10/build/vboxpci/linux/VBoxPci-linux.c:648:17: warning: assignment makes pointer from integer without a cast [-Wint-conversion]
         pPciDev = PCI_DEV_GET_SLOT((pIns->HostPciAddress) >> 8,
                 ^
cc1: some warnings being treated as errors
/usr/src/linux-headers-4.17.0-0.bpo.1-common/scripts/Makefile.build:317: recipe for target '/var/lib/dkms/virtualbox/5.2.10/build/vboxpci/linux/VBoxPci-linux.o' failed
make[4]: *** [/var/lib/dkms/virtualbox/5.2.10/build/vboxpci/linux/VBoxPci-linux.o] Error 1
/usr/src/linux-headers-4.17.0-0.bpo.1-common/scripts/Makefile.build:564: recipe for target '/var/lib/dkms/virtualbox/5.2.10/build/vboxpci' failed
make[3]: *** [/var/lib/dkms/virtualbox/5.2.10/build/vboxpci] Error 2
/usr/src/linux-headers-4.17.0-0.bpo.1-common/Makefile:1585: recipe for target '_module_/var/lib/dkms/virtualbox/5.2.10/build' failed
make[2]: *** [_module_/var/lib/dkms/virtualbox/5.2.10/build] Error 2
Makefile:146: recipe for target 'sub-make' failed
make[1]: *** [sub-make] Error 2
Makefile:8: recipe for target 'all' failed
make: *** [all] Error 2
make: Leaving directory '/usr/src/linux-headers-4.17.0-0.bpo.1-amd64'

Alles anzeigen

odinb · 4. August 2018

Any idea on whats causing this, and when it will be fixed?

Only checked here after I had already upgraded.

Running on the old kernel (4.16.0-0.bpo.2) for now....

ryecoaaron · 4. August 2018

Zitat von odinb

Any idea on whats causing this, and when it will be fixed?

The virtualbox kernel driver needs to be updated to support the newer kernel. It can be fixed by using the proxmox kernel or waiting for virtualbox 5.2.12+ to be in the debian repos or not upgrading or just keep using the 4.16 kernel for now. I will see if the 5.2.16 package from Buster builds on Stretch.

The virtualbox 5.2.16 package is in the stretch-backports repo now. You just need to update your system.

odinb · 5. August 2018

Thanks a bunch! Works now!

kekec888 · 7. August 2018

Zitat von ryecoaaron

The virtualbox kernel driver needs to be updated to support the newer kernel. It can be fixed by using the proxmox kernel or waiting for virtualbox 5.2.12+ to be in the debian repos or not upgrading or just keep using the 4.16 kernel for now. I will see if the 5.2.16 package from Buster builds on Stretch.
The virtualbox 5.2.16 package is in the stretch-backports repo now. You just need to update your system.

Hallo sir

My vm is running very bad (Windows10 keeps locking and frezzing // In rdp VNC is running fine)
I have installed the new kernel 4.17 and updated virtualbox to 5.2.16 BUT still having issues..

I also keep getting this: See attachments

And the log: See attachments

ryecoaaron · 7. August 2018

Zitat von kekec888

My vm is running very bad (Windows10 keeps locking and frezzing // In rdp VNC is running fine)
I have installed the new kernel 4.17 and updated virtualbox to 5.2.16 BUT still having issues..

I don't use virtualbox and even when I did, I didn't run Windows VMs. Did you install the latest guest tools/drivers? This is one reason to not always run the latest version of virtualbox I guess.

kekec888 · 7. August 2018

Zitat von ryecoaaron

I don't use virtualbox and even when I did, I didn't run Windows VMs. Did you install the latest guest tools/drivers? This is one reason to not always run the latest version of virtualbox I guess.

Hmm yeah i have updated the guest additions also...

Is there anyway to roll back ?
I can uninstall virtualbox but when i install it from plugins its still the new version...

ryecoaaron · 7. August 2018

Zitat von kekec888

Is there anyway to roll back ?

Sure. The other kernel is probably still installed (select it from the kernel tab in omv-extras). I would try the older kernel before changing virtualbox.

Mr Smile · 7. August 2018

Zitat von ryecoaaron

The virtualbox kernel driver needs to be updated to support the newer kernel. It can be fixed by using the proxmox kernel or waiting for virtualbox 5.2.12+ to be in the debian repos or not upgrading or just keep using the 4.16 kernel for now. I will see if the 5.2.16 package from Buster builds on Stretch.
The virtualbox 5.2.16 package is in the stretch-backports repo now. You just need to update your system.

Thanks a lot for this advice. I waited patiently and today 4.17.0-0.bpo.1-amd64 update went through without problems.

Don't have any Windows VMs. The Linux ones run as fast a expected.

Mr Smile · 7. August 2018

ryecoaaron:

Just an idea. (Kernel-)Updates seem to be "problematic" to users of vbox-plugin in general. Should we have a pinned status thread for vbox related stuff? ... any fixed place you can put such infos to.

ryecoaaron · 8. August 2018

Zitat von Mr Smile

(Kernel-)Updates seem to be "problematic" to users of vbox-plugin in general. Should we have a pinned status thread for vbox related stuff?

Kernel updates can be problematic for virtualbox, zfs, and other compiled kernel modules. I guess I could pin a thread for it if someone else maintains it. But, most people don't look at them.

Jetzt mitmachen!