QO Vision - VM player

Offen
#917 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 6 Tagen

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
3/5
Geschätzter Aufwand
1-2 Tage
Anfängerfreundlichkeit
38/100
Issue-Typ
Bug
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
c, linux

Rechercherichtung

Start with the VERR_VM_DRIVER_VERSION_MISMATCH error in the VirtualBoxVM runtime path and the reported /sbin/vboxconfig executable. Reproduce VM startup using the listed VirtualBox and ROSA host versions, then verify which installed host-driver build is loaded. The issue becomes actionable once the mismatched component is identified and a repeatable startup check is defined.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

bug
Version

7.2.18

Host OS Type

Linux

Host OS name + version

Operating System: ROSA Fresh Desktop 13 KDE Plasma Version: 6.6.6 KDE Frameworks Version: 6.29.0 Qt Version: 6.11.1 Kernel Version: 6.12.91-generic-24rosa13-x86_64 (64-bit) Graphics Platform: X11 Processors: 8 × 11th Gen Intel® Core™ i5-1135G7 @ 2.40GHz Memory: 32 ГиБ of RAM (31.1 ГиБ usable) Graphics Processor: Intel® Iris® Xe Graphics Manufacturer: Dell Inc. Product Name: Latitude 5420

Host Architecture

x86

Guest OS Type

Windows

Guest Architecture

x86

Guest OS name + version

Windows 10 X64

Component

Unspecified

What happened?

Failed to start up the machine with dialogue window:
RTR3InitEx failed with rc=-1912 (fRtFlags=0x10000) (rc=-1912)
The VirtualBox kernel modules do not match this version of VirtualBox. The installation of VirtualBox was apparently not successful. Executing '/sbin/vboxconfig' may correct this. Make sure that you are not mixing builds of VirtualBox from different sources.
where: supR3HardenedMainInitRuntime what: 4 VERR_VM_DRIVER_VERSION_MISMATCH (-1912) - The installed support driver doesn't match the version of the user.

How can we reproduce this?

Failure report from OS sais:
PID: 5082 (VirtualBoxVM)
UID: 500 (yura)
GID: 500 (yura)
Signal: 6 (ABRT)
Timestamp: Sat 2026-10-17 18:57:56 MSK (4s ago)
Command Line: /usr/lib64/virtualbox/VirtualBoxVM --comment $'Vision 5.16.0, Mod90 Biovue' --startvm d50c1494-204f-4f1b-802a-9a46a658c54a --no-startvm-errormsgbox
Executable: /usr/lib64/virtualbox/VirtualBoxVM
Control Group: /user.slice/user-500.slice/[email protected]/app.slice/app-rosa\[email protected]
Unit: [email protected]
User Unit: app-rosa\[email protected]
Slice: user-500.slice
Owner UID: 500 (yura)
Boot ID: c536d4dd277a48d98b66f8bcdfbc7296
Machine ID: 9369777b44ce4cc1af70138b355d712c
Hostname: rosa-rb2cjk
Storage: /var/lib/systemd/coredump/core.VirtualBoxVM.500.c536d4dd277a48d98b66f8bcdfbc7296.5082.1792252676000000.zst (inaccessible)
Message: Process 5082 (VirtualBoxVM) of user 500 dumped core.

            Stack trace of thread 5082:
            #0  0x00007fcb3d527f5c __pthread_kill_implementation (libc.so.6 + 0x94f5c)
            #1  0x00007fcb3d4d34f6 raise (libc.so.6 + 0x404f6)
            #2  0x00007fcb3d4bb878 abort (libc.so.6 + 0x28878)
            #3  0x00007fcb31af062f _ZL10qt_message9QtMsgTypeRK18QMessageLogContextPKcP13__va_list_tag.cold (libQt6Core.so.6 + 0xf062f)
            #4  0x00007fcb31af11ca _ZNK14QMessageLogger5fatalEPKcz (libQt6Core.so.6 + 0xf11ca)
            #5  0x00007fcb382e5358 TrustedError.cold (VirtualBoxVM.so + 0x59358)
            #6  0x0000000000403c5d n/a (/usr/lib64/virtualbox/VirtualBoxVM + 0x3c5d)
            #7  0x0000000000403cd6 n/a (/usr/lib64/virtualbox/VirtualBoxVM + 0x3cd6)
            #8  0x0000000000403e6e n/a (/usr/lib64/virtualbox/VirtualBoxVM + 0x3e6e)
            #9  0x0000000000404510 n/a (/usr/lib64/virtualbox/VirtualBoxVM + 0x4510)
            #10 0x00007fcb3d4bd36c __libc_start_call_main (libc.so.6 + 0x2a36c)
            #11 0x00007fcb3d4bd429 __libc_start_main (libc.so.6 + 0x2a429)
            #12 0x00000000004025b5 n/a (/usr/lib64/virtualbox/VirtualBoxVM + 0x25b5)
            ELF object binary architecture: AMD x86-64
Did you upload all of your necessary log files, screenshots, etc.?
  • Yes, I've uploaded all pertinent files to this issue.
Vorherrschende Sprache
C
Sterne
1.4k
Forks
219
PR-Merge-Kennzahlen
Keine gemergten PRs in 30 T.

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus VirtualBox/virtualbox

Alle Issues in VirtualBox/virtualbox

Ähnliche Issues

Weitere Issues zu C

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.