Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#74919 - [virtualbox] VMs don't start with 6.1.34-4 on linux-lts

Attached to Project: Community Packages
Opened by Olivier Bilodeau (plaxx) - Tuesday, 31 May 2022, 12:54 GMT
Last edited by Christian Hesse (eworm) - Wednesday, 01 June 2022, 21:03 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Christian Hesse (eworm)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

When trying to launch any VM, you get a VirtualBox Error:

> Failed to open a session for the virtual machine Windows10.
>
> Failed to load R0 module /usr/lib/virtualbox/VMMR0.r0: Unable to locate imported symbol 'SUPR0FpuBegin' for module 'VMMR0.r0' (VERR_SYMBOL_NOT_FOUND).
>
> Failed to load VMMR0.r0 (VERR_SYMBOL_NOT_FOUND).
>
> Result Code: NS_ERROR_FAILURE (0x80004005)
> Component: ConsoleWrap
> Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}


Important to note that I'm on the linux-lts kernel 5.15.43-1-lts. Latest patch notes for virtualbox seem to indicate kernel 5.18 specific changes that might have been compiled in my kernel module. Not sure. See https://github.com/archlinux/svntogit-community/commit/b103146beee8b7c70d04685033a8536aed2e5aea


Steps to reproduce:

Try to launch a VM with latest VirtualBox
   2022-05-31_09-53.png (47.4 KiB)
This task depends upon

Closed by  Christian Hesse (eworm)
Wednesday, 01 June 2022, 21:03 GMT
Reason for closing:  Works for me
Additional comments about closing:  Works with linux-lts 5.15.44-1
Comment by Olivier Bilodeau (plaxx) - Tuesday, 31 May 2022, 13:06 GMT
I rebooted to linux (at 5.18.1-arch1-1) (instead of linux-lts; at 5.15.43-1-lts) and it works now!

Patches added in 6.1.34-3 or 6.1.34-4 might introduce a regression for non-5.18 kernel or maybe the dkms built module is building with the ifdef like its 5.18 although you are building for an older version?
Comment by Christian Hesse (eworm) - Tuesday, 31 May 2022, 13:16 GMT
Wondering if this is a temporary issue with old modules still being loaded? Are you still suffering this if you boot linux-lts again?
Comment by Olivier Bilodeau (plaxx) - Tuesday, 31 May 2022, 16:25 GMT
Yes, I rebooted after the initial problem and it still happened.
Comment by Christian Hesse (eworm) - Tuesday, 31 May 2022, 20:00 GMT
I can not reproduce... Works for me without issues (with linux-lts 5.15.44-1).
Comment by Ledun Julien (dun32) - Wednesday, 01 June 2022, 09:12 GMT
Got an issue too with the latest update. My Windows 10 guests boot correctly but are freezing after a few minutes of use with linux-lts 5.15.44-1.
Currently trying with linux 5.18.1, it looks ok, the guests are faster than with lts kernel.
Comment by Olivier Bilodeau (plaxx) - Wednesday, 01 June 2022, 11:33 GMT
Retried LTS this morning. Clean boot with the same issue. Unfortunately was at 5.15.43-1, not .44. I just upgraded to 5.15.44, I'll test it later.

I'm using dkms, virtualbox-host-dkms to be exact, in case it matters:

```
==> dkms install --no-depmod vboxhost/6.1.34_OSE -k 5.15.44-1-lts
```
   2022-06-01_08-22.png (106.2 KiB)
Comment by Olivier Bilodeau (plaxx) - Wednesday, 01 June 2022, 19:34 GMT
Ok, when back in 5.15.44-1 VirtualBox worked. I'm not 100% sure to what I can attribute the problem given that I use the `kernel-modules-hook` thing, switch between lts and non-lts and I was not running latest when it was failing.

I think this can be closed.
   2022-06-01_16-23.png (27 KiB)

Loading...