Regular update. It have been sitting in updates_testing already a month. Time to open bug. Advisory, changelog required. I find it OK in my usual test: --- mga9 x86_64 OK here, host hardware see below. Running MSW 7 64 bit guest: it detected it needed new guest addition - i let it download, update, reboot. All OK: 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, Windows update. Host: [morgan@svarten ~]$ inxi -SMCG System: Host: svarten.tribun Kernel: 6.6.93-desktop-1.mga9 arch: x86_64 bits: 64 Desktop: KDE Plasma v: 5.27.10 Distro: Mageia 9 Machine: Type: Desktop Mobo: ASRock model: P55 Pro serial: <superuser required> BIOS: American Megatrends v: P2.60 date: 08/20/2010 CPU: Info: quad core model: Intel Core i7 870 bits: 64 type: MT MCP cache: L2: 1024 KiB Speed (MHz): avg: 1205 min/max: 1200/2934 cores: 1: 1205 2: 1205 3: 1205 4: 1205 5: 1205 6: 1205 7: 1205 8: 1205 Graphics: Device-1: Advanced Micro Devices [AMD/ATI] Navi 24 [Radeon RX 6400/6500 XT/6500M] driver: amdgpu v: kernel Display: x11 server: X.org v: 1.21.1.8 with: Xwayland v: 22.1.9 driver: X: loaded: amdgpu,v4l dri: radeonsi gpu: amdgpu resolution: 3840x2160~60Hz API: EGL v: 1.5 drivers: kms_swrast,radeonsi,swrast platforms: gbm,x11,surfaceless,device API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 25.0.7 renderer: AMD Radeon RX 6400 (radeonsi navi24 LLVM 15.0.6 DRM 3.54 6.6.93-desktop-1.mga9)
CC: (none) => ghibomgx
Until Giuseppe's confirmation that this is ready for QA We should hold the test, usually should be in company of static and dynamic modules
Keywords: (none) => feedback
Source RPM: virtualbox-7.1.8-1 => virtualbox-7.1.8-1, kmod-virtualbox
RPMS: dkms-virtualbox-7.1.10-1.mga9 python-virtualbox-7.1.10-1.mga9 virtualbox-7.1.10-1.mga9 virtualbox-devel-7.1.10-1.mga9 virtualbox-guest-additions-7.1.10-1.mga9 virtualbox-kernel-6.6.93-desktop-1.mga9-7.1.10-4.mga9 virtualbox-kernel-6.6.93-server-1.mga9-7.1.10-4.mga9 virtualbox-kernel-desktop-latest-7.1.10-4.mga9 virtualbox-kernel-server-latest-7.1.10-4.mga9 SRPMS: kmod-virtualbox-7.1.10-4.mga9 virtualbox-7.1.10-1.mga9
Keywords: feedback => (none)
URL: (none) => https://www.virtualbox.org/wiki/Changelog-7.1#v10
Keywords: (none) => advisory
i586 rpms: virtualbox-7.1.10-1.mga9 virtualbox-guest-additions-7.1.10-1.mga9
CC: (none) => andrewsfarm
(In reply to katnatek from comment #1) > Until Giuseppe's confirmation that this is ready for QA Ah, I forgot to tell he told me I could open the bug. > We should hold the test, usually should be in company of static and dynamic > modules Yes you are correct, they should be built. Anyway we also should test, and I usually do, and did in comment 0, that it work with dkms built kmods. And for kernel-linus we ship no binary kmods so there dkms is the only option. For kernel 6.12 currently in testing, VirtualBox need a workaround Bug 34408 Comment 3
I usually use our kmods, as I believe that is what the casual user who simply installs virtualbox would be using. MGA9-64 Plasma, two systems, no installation issues. Ran Win7 and Win10 guests, updated guest additions. With the Win7 guest on one system, the iso downloaded by the vbox gui failed to install, but one downloaded manually from https://download.virtualbox.org/virtualbox/ had no issues. A bad download, perhaps, because another Win7 guest on another system had no problems downloading and installing using the vbox gui. Ran each system for a while, mostly catching up on various updates. (Windows takes so LONG to update sometimes.) No other issues to report. It was time to go to bed by then, so I didn't try any Mageia guests yet. Perhaps tonight.
Ran a Mageia 9 guest, got updates including new guest additions, rebooted, no issues apparent. Still need to try creating a new guest, but no time again now.
Created a new Mageia 9 guest with no issues. I think this is ready to go. Validating.
Keywords: (none) => validated_updateWhiteboard: (none) => MGA9-64-OKCC: (none) => sysadmin-bugs
An update for this issue has been pushed to the Mageia Updates repository. https://advisories.mageia.org/MGAA-2025-0068.html
Resolution: (none) => FIXEDStatus: NEW => RESOLVED