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
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
@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
Len, did you remember to update the extension pack? https://www.virtualbox.org/wiki/Downloads
CC: (none) => davidwhodgins
@Morgan: shall check that after some sleep. Thanks.
@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.
You need the new extension pack :)
It looks like the latest extension pack was already in place. And, as said, it was working a month ago with an earlier kernel.
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/
(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...
@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.
Keywords: (none) => advisory, validated_updateCC: (none) => sysadmin-bugsWhiteboard: (none) => MGA8-64-OK
An update for this issue has been pushed to the Mageia Updates repository. https://advisories.mageia.org/MGASA-2022-0279.html
Status: NEW => RESOLVEDResolution: (none) => FIXED