- win 11 host
- Fedora 39 (last iso just installed and updated)
- guest loads until login screen, then crash or freeze on the first interaction (clicking my username)
- works ok without 3D acceleration
[7.0.14] Crash when using 3D acceleration
-
- Posts: 2
- Joined: 16. Feb 2024, 16:57
[7.0.14] Crash when using 3D acceleration
Hi, I can't figure out what's the issue:
- Attachments
-
- VBox.zip
- (22.28 KiB) Downloaded 26 times
-
- Posts: 2
- Joined: 16. Feb 2024, 16:57
Re: [7.0.14] Crash when using 3D acceleration
Just took the time to check the kernel logs on the guest.
While running without 3D acceleration:
There are strange interruptions and repeated attempts at service creation, not sure if that's ok. Note the only line colored red in dmesg: "vboxsf: Unknown parameter 'tag'"
While running with 3D acceleration:
The kernel log stops after 3 seconds, so nothing of interest there.
While running without 3D acceleration:
There are strange interruptions and repeated attempts at service creation, not sure if that's ok. Note the only line colored red in dmesg: "vboxsf: Unknown parameter 'tag'"
Code: Select all
[ 4.393385] vboxguest: host-version: 7.0.14r161095 0x8000000f
[ 4.394034] vbg_heartbeat_init: Setting up heartbeat to trigger every 2000 milliseconds
[ 4.394776] input: PC Speaker as /devices/platform/pcspkr/input/input6
[ 4.399094] input: VirtualBox mouse integration as /devices/pci0000:00/0000:00:04.0/input/input7
[ 4.412975] RAPL PMU: API unit is 2^-32 Joules, 0 fixed counters, 10737418240 ms ovfl timer
[ 4.418119] lpc_ich 0000:00:1f.0: I/O space for GPIO uninitialized
[ 4.445650] leds_ss4200: no LED devices found
[ 4.465425] iTCO_vendor_support: vendor-support=0
[ 4.470337] iTCO_wdt iTCO_wdt.1.auto: Found a ICH7-M or ICH7-U TCO device (Version=2, TCOBASE=0x8060)
[ 4.470370] iTCO_wdt iTCO_wdt.1.auto: timeout value out of range, using 30
[ 4.470700] iTCO_wdt iTCO_wdt.1.auto: initialized. heartbeat=30 sec (nowayout=0)
[ 4.506507] EXT4-fs (sda2): mounted filesystem f474e621-e1ce-4f75-9c5c-005f5375642c r/w with ordered data mode. Quota mode: none.
[ 4.793832] snd_intel8x0 0000:00:05.0: intel8x0_measure_ac97_clock: measured 51659 usecs (2400 samples)
[ 4.793836] snd_intel8x0 0000:00:05.0: clocking to 49593
[ 4.880646] 17:10:40.663603 main VBoxClient 7.0.14_Fedora r161095 (verbosity: 0) linux.amd64 (Jan 16 2024 00:00:00) release log
17:10:4
[ 4.881272] 17:10:40.664654 main OS Product: Linux
[ 4.881561] 17:10:40.664878 main OS Release: 6.7.4-200.fc39.x86_64
[ 4.881997] 17:10:40.665166 main OS Version: #1 SMP PREEMPT_DYNAMIC Mon Feb 5 22:21:14 UTC 2024
[ 4.882668] 17:10:40.665630 main Executable: /usr/bin/VBoxDRMClient
17:10:40.665630 main Process ID: 876
17:10:40.665631 main P
[ 4.883731] 17:10:40.666905 main VBoxDRMClient: found compatible device: /dev/dri/renderD128
[ 4.884960] 17:10:40.668045 main VBoxDRMClient: IPC server socket access granted to all users
[ 4.886759] 17:10:40.669678 DrmResizeThread VBoxDRMClient: push screen layout data of 1 display(s) to DRM stack, fPartialLayout=false, rc=V
[ 4.894883] 17:10:40.677801 main VBoxService 7.0.14_Fedora r161095 (verbosity: 0) linux.amd64 (Jan 16 2024 00:00:00) release log
17:10:
[ 4.896083] 17:10:40.679430 main OS Product: Linux
[ 4.896418] 17:10:40.679692 main OS Release: 6.7.4-200.fc39.x86_64
[ 4.897697] 17:10:40.680814 main OS Version: #1 SMP PREEMPT_DYNAMIC Mon Feb 5 22:21:14 UTC 2024
[ 4.898466] 17:10:40.681381 main Executable: /usr/sbin/VBoxService
17:10:40.681382 main Process ID: 885
17:10:40.681383 main Pa
[ 4.901075] 17:10:40.684236 main 7.0.14_Fedora r161095 started. Verbose level = 0
[ 4.901826] 17:10:40.684779 main VBoxClient 7.0.14_Fedora r161095 (verbosity: 0) linux.amd64 (Jan 16 2024 00:00:00) release log
17:10:4
[ 4.902193] 17:10:40.685575 main OS Product: Linux
[ 4.902660] 17:10:40.685828 main vbglR3GuestCtrlDetectPeekGetCancelSupport: Supported (#1)
[ 4.902952] 17:10:40.685844 main OS Release: 6.7.4-200.fc39.x86_64
[ 4.903607] 17:10:40.686754 main OS Version: #1 SMP PREEMPT_DYNAMIC Mon Feb 5 22:21:14 UTC 2024
[ 4.904322] 17:10:40.687300 main Executable: /usr/bin/VBoxDRMClient
17:10:40.687300 main Process ID: 898
17:10:40.687301 main P
[ 4.904742] 17:10:40.687969 main VBoxDRMClient: already running, exiting
[ 4.918885] vboxsf: Unknown parameter 'tag'
[ 4.920849] 17:10:40.703824 automount vbsvcAutomounterMountIt: Running outdated vboxsf module without support for the 'tag' option?
[ 4.922088] 17:10:40.705131 automount vbsvcAutomounterMountIt: Successfully mounted 'shared' on '/home/guiohm/shared'
[ 5.041435] RPC: Registered named UNIX socket transport module.
[ 5.041438] RPC: Registered udp transport module.
[ 5.041438] RPC: Registered tcp transport module.
[ 5.041439] RPC: Registered tcp-with-tls transport module.
[ 5.041439] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 5.152859] NET: Registered PF_QIPCRTR protocol family
[ 5.480611] e1000: enp0s3 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
[ 7.135010] rfkill: input handler disabled
[ 15.110648] rfkill: input handler enabled
[ 16.044154] rfkill: input handler disabled
[ 16.045166] 17:10:51.393558 main VBoxClient 7.0.14_Fedora r161095 (verbosity: 0) linux.amd64 (Jan 16 2024 00:00:00) release log
17:10:5
[ 16.054374] 17:10:51.403236 main OS Product: Linux
[ 16.060223] 17:10:51.408995 main OS Release: 6.7.4-200.fc39.x86_64
[ 16.061962] 17:10:51.410616 main OS Version: #1 SMP PREEMPT_DYNAMIC Mon Feb 5 22:21:14 UTC 2024
[ 16.062715] 17:10:51.411080 main Executable: /usr/bin/VBoxClient
17:10:51.411081 main Process ID: 2218
17:10:51.411081 main Pac
[ 16.066489] 17:10:51.414874 main VBoxClient 7.0.14_Fedora r161095 started. Verbose level = 0. Wayland environment detected: yes
[ 16.066839] 17:10:51.415685 main Service: Shared Clipboard
[ 16.067842] 17:10:51.416674 main Initializing service ...
[ 16.068127] 17:10:51.416958 main Creating worker thread ...
[ 17.020107] 17:10:52.368583 main VBoxClient 7.0.14_Fedora r161095 (verbosity: 0) linux.amd64 (Jan 16 2024 00:00:00) release log
17:10:5
[ 17.020367] 17:10:52.369279 main OS Product: Linux
[ 17.020722] 17:10:52.369563 main OS Release: 6.7.4-200.fc39.x86_64
[ 17.021207] 17:10:52.369865 main OS Version: #1 SMP PREEMPT_DYNAMIC Mon Feb 5 22:21:14 UTC 2024
[ 17.021953] 17:10:52.370363 main Executable: /usr/bin/VBoxClient
17:10:52.370365 main Process ID: 2673
17:10:52.370365 main Pac
[ 17.022738] 17:10:52.371138 main VBoxClient 7.0.14_Fedora r161095 started. Verbose level = 0. Wayland environment detected: yes
[ 17.023198] 17:10:52.371953 main Service: VirtualBox host version check
[ 17.023959] 17:10:52.372864 main Service started
[ 17.024746] 17:10:52.373592 main Creating worker thread ...
[ 17.026216] 17:10:52.374718 main VBoxClient 7.0.14_Fedora r161095 (verbosity: 0) linux.amd64 (Jan 16 2024 00:00:00) release log
17:10:5
[ 17.026432] 17:10:52.374721 main Service started
[ 17.026650] 17:10:52.375555 main OS Product: Linux
[ 17.027075] 17:10:52.375892 main OS Release: 6.7.4-200.fc39.x86_64
[ 17.027587] 17:10:52.376272 main OS Version: #1 SMP PREEMPT_DYNAMIC Mon Feb 5 22:21:14 UTC 2024
[ 17.028305] 17:10:52.376761 main Executable: /usr/bin/VBoxClient
17:10:52.376762 main Process ID: 2678
17:10:52.376762 main Pac
[ 17.028973] 17:10:52.377534 main VBoxClient 7.0.14_Fedora r161095 started. Verbose level = 0. Wayland environment detected: yes
[ 17.029307] 17:10:52.378140 main Service: Seamless Mode Support
[ 17.030432] 17:10:52.379302 main Initializing service ...
[ 17.033516] 17:10:52.382373 main Creating worker thread ...
[ 17.034454] 17:10:52.383364 main Service started
[ 17.035195] 17:10:52.383685 main VBoxClient 7.0.14_Fedora r161095 (verbosity: 0) linux.amd64 (Jan 16 2024 00:00:00) release log
17:10:5
[ 17.035477] 17:10:52.384395 main OS Product: Linux
[ 17.035767] 17:10:52.384617 main OS Release: 6.7.4-200.fc39.x86_64
[ 17.036226] 17:10:52.384906 main OS Version: #1 SMP PREEMPT_DYNAMIC Mon Feb 5 22:21:14 UTC 2024
[ 17.036902] 17:10:52.385404 main Executable: /usr/bin/VBoxClient
17:10:52.385405 main Process ID: 2689
17:10:52.385405 main Pac
[ 17.037551] 17:10:52.386079 main VBoxClient 7.0.14_Fedora r161095 started. Verbose level = 0. Wayland environment detected: yes
[ 17.037818] 17:10:52.386719 main Service: Drag'n'Drop
[ 17.038920] 17:10:52.387772 main Initializing service ...
[ 17.042069] 17:10:52.390921 main Creating worker thread ...
[ 17.042792] 17:10:52.391473 dnd Proxy window=0x800001 (debug mode: false), root window=0x40b ...
[ 17.043117] 17:10:52.392027 main Service started
The kernel log stops after 3 seconds, so nothing of interest there.
-
- Posts: 7
- Joined: 22. Sep 2017, 20:05
Re: [7.0.14] Crash when using 3D acceleration
A couple thoughts -
1. The posted vbox.log says you are using Guest Additions 6.0.0 with your Fedora VM. Generally speaking, the build of Guest Additions you are supposed to use should match the build of Virtual Box you are using. Ergo, if you are running Virtual Box 7.0.14, you should install Guest Additions 7.0.14 in the VM. This is particularly important, as the Virtual Box 7.x series included a major rewrite of the graphics backend to utilize Vulkan / DX11 when 3D acceleration is enabled.
2. Your kernel log from the Fedora VM indicates you are running Fedora with a Linux 6.7.x kernel. Even the latest Virtual Box Guest Additions (i.e. 7.0.14), as per the Virtual Box changelog, is only compatible up to Linux 6.6.x kernels. Ergo, I would not expect the graphics drivers component of Guest Additions 7.0.14 will work with said 6.7.x Linux kernel, to say nothing of the even older Guest Additions 6.0.0 that you have installed.
Accordingly, my suggestion(s) would be -
- Downgrade the Linux kernel in your Fedora VM to 6.6.x or older; and
- Install Guest Additions 7.0.14 in the Fedora VM.
1. The posted vbox.log says you are using Guest Additions 6.0.0 with your Fedora VM. Generally speaking, the build of Guest Additions you are supposed to use should match the build of Virtual Box you are using. Ergo, if you are running Virtual Box 7.0.14, you should install Guest Additions 7.0.14 in the VM. This is particularly important, as the Virtual Box 7.x series included a major rewrite of the graphics backend to utilize Vulkan / DX11 when 3D acceleration is enabled.
2. Your kernel log from the Fedora VM indicates you are running Fedora with a Linux 6.7.x kernel. Even the latest Virtual Box Guest Additions (i.e. 7.0.14), as per the Virtual Box changelog, is only compatible up to Linux 6.6.x kernels. Ergo, I would not expect the graphics drivers component of Guest Additions 7.0.14 will work with said 6.7.x Linux kernel, to say nothing of the even older Guest Additions 6.0.0 that you have installed.
Accordingly, my suggestion(s) would be -
- Downgrade the Linux kernel in your Fedora VM to 6.6.x or older; and
- Install Guest Additions 7.0.14 in the Fedora VM.