Bug 30688 - Update request: kernel-linus-5.15.58-1.mga8
Summary: Update request: kernel-linus-5.15.58-1.mga8
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: Security (show other bugs)
Version: 8
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: QA Team
QA Contact: Sec team
URL:
Whiteboard: MGA8-64-OK
Keywords: advisory, validated_update
Depends on:
Blocks:
 
Reported: 2022-07-30 10:39 CEST by Thomas Backlund
Modified: 2022-08-06 17:44 CEST (History)
4 users (show)

See Also:
Source RPM: kernel-linus
CVE:
Status comment:


Attachments

Description Thomas Backlund 2022-07-30 10:39:17 CEST
Retbleed and other security and bugfixes, advisory will follow...

SRPMS:
kernel-linus-5.15.58-1.mga8.src.rpm


i586:
kernel-linus-5.15.58-1.mga8-1-1.mga8.i586.rpm
kernel-linus-devel-5.15.58-1.mga8-1-1.mga8.i586.rpm
kernel-linus-devel-latest-5.15.58-1.mga8.i586.rpm
kernel-linus-doc-5.15.58-1.mga8.noarch.rpm
kernel-linus-latest-5.15.58-1.mga8.i586.rpm
kernel-linus-source-5.15.58-1.mga8-1-1.mga8.noarch.rpm
kernel-linus-source-latest-5.15.58-1.mga8.noarch.rpm


x86_64:
kernel-linus-5.15.58-1.mga8-1-1.mga8.x86_64.rpm
kernel-linus-devel-5.15.58-1.mga8-1-1.mga8.x86_64.rpm
kernel-linus-devel-latest-5.15.58-1.mga8.x86_64.rpm
kernel-linus-doc-5.15.58-1.mga8.noarch.rpm
kernel-linus-latest-5.15.58-1.mga8.x86_64.rpm
kernel-linus-source-5.15.58-1.mga8-1-1.mga8.noarch.rpm
kernel-linus-source-latest-5.15.58-1.mga8.noarch.rpm
Comment 1 Len Lawrence 2022-07-31 01:36:05 CEST
Kernel: 5.15.58-1.mga8 x86_64
10-Core Intel Core i9-7900X
NVIDIA GeForce GTX 1080 Ti

All three flavours of the  the new kernel installed without incident.

After reboot most things seemed to be working including bluetooth audio but virtualbox would not run.  Crashed immediately.  NS_ERROR_FAILURE
virtualbox-6.1.36-1.mga8

Tried:
$ sudo urpme dkms-virtualbox
That took a very long time.
# urpmi dkms-virtualbox
Package dkms-virtualbox-6.1.36-1.mga8.x86_64 is already installed

$ ls -l 'VirtualBox VMs'/rastaban/Logs
total 424
-rw------- 1 lcl lcl  39975 Jul 31 00:14 VBox.log
-rw------- 1 lcl lcl  39975 Jul 30 23:54 VBox.log.1
-rw------- 1 lcl lcl 168338 Jun 26 17:23 VBox.log.2
-rw------- 1 lcl lcl 176697 Jun 21 18:58 VBox.log.3

Last few lines of VBox.log:
00:00:01.112918 SUP: Loaded VBoxEhciR0.r0 (/usr/lib64/virtualbox/ExtensionPacks/Oracle_VM_VirtualBox_Extension_Pack/linux.amd64/VBoxEhciR0.r0) at 0xXXXXXXXXXXXXXXXX - ModuleInit at XXXXXXXXXXXXXXXX and ModuleTerm at XXXXXXXXXXXXXXXX

It was working a month ago.

CC: (none) => tarazed25

Comment 2 Morgan Leijström 2022-07-31 02:00:54 CEST
@Len: Do VB launch for you on our 5.15.55 kernel?

VirtualBox works OK for me on the new backport kernel Bug 30689.

CC: (none) => fri

Comment 3 Dave Hodgins 2022-07-31 02:05:10 CEST
Len, did you remember to update the extension pack?
https://www.virtualbox.org/wiki/Downloads

CC: (none) => davidwhodgins

Comment 4 Len Lawrence 2022-07-31 02:06:52 CEST
@Morgan: shall check that after some sleep.  Thanks.
Comment 5 Len Lawrence 2022-07-31 02:10:02 CEST
@Dave: No.  Did not even realise that it was necessary.  Still an absolute beginner with virtualbox.  Don't actually use it for anything except testing kernels.  Thanks.
Comment 6 Morgan Leijström 2022-07-31 11:01:03 CEST
You need the new extension pack :)
Comment 7 Len Lawrence 2022-07-31 11:24:05 CEST
It looks like the latest extension pack was already in place.  And, as said, it was working a month ago with an earlier kernel.
Comment 8 Dave Hodgins 2022-07-31 22:09:21 CEST
Looks like data center problems are fixed

Having ruled out in private messages a version problem for the extension packs,
etc., I checked the VBox.log from my working VirtualBox install.
00:00:01.908953 SUP: Loaded VBoxEhciR0.r0 (/usr/lib64/virtualbox/ExtensionPacks/Oracle_VM_VirtualBox_Extension_Pack/linux.amd64/VBoxEhciR0.r0) at 0xXXXXXXXXXXXXXXXX - ModuleInit at XXXXXXXXXXXXXXXX and ModuleTerm at XXXXXXXXXXXXXXXX
00:00:01.910419 PGM: The CPU physical address width is 48 bits
00:00:01.910441 PGM: PGMR3InitFinalize: 4 MB PSE mask 0000ffffffffffff -> VINF_SUCCESS

And lots more messages as I ran/then stopped the guest.

Two more things to check. Is the file system full (df -h)? Any chance the
cmos settings were lost and it reverted to having virtualization disabled?
https://www.vminstall.com/how-to-enable-virtualization-in-the-bios/
Comment 9 Thomas Backlund 2022-07-31 22:26:28 CEST
(In reply to Len Lawrence from comment #5)
> @Dave: No.  Did not even realise that it was necessary.  Still an absolute
> beginner with virtualbox.  Don't actually use it for anything except testing
> kernels.  Thanks.

Well, technically you dont need the extension pack unless you want to use theese features for the client vms:

Oracle Cloud Infrastructure integration, USB 2.0 and USB 3.0 Host Controller, Host Webcam, VirtualBox RDP, PXE ROM, Disk Encryption, NVMe.


but _if_ it's installed, it must match the version on the host, so currently it must show version 6.1.36r152435 in VritualBox Preferences.


(In reply to Len Lawrence from comment #7)
> It looks like the latest extension pack was already in place.  And, as said,
> it was working a month ago with an earlier kernel.

A month ago we didn't have 6.1.36, as I built that one on 2022-07-21, and released it as an update on 2022-07-25



one thing to test is to remove the extension pack, check that the client vm works without it, then try to re-install the extension pack and see if it breaks down again...
Comment 10 Len Lawrence 2022-08-01 00:10:04 CEST
@tmb in reply to comment 9:
No, virtualbox guests now launch OK - managed to sort out the numbers.  I also ran vbox with the desktop kernel and that also worked.  Had not been able to post a report.  The main trouble now is that vbox with either kernel fails to connect to external USB devices even though they are registered in settings.  USB has worked on past systems so there must be something I have missed.
Thomas Backlund 2022-08-06 16:50:01 CEST

Keywords: (none) => advisory, validated_update
CC: (none) => sysadmin-bugs
Whiteboard: (none) => MGA8-64-OK

Comment 11 Mageia Robot 2022-08-06 17:44:46 CEST
An update for this issue has been pushed to the Mageia Updates repository.

https://advisories.mageia.org/MGASA-2022-0279.html

Status: NEW => RESOLVED
Resolution: (none) => FIXED


Note You need to log in before you can comment on or make changes to this bug.