Bug 26291 - VBoxClient segfaults every 5 seconds
Summary: VBoxClient segfaults every 5 seconds
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Kernel and Drivers maintainers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-03-03 00:26 CET by Martin Whitaker
Modified: 2020-06-01 09:29 CEST (History)
1 user (show)

See Also:
Source RPM: virtualbox-6.1.4-1.mga8
CVE:
Status comment:

Attachments
Screenshot of guest showing segfault in journal (220.48 KB, image/png)
2020-03-03 00:26 CET, Martin Whitaker 		Details
Patch (1.93 KB, patch)
2020-03-29 22:11 CEST, Giuseppe Ghibò 		Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Description Martin Whitaker 2020-03-03 00:26:15 CET 
Created attachment 11534 [details]
Screenshot of guest showing segfault in journal

This is running a cauldron guest on a mga7 host. Screenshot of fault attached, because the bi-directional clipboard isn't working (maybe due to this bug?).

Host is:
  Ryzen 2400G, 16G RAM
  kernel-desktop-5.5.6-2.mga7-1-1.mga7
  virtualbox-kernel-5.5.6-desktop-2.mga7-6.0.18-4.mga7
  virtualbox-6.0.18-1.mga7
  VirtualBox Extension Pack 6.0.18r136238

Guest is:
  4 processors, 4GB RAM, AMD-V acceleration, KVM Paravirtualization
  VBoxSVGA, 16MB, 3D acceleration
  kernel-desktop-5.5.7-1.mga8-1-1.mga8
  virtualbox-guest-additions-6.1.4-1.mga8
  x11-driver-video-vboxvideo-1.0.0-6.mga8

Switching the guest display to VMSVGA avoids the segfault, but loses several useful features, including console display during boot and the bi-directional clipboard.

The fault still occurs with VBoxVGA, no 3D acceleration.
Comment 1 Giuseppe Ghibò 2020-03-29 22:11:49 CEST 
Created attachment 11567 [details]
Patch

CC: (none) => ghibomgx

Comment 2 Giuseppe Ghibò 2020-03-29 22:13:23 CEST 
Here is a fix, borrowed from Arch:

https://git.archlinux.org/svntogit/community.git/commit/trunk?h=packages/virtualbox&id=50a7cdc3fbae69be2d3a465eecde5aa1789866b1

Tested locally. It Works.
Comment 3 Giuseppe Ghibò 2020-05-07 18:16:25 CEST 
Upgrade to Virtualbox 6.1.6 resolved this issue too. I think this bug can be closed.
Comment 4 Martin Whitaker 2020-06-01 09:29:44 CEST 
Indeed, it is fixed now.

Resolution: (none) => FIXED
Status: NEW => RESOLVED
Note You need to log in before you can comment on or make changes to this bug.