Bug 30507 - Update request: virtualbox-6.1.34-1.5.mga8
Summary: Update request: virtualbox-6.1.34-1.5.mga8
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 8
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: QA Team
QA Contact:
Whiteboard: MGA8-64-OK
Keywords: advisory, validated_update
Depends on:
Reported: 2022-06-03 23:32 CEST by Thomas Backlund
Modified: 2022-06-09 22:50 CEST (History)
4 users (show)

See Also:
Source RPM: virtualbox
Status comment:


Description Thomas Backlund 2022-06-03 23:32:21 CEST
Adds support for kernel 5.18 series and a fix for some windows vms crashing




Comment 1 Frédéric "LpSolit" Buclin 2022-06-04 12:58:46 CEST
Do you also have a new virtualbox-kernel for kernel 5.18.1? I already installed 5.18.1 and virtualbox fails to start my Windows 10 VM:

"Kernel driver not installed (rc=-1908)

The VirtualBox Linux kernel driver is either not loaded or not set up correctly."

CC: (none) => LpSolit

Comment 2 Thomas Backlund 2022-06-04 16:16:11 CEST
(In reply to Frédéric "LpSolit" Buclin from comment #1)
> Do you also have a new virtualbox-kernel for kernel 5.18.1? I already
> installed 5.18.1 and virtualbox fails to start my Windows 10 VM:

that cant be built until the core updates package is validated.

but you can use dkms-virtualbox
Frédéric "LpSolit" Buclin 2022-06-04 17:32:50 CEST

CC: LpSolit => (none)

Comment 3 Dave Hodgins 2022-06-04 21:59:44 CEST
Pleased to note this update finally fixes bug 26214 where vboxsf mounted host
files had corruption for i586 guests.

Tested ok with i586 and x86_64 Mageia 8 guests.

CC: (none) => davidwhodgins

Comment 4 Dave Hodgins 2022-06-05 00:04:15 CEST
Argh. Seems I was wrong about it fixing bug 26214. No new regressions found
Comment 5 Morgan Leijström 2022-06-05 22:04:10 CEST
OK at my usual test/workstation; nvidia-current, Plasma

Testing with kernel 5.15.43-desktop-1.mga8

Updated VirtualBox packages, reboot

dkms status is OK

No update needed of extpack (I usually use command line to install the upstream extpack, for USB2 etc.), Nor VBoxGuestAdditions in my MSW7 guest (usually done by guest window menu)

Performed the tests I use to:

Guest 1: system MSW7pro 64 bit:
  Dynamically resizing guest window by mouse
  Shared clipboard, bidirectional
  Shared folders bidirectional read/write copying, and readonly works correctly.
  Drag a file from host Dolphin to guest Explorer
  USB2: flash stick and Brother Ptouch label writer
  Sound, Internet, performance: playing video in Firefox
  Windows update (antivirus definitions)

Guest 2: BOINC LHC@home "ATLAS simulation 2.00" VirtualBox VM

CC: (none) => fri

Comment 6 Thomas Andrews 2022-06-09 20:20:19 CEST
MGA8-64 Plasma system. No installation issues.

Windows XP and Windows 7 Pro guests do not crash, but then I hadn't had either of them crash before the update, either. (Wondering, not for the first time, why I keep the XP guest around.)

Tried various Mageia guests, with no issues noted.

CC: (none) => andrewsfarm

Comment 7 Thomas Andrews 2022-06-09 20:25:08 CEST
No new issues, that is. Confirming that bug 26214 is still in effect.
Comment 8 Morgan Leijström 2022-06-09 21:09:28 CEST
(In reply to Thomas Andrews from comment #6)
> (Wondering, not for the first time, why I keep the XP guest around.)

Nice to know it works.
I am pondering to install XP in VB on my laptop as it happens (twice last week) that i need to use laptop with XP and serial port for servicing old machinery.
I dual boot it with MSW10 but MSW10 is pretty useless, no old program works...
My Thinkpad T43 with dock still works, and i dual boot with mga8.
Impressive outclasing of hardware support, Microsoft versus floss :)
Comment 9 Dave Hodgins 2022-06-09 21:15:09 CEST

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

Dave Hodgins 2022-06-09 21:23:11 CEST

Keywords: (none) => advisory

Comment 10 Mageia Robot 2022-06-09 22:50:45 CEST
An update for this issue has been pushed to the Mageia Updates repository.


Resolution: (none) => FIXED

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