Thank you for the heads up.

CC: (none) => fri
Assignee: bugsquad => kernel

virtualbox-7.1.8-1.mga9 is available in core/updates_testing

Still missing the kmod-virtualbox module. Waiting for completing bug #34189 to avoid overlapping. In the meanwhile you can use with the dkms-virtualbox module. There is also the virtualbox-kvm (which works alongside with qemu and doesn't require the extra modules) in my copr page.

CC: (none) => ghibomgx

mga9-64 OK using local dkms built kmod

[morgan@svarten ~]$ dkms status
virtualbox, 7.1.8-1.mga9, 6.6.87-desktop-1.mga9, x86_64: installed 
virtualbox, 7.1.8-1.mga9, 6.6.87-1.mga9, x86_64: installed 
virtualbox, 7.1.8-1.mga9, 6.6.87-server-1.mga9, x86_64: installed 

For now only tested with kernel-desktop-6.6.87-1.mga9

As test I took a (compacted backup of) my usual Windows 7 guest and perfomed same test as usual.  On first launch using the menu in VirtualBox guest window frame, I fed it the guest additions, and it then downloaded the correct version and installed, and I let it reboot.

Then I tested dynamic window resizing, USB 2 flash disk, host folder sharing write protected and not, bidirectional clipboard, drag file from Dolphin to Explorer, Internet video in Firefox.

One minor problem.

(I saw it already during testing for Comment 4 but thought it was due to a mistake i made in moving a VM, but now i could repeat on another system.)

On first launch after updating VirtualBox (and rebooting), it segfaults:

[morgan@republic ~]$ VirtualBox 
Qt WARNING: Qt: Session management error: Authentication Rejected, reason : MIT-MAGIC-COOKIE-1 authentication rejected
Qt WARNING: QObject::connect(UITranslationEventListener, QIRichTextLabel): invalid nullptr parameter
Qt WARNING: QObject::connect(UITranslationEventListener, QIArrowButtonPress): invalid nullptr parameter
Qt WARNING: QObject::connect(UITranslationEventListener, QIArrowButtonPress): invalid nullptr parameter
Qt WARNING: QObject::connect(UITranslationEventListener, QIArrowSplitter): invalid nullptr parameter
Qt WARNING: QObject::connect(UITranslationEventListener, QIDialogButtonBox): invalid nullptr parameter
Segmenteringsfel (minnesutskrift skapad)

Just launch again and it is OK.


Now i tested a fresh install of VB on a third machine and there this problem did not show.

Do other testers see this too?

Ready to test, including kmod for kernel 6.6.88-3

---

Test OK on Asus G75V, nvidia470

More spec see: Kernel tests per Bug 34189 comment #41 revisted: full OK using desktop 6.6.88-3

Tested both dkms built kmod as well as our binary package:

Using Win XP guest, vdi prepared by someone else originally for VB6
Updated Guest extension pack when under Windows 11 VB7.1.8 host, then copied to this machine.
Basic settings: W32 mode, 1 core, nested paging, PAE/NX, VBoxVGA
Dynamic window size and full screen.
Sound.
Bidirectional clipboard text.
Drag file from Explorer in guest to Dolphin in host.
Host folder sharing.
Performing time critical protocol "PPI" over USB2 with old Siemens S7-200 CPU using adapter dongle cable. (same guest fails this running on Windows 11 VB 7.1.8 host even on a much faster machine! Guest vdi was copied from that W11 system.)
Network not enabled; i dont want it to connect to Internet.

Assignee: kernel => qa-bugs

Tests OK on my workstation, with various kernels:
desktop and server 6.6.88-3: Bug 34189 Comment 71 
linus 6.6.88-1: Bug 34191 Comment 19

Packages

Source RPMS
virtualbox-7.1.8-1.mga9
kmod-virtualbox-7.1.8-1.mga9

Repository: 9-x86_64-core-updates_testing
dkms-virtualbox-7.1.8-1.mga9
python-virtualbox-7.1.8-1.mga9
virtualbox-7.1.8-1.mga9
virtualbox-devel-7.1.8-1.mga9
virtualbox-guest-additions-7.1.8-1.mga9
virtualbox-kernel-6.6.88-desktop-3.mga9-7.1.8-1.mga9
virtualbox-kernel-6.6.88-server-3.mga9-7.1.8-1.mga9
virtualbox-kernel-desktop-latest-7.1.8-1.mga9
virtualbox-kernel-server-latest-7.1.8-1.mga9


Repository: 9-i586-core-updates_testing
virtualbox-7.1.8-1.mga9
virtualbox-guest-additions-7.1.8-1.mga9

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

> Tested both dkms built kmod as well as our binary package:

Woops, I now realise the binary packages i used is for the previous VB version.
Anyway, it worked.

[morgan@svarten ~]$ rpm -qa|grep virtualbox
dkms-virtualbox-7.1.8-1.mga9
virtualbox-7.1.8-1.mga9
virtualbox-kernel-6.6.88-server-3.mga9-7.0.24-70.mga9
virtualbox-kernel-6.6.88-desktop-3.mga9-7.0.24-70.mga9

Updated versions now installed from testing repo

[morgan@svarten ~]$ rpm -qa|grep virtualbox
dkms-virtualbox-7.1.8-1.mga9
virtualbox-7.1.8-1.mga9
virtualbox-kernel-6.6.88-server-3.mga9-7.1.8-1.mga9
virtualbox-kernel-6.6.88-desktop-3.mga9-7.1.8-1.mga9

Iĺl test in a couple days.

Hello everyone, I have already had this problem in the installation of virtualbox for several versions. It appears in rpmdrake that the version of the kernel to be installed is older than the current one and does not allow me to install virtualbox. 

I can install from terminal by selecting the correct kernel, but this is not functional for a user who uses rpmdrake to install applications.

CC: (none) => Joselp

Created attachment 14968 [details]
Error installing Virtualbox

This is the error that I get when installing Virtualbox from rpmdrake.

Do i read/guess correctly  it complains about 6.6.88-1 and 6.6.88-3 desktop kernels are installed, and it wants an older kernel 6.6.65-2?

I guess it wants to install elder virtualbox-kernel package that then requires that kernel.

If so, root cause is it select not the latest virtualbox-kernel?

How can that be?
Packaging or drakrpm fault?

---

PS/

In future you could make English screenshots i.e by launching mcc like

 LC_ALL=C  mcc

/DS

Do urpmi work different in that case?

MGA9-64, ‎AMD Ryzen 5 2600, Nvidia 1650 super, GNOME, virtualbox host

The following 14 packages are going to be installed:

- dkms-virtualbox-7.1.8-1.mga9.x86_64
- lib64qt6-database-plugin-ibase-6.4.1-5.1.mga9.x86_64
- lib64qt6-database-plugin-sqlite-6.4.1-5.1.mga9.x86_64
- lib64qt6help6-6.4.1-2.mga9.x86_64
- lib64qt6scxml6-6.4.1-2.mga9.x86_64
- lib64qt6scxmlqml6-6.4.1-2.mga9.x86_64
- lib64qt6sql6-6.4.1-5.1.mga9.x86_64
- lib64qt6statemachine6-6.4.1-2.mga9.x86_64
- lib64qt6statemachineqml6-6.4.1-2.mga9.x86_64
- lib64qt6xml6-6.4.1-5.1.mga9.x86_64
- qtscxml6-6.4.1-2.mga9.x86_64
- virtualbox-7.1.8-1.mga9.x86_64
- virtualbox-kernel-6.6.88-server-3.mga9-7.1.8-1.mga9.x86_64
- virtualbox-kernel-server-latest-7.1.8-1.mga9.x86_64

14MB of additional disk space will be used.

59MB of packages will be retrieved.



--- rebooted and downloaded the Extensions


- VM's are working on Vbox (64/Xfce)
- new VM working (i586/mate)
- used remote desktop to access, that works - note, it now default to TLS.  You may need to switch to RDP security in order to use default xfreerdp connection.

CC: (none) => brtians1

(In reply to Jose Manuel López from comment #12)
> Hello everyone, I have already had this problem in the installation of
> virtualbox for several versions. It appears in rpmdrake that the version of
> the kernel to be installed is older than the current one and does not allow
> me to install virtualbox. 
> 
> I can install from terminal by selecting the correct kernel, but this is not
> functional for a user who uses rpmdrake to install applications.

Confirmed, but it should be fixed with this update. 

I just tried to use MCC to do a new install of virtualbox 7.0.24, and I got this list for dependencies:

To satisfy dependencies, the following package(s) also need to be installed:

- kernel-desktop-6.6.65-2.mga9.x86_64
- virtualbox-7.0.24-1.mga9.x86_64
- virtualbox-kernel-6.6.65-desktop-2.mga9-7.0.24-63.mga9.x86_64
- virtualbox-kernel-6.6.88-desktop-3.mga9-7.0.24-70.mga9.x86_64
- virtualbox-kernel-desktop-latest-7.0.24-70.mga9.x86_64

Note the kmod for kernel 6.6.65 is on the list, even though that kernel isn't installed. But, with packages from comment 10 downloaded by qarepo, if you install virtualbox 7.1.8 from MCC, you get this:

To satisfy dependencies, the following package(s) also need to be installed:

- lib64qt6help6-6.4.1-2.mga9.x86_64
- lib64qt6scxml6-6.4.1-2.mga9.x86_64
- lib64qt6scxmlqml6-6.4.1-2.mga9.x86_64
- lib64qt6statemachine6-6.4.1-2.mga9.x86_64
- lib64qt6statemachineqml6-6.4.1-2.mga9.x86_64
- lib64qt6xml6-6.4.1-5.1.mga9.x86_64
- qtscxml6-6.4.1-2.mga9.x86_64
- virtualbox-kernel-6.6.88-desktop-3.mga9-7.1.8-1.mga9.x86_64
- virtualbox-kernel-desktop-latest-7.1.8-1.mga9.x86_64

Note that the kmod for the old kernel is gone.

CC: (none) => andrewsfarm

Giuseppe, would you please make sure that the 6.6.88 kmod is not a direct dependency of virtualbox itself, but is only drawn in because of the kmod -latest package? 

Upon further reflection I think that may have been the reason why the older 6.6.65 kmod was a dependency of vbox 7.0.24.

I don't understand where the 6.6.65 comes from there. The kernel has been updated from 6.6.83 to 6.6.88-3.mga9, and was including the virtualbox-kernel-6.6.88-desktop-3.mga9-7.0.24-70.mga9.x86_64 and virtualbox-kernel-desktop-latest-7.0.24-70.mga9.x86_64 for older (current) virtualbox 7.0.24, so if virtualbox-kernel-desktop-latest was installed, retrieving all the upgrades would retrieve also virtualbox-kernel-6.6.88-desktop-3.mga9-7.0.24-70.mga9.x86_64. This should have closed all the older virtualbox updates cycle for current kernel 6.6.88-3.mga9.

Later there is virtualbox-kernel-desktop-latest-7.1.8-1.mga9.x86_64 which requires virtualbox-kernel-6.6.88-desktop-3.mga9-7.1.8-1.mga9.x86_64 (the package name is "virtualbox-kernel-6.6.88-desktop-3.mga9"). The package virtualbox-kernel-6.6.88-desktop-3.mga9-7.1.8-1.mga9.x86_64 can be installed even without installing the virtualbox package, it only has (as any previous releases) a "Recommends:" to virtualbox-kernel-desktop-latest, which can be avoided installin g it with --no-recommends.

But drakrpm, as run from MCC, doesn't include --no-recommends. (Correct me if I'm wrong) That's the way a lot of our users would install virtualbox.

All I can think of is that somehow, when vbox 7.0.24 was released it mistakenly included either a dependency or a recommends for the 6.6.65 kmod, as well as the kmod-latest. I just wanted to make sure that when we release 7.1.8 it doesn't include a similar recommends for the 6.6.88 kmod.

The QT6 dependencies are correct for VirtualBox 7.1.8, since the 7.1.x series is no longer compatible with QT5.

What you described seems to appears also in earlier versions of VirtualBox, such as VirtualBox 7.0.10 (which is also available in rpmdrake beside 7.0.24). What is weird is that rpmdrake doesn't show the other intermediate versions between 7.0.10 and 7.0.24, that are still available in core/updates.

From what I checked the dependency chains was not changed since much time.

It is strange that the VirtualBox package triggers the dependency 'virtualbox-kernel-6.6.65-desktop-2.mga9-7.0.24-63.mga9.x86_64' instead of the highest available version (i.e. virtualbox-kernel-6.6.88-desktop-3.mga9-7.0.24-70.mga9.x86_64), even though none of these versions were explicitly declared a dependency. virtualbox-kernel-6.6.65-desktop-2.mga9-7.0.24-63.mga9.x86_64 also triggers the kernel-desktop-6.6.65-2.mga9.x86_64, which is not installed.

The 'virtualbox-kernel' package is required by virtualbox with the dependency 'Requires: kmod(vboxdrv.ko) = %{version}', which is provided by both 'virtualbox-kernel-6.6.65...' and 'virtualbox-kernel-6.6.88-3.mga9...'. Also although there are intermediate versions between 6.6.65 and 6.6.88 (e.g., 6.6.74) in the core/updates repository, they are not shown in rpmdrake. Maybe it deserve a standalone bug.

MGA9-64 Plasma, i5-7500,nvidia Quadro K620 graphics. No installation issues.

Just did a quick test so far, running a Windows 10 guest and updating guest additions without issues. Well, it was meant to be a quick test, but there was the usual Windows stuff when you haven't used it for a while. All OK in the end, though. Will try a more thorough test later today.

Started some Mageia 9 guests, Plasma, Xfce, Gnome, most 64-bit but one 32-bit. Some  had not been started in months. Got updates including guest additions under test. Rebooted, checked shared folder access. Created a new Mageia 9 EFI guest using the netinstall iso.

No issues to report.

I tested this out.  Seems ok.  If there anything holding this up?

I noticed a discussion on a dependency missing for kernel desktop. Was that resolved?

I think this is good to go. Validating.

Keywords: (none) => validated_update
Whiteboard: (none) => MGA9-64-OK
CC: (none) => sysadmin-bugs

The advisory file only lists virtualbox-7.1.8-1.mga9 but not virtualbox-guest-additions or the kernels mentioned in comment 10. Should those be included in the update?

CC: (none) => dan

(In reply to Dan Fandrich from comment #26)
> The advisory file only lists virtualbox-7.1.8-1.mga9 but not
> virtualbox-guest-additions or the kernels mentioned in comment 10. Should
> those be included in the update?

Yes, the advisory is fixed now

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

https://advisories.mageia.org/MGAA-2025-0048.html

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