kmods will be built after kernel-5.15.74-1.mga8 update is tested and validated...

Depends on: (none) => 30969

Note the extension pack is available from
https://www.virtualbox.org/wiki/Download_Old_Builds_6_1
which links to
https://download.virtualbox.org/virtualbox/6.1.40/Oracle_VM_VirtualBox_Extension_Pack-6.1.40.vbox-extpack

CC: (none) => davidwhodgins

MGA8 64 XFCE Core I3 6Go RAM 

uname -a 
Linux localhost 5.15.65-desktop-1.mga8

Updated with QA repo and RPM:

dkms-virtualbox                6.1.40       1.mga8        x86_64  
virtualbox                     6.1.40       1.mga8        x86_64  

No issues at installation.

VM tested MGA8 XFCE OK, MGA Cauldron OK, Primtux based on lubuntu distro OK.
Creation new VM OK

CC: (none) => guillaume.royer

This update fixes CVE-2022-2162[017] and CVE-2022-3942[4-6]:
https://www.oracle.com/security-alerts/cpuoct2022.html#AppendixOVIR

On real hardware, M8, Plasma, 64-bit

Package(s) under test:
virtualbox

M8 i586   Xfce   upating works just fine as a Vbox client
  Package virtualbox-guest-additions-6.1.38-1.2.mga8.i586 is already installed

M8 x86_64 Plasma upating works just fine as a Vbox client
  Package virtualbox-guest-additions-6.1.38-1.2.mga8.x86_64 is already installed


clear
uname -a
urpmi --test virtualbox
urpmi dkms-virtualbox
urpmi virtualbox-guest-additions
urpmi x11-driver-video-vboxvideo
urpmi kernel-desktop-devel-latest
urpmi virtualbox-kernel-desktop-latest

Linux localhost 5.15.65-desktop-1.mga8 #1 SMP Mon Sep 5 14:05:33 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
Package virtualbox-6.1.38-1.2.mga8.x86_64 is already installed
Package dkms-virtualbox-6.1.38-1.2.mga8.x86_64 is already installed
Package virtualbox-guest-additions-6.1.38-1.2.mga8.x86_64 is already installed
Package x11-driver-video-vboxvideo-1.0.0-6.mga8.x86_64 is already installed
Package kernel-desktop-devel-latest-5.15.65-1.mga8.x86_64 is already installed
Package virtualbox-kernel-desktop-latest-6.1.38-1.5.mga8.x86_64 is already installed

install from updates testing:

clear
urpmi --auto virtualbox
urpmi --auto dkms-virtualbox
urpmi --auto virtualbox-guest-additions
urpmi --auto x11-driver-video-vboxvideo
urpmi --auto kernel-desktop-devel-latest
urpmi --auto virtualbox-kernel-desktop-latest

reboot

clear
uname -a
urpmi --test virtualbox
urpmi --test dkms-virtualbox
urpmi --test virtualbox-guest-additions
urpmi --test x11-driver-video-vboxvideo
urpmi --test kernel-desktop-devel-latest
urpmi --test virtualbox-kernel-desktop-latest

Linux localhost 5.15.74-desktop-1.mga8 #1 SMP Sat Oct 15 19:19:46 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
Package virtualbox-6.1.40-1.mga8.x86_64 is already installed
Package dkms-virtualbox-6.1.40-1.mga8.x86_64 is already installed
Package virtualbox-guest-additions-6.1.40-1.mga8.x86_64 is already installed
Package x11-driver-video-vboxvideo-1.0.0-6.mga8.x86_64 is already installed
Package kernel-desktop-devel-latest-5.15.74-1.mga8.x86_64 is already installed
Package virtualbox-kernel-desktop-latest-6.1.38-1.6.mga8.x86_64 is already installed

checking update:

M8 i586   Xfce   upating works just fine as a Vbox client ( glibc updated )
  Package virtualbox-guest-additions-6.1.38-1.2.mga8.i586 is already installed

M8 x86_64 Plasma upating works just fine as a Vbox client ( glibc updated )
  Package virtualbox-guest-additions-6.1.40-1.mga8.x86_64 is already installed

CC: (none) => wilcal.int

Hi. Using QArepo and urpmi --auto-update, I get the request to install kernel-devel as a dependency.

Do you have that as well?

CC: (none) => chb0

Installing any dkms related package will pull in the kernel-devel package.

(In reply to Dave Hodgins from comment #7)
> Installing any dkms related package will pull in the kernel-devel package.

Is it new with this update then? Because I have virtualbox installed already without kernel-devel. Thanks.

Does rpm -qa 'dkms*' show anything?

(In reply to Dave Hodgins from comment #9)
> Does rpm -qa 'dkms*' show anything?

Yes: dkms-minimal-2.0.19-41.mga8

Did you include dkms-virtualbox in the list for qarepo? If so, that package
provides the source used to compile the virtualbox kernel module. It requires
the kernel-devel package fro the compile to work.

(In reply to Dave Hodgins from comment #11)
> Did you include dkms-virtualbox in the list for qarepo? If so, that package
> provides the source used to compile the virtualbox kernel module. It requires
> the kernel-devel package fro the compile to work.

Yes, I did. I always add all the listed packages. I don't remember I had this issue with the previous testing.
Should I remove it? Does it mean it is not required to install this update of virtualbox?

The virtualbox-kernel packages are pre-compiled virtualbox kernel modules for
the desktop and server kernels.

When (as is the case here) the pre-compiled kernel modules (kmod packages) are
not yet available, or if using a kernel flavor that does not have them, such
as kernel-linus, then the dkms-virtualbox is needed, which requires the
corresponding kernel devel package in order to compile the kernel module on
that system. This is expected behaviour. Most of the time the pre-compiled
modules are available, but not always.

x86_64 OK here

Hardware:  My venerable workstation "svarten": Mainboard: Sabertooth P67, CPU: i7-3770, RAM 16G, GM107 [GeForce GTX 750] using nvidia-current; GeForce 635 series and later, 4k display.

Updated to
- dkms-virtualbox-6.1.40-1.mga8.x86_64
- virtualbox-6.1.40-1.mga8.x86_64

rebooted

$ uname -a
Linux svarten.tribun 5.19.16-desktop-1.mga8 #1 SMP PREEMPT_DYNAMIC Sat Oct 15 18:19:46 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

$ dkms status
virtualbox, 6.1.40-1.mga8, 5.19.16-desktop-1.mga8, x86_64: installed 
nvidia-current, 515.65.01-1.mga8.nonfree, 5.19.16-desktop-1.mga8, x86_64: installed 
nvidia-current, 515.65.01-1.mga8.nonfree, 5.15.74-desktop-1.mga8, x86_64: installed 
virtualbox, 6.1.38-1.2.mga8, 5.19.16-desktop-1.mga8, x86_64: installed-binary from 5.19.16-desktop-1.mga8
virtualbox, 6.1.38-1.2.mga8, 5.15.74-desktop-1.mga8, x86_64: installed-binary from 5.15.74-desktop-1.mga8


Hmmm... this system per above now have both
virtualbox, 6.1.40-1.mga8, 5.19.16-desktop-1.mga8, x86_64: installed 
virtualbox, 6.1.38-1.2.mga8, 5.19.16-desktop-1.mga8, x86_64: installed-binary from 5.19.16-desktop-1.mga8


§ wget https://download.virtualbox.org/virtualbox/6.1.40/Oracle_VM_VirtualBox_Extension_Pack-6.1.40.vbox-extpack

$ sudo VBoxManage extpack install --replace Oracle_VM_VirtualBox_Extension_Pack-6.1.40.vbox-extpack

Starting VirtualBox GUI, and guests:

___Guests are OK: running concurrently

Guest 1: my usual MSW7pro-64. It found it needed to update guest additions, i let it download OK, and let it run and reboot.
Tests OK: dynamic guest window resizing, bidirectional clipboard, host shared folders both bidirectional and write protection checked, USB2 memory stick read&write (using upstream extension pack) USB2 chip programmer Conitec Galep-5, video playing OK in Firefox, drag file from host Dolphin to guest Explorer. Windows update (virus def).

Guest 2: BOINC LHC@home ATLAS simulation virtual machine 3CPU.

Guest 3: Mageia 8 -64, Xfce, kernel 5.19.16-desktop-1.mga8
Tests OK: update applet, Firefox surfing and plays video. Plugged in USB flash stick in host, checked it in VritualBox guest window frame menu to share, the partitions icons popped up on xfce desktop, and I could read and put new files. Bidirectional shared clipboard. Dynamic desktop resizing.

CC: (none) => fri

kmods for updates:

SRPM:
kmod-virtualbox-6.1.40-1.mga8.src.rpm

x86_64:
virtualbox-kernel-5.15.74-desktop-1.mga8-6.1.40-1.mga8.x86_64.rpm
virtualbox-kernel-5.15.74-server-1.mga8-6.1.40-1.mga8.x86_64.rpm
virtualbox-kernel-desktop-latest-6.1.40-1.mga8.x86_64.rpm
virtualbox-kernel-server-latest-6.1.40-1.mga8.x86_64.rpm



kmods for backports:

SRPM:
kmod-virtualbox-6.1.40-2.mga8.src.rpm

x86_64:
virtualbox-kernel-5.19.16-desktop-1.mga8-6.1.40-2.mga8.x86_64.rpm
virtualbox-kernel-5.19.16-server-1.mga8-6.1.40-2.mga8.x86_64.rpm
virtualbox-kernel-desktop-latest-6.1.40-2.mga8.x86_64.rpm
virtualbox-kernel-server-latest-6.1.40-2.mga8.x86_64.rpm

(In reply to Thomas Backlund from comment #15)
> kmods for backports:
> 
> SRPM:
> kmod-virtualbox-6.1.40-2.mga8.src.rpm
> 
> x86_64:
> virtualbox-kernel-5.19.16-desktop-1.mga8-6.1.40-2.mga8.x86_64.rpm
> virtualbox-kernel-5.19.16-server-1.mga8-6.1.40-2.mga8.x86_64.rpm
> virtualbox-kernel-desktop-latest-6.1.40-2.mga8.x86_64.rpm
> virtualbox-kernel-server-latest-6.1.40-2.mga8.x86_64.rpm

Windows 10 version 22H2 is running fine in VirtualBox 6.1.40 with kernel 5.19.16 on the host machine (i7-12700 CPU with 32GB RAM).

Testing as host kernel-5.15.74-desktop-1, kmods yet not installed, and I saw dkms built module;

$ uname -a
Linux svarten.tribun 5.15.74-desktop-1.mga8 #1 SMP Sat Oct 15 19:19:46 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

$ dkms status | grep virtualbox
virtualbox, 6.1.40-1.mga8, 5.19.16-desktop-1.mga8, x86_64: installed 
virtualbox, 6.1.40-1.mga8, 5.15.74-desktop-1.mga8, x86_64: installed  
virtualbox, 6.1.38-1.2.mga8, 5.19.16-desktop-1.mga8, x86_64: installed-binary from 5.19.16-desktop-1.mga8
virtualbox, 6.1.38-1.2.mga8, 5.15.74-desktop-1.mga8, x86_64: installed-binary from 5.15.74-desktop-1.mga8

Quick tests of Guest 1 & 2 per Comment 14 OK


Installed kmods; 
used drakrpm to install virtualbox-kernel-5.15.74-desktop-1.mga8-6.1.40-1.mga8.x86_64
... and command line for the backport;
$ LC_ALL=C sudo urpmi.update 'Core Backports Testing' && LC_ALL=C sudo urpmi --search-media 'Core Backports Testing' virtualbox-kernel-desktop-latest

$ dkms status | grep virtualbox
virtualbox, 6.1.40-1.mga8, 5.19.16-desktop-1.mga8, x86_64: installed 
virtualbox, 6.1.40-1.mga8, 5.15.74-desktop-1.mga8, x86_64: installed 
virtualbox, 6.1.40-1.mga8, 5.19.16-desktop-1.mga8, x86_64: installed-binary from 5.19.16-desktop-1.mga8
virtualbox, 6.1.40-1.mga8, 5.15.74-desktop-1.mga8, x86_64: installed-binary from 5.15.74-desktop-1.mga8

That looks as it use to but who do I interprete that? Do I have two modules now for each kernel?  How do I know which will be used next boot?  Is there something to uninstall o be sure?

(In reply to Morgan Leijström from comment #17)

> That looks as it use to but who do I interprete that? Do I have two modules
> now for each kernel?  How do I know which will be used next boot?  Is there
> something to uninstall o be sure?

you can uninstall dkms-virtualbox

Ah thanks.
Dumping my detour for self and others'reference:

$ sudo urpme dkms-virtualbox

-reboot-

$ dkms status | grep virtualbox
virtualbox, 6.1.40-1.mga8, 5.19.16-desktop-1.mga8, x86_64: installed-binary from 5.19.16-desktop-1.mga8
virtualbox, 6.1.40-1.mga8, 5.15.74-desktop-1.mga8, x86_64: installed-binary from 5.15.74-desktop-1.mga8

$ VirtualBox 
WARNING: The vboxdrv kernel module is not loaded. Either there is no module
         available for the current kernel (5.15.74-desktop-1.mga8) or it failed to
         load. Please recompile the kernel module and install it by

           sudo /sbin/vboxconfig

         You will not be able to start VMs until this problem is fixed.

Hmff, I choose to reinstall 

$ sudo urpme virtualbox-kernel-5.19.17-desktop-1.mga8-6.1.40-2.mga8.x86_64 virtualbox-kernel-5.15.74-desktop-1.mga8-6.1.40-1.mga8.x86_64

  (...that also removed virtualbox.)

$ sudo urpmi virtualbox virtualbox-kernel-5.15.74-desktop-1.mga8-6.1.40-1.mga8.x86_64

§ sudo urpmi --search-media 'Core Backports Testing' virtualbox-kernel-desktop-latest

$ dkms status | grep virtualbox
virtualbox, 6.1.40-1.mga8, 5.19.16-desktop-1.mga8, x86_64: installed-binary from 5.19.16-desktop-1.mga8
virtualbox, 6.1.40-1.mga8, 5.15.74-desktop-1.mga8, x86_64: installed-binary from 5.15.74-desktop-1.mga8

§ VirtualBox

WORKS :)
(no reboot needed)


------


* Tests OK with kernel 5.15.74-desktop-1 and kmods *

All tests on guests as in Comment 14 performed.
(except Windows 7 needed not update guest additions of course)

* same system again, tests OK with kernel 5.19.16-desktop-1 and kmods *

All tests on guests as in Comment 14 performed again, minus chip programmer)

MGA8-64 Plasma, on an HP Pavilion 15. No installation issues, and no issues upgrading the extension pack from the gui.

All existing guests ran fine, including Windows 7. Windows 7 downloaded and inserted guest additions without incident.

I ran into a bit of trouble when trying to create a new guest with the Mageia 9 alpha1 iso. When setting vbox to simulate EFI hardware, the iso refused to work. It got as far as "loading the program" and then crashed the gui. Something about the keyboard buffer. The install continued in text mode, but I aborted it.

Another guest creation in non-EFI mode was successful, as was an EFI install from the Mageia 8 Classic iso, so I believe it is most likely the alpha1 iso that has the problem, not VirtualBox.

CC: (none) => andrewsfarm

enough tests, flushing out

and yes, there might be some hiccups for mga9 alpha isos..

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

An update for this issue has been pushed to the Mageia Updates repository.

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

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