virtualbox.org

Virtualbox 6.1.12 r139181 (Qt5.9.5)
Windows 7 guest, running Solidworks in that VM.

I have had problems for years where after a few days of usage the host will segfault. After reading that it could be Wayland, I started to change a few things. It crashed again today, but did not make a file in /var/crash, but this did come out on the console.

Ignore the QCursor entries. They emit at startup.

michalk@michalk-desktop:~$ GDK_BACKEND=x11 VirtualBoxVM --startvm Win7
Qt WARNING: QCursor: Cannot create bitmap cursor; invalid bitmap(s)
Qt WARNING: QCursor: Cannot create bitmap cursor; invalid bitmap(s)
VirtualBoxVM: tpp.c:84: __pthread_tpp_change_priority: Assertion `new_prio == -1 || (new_prio >= fifo_min_prio && new_prio <= fifo_max_prio)' failed.
Aborted (core dumped)

I am no Linux guru, but I have googled a few things so this is fwiw

A segfault is a failure to read a memory address, so is a signal 11. I have seen something in the VboxSVC.log on a host that stayed running indicating a possible signal 11 when a guest aborted.

I wonder if your host memory is reliable. Virtual machines touch portions of memory that don't normally get touched, and it is not common for Virtualbox to segfault a host to the ground.

Can you run an intensive memory test on your host over the weekend?

Thanks for replying. Yes, I'll run one overnight.

I just had another crash, and this is the beginning of the core file. I can provide the full file on request.

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
Date: Fri Sep 4 14:19:20 2020
DistroRelease: Ubuntu 18.04
ExecutablePath: /usr/lib/virtualbox/VirtualBoxVM
ExecutableTimestamp: 1594458480
ProcCmdline: /usr/lib/virtualbox/VirtualBoxVM --comment Win7 --startvm fbcd0a3c-a29c-4849-9231-401e4a6cde22 --no-startvm-errormsgbox
ProcEnviron: Error: [Errno 13] Permission denied: 'environ'
ProcMaps: Error: [Errno 13] Permission denied: 'maps'
ProcStatus:
Name: VirtualBoxVM
Umask: 0002
State: D (disk sleep)
Tgid: 19676
Ngid: 0
Pid: 19676
PPid: 12813
TracerPid: 0
Uid: 1000 1000 1000 1000
Gid: 1000 1000 1000 1000
FDSize: 128
Groups: 4 20 24 27 30 46 116 126 132 133 139 1000
NStgid: 19676
NSpid: 19676
NSpgid: 19676
NSsid: 12812
VmPeak: 15273632 kB
VmSize: 15214848 kB
VmLck: 0 kB
VmPin: 0 kB
VmHWM: 8903008 kB
VmRSS: 8903008 kB
RssAnon: 235596 kB
RssFile: 8654516 kB
RssShmem: 12896 kB
VmData: 693452 kB
VmStk: 132 kB
VmExe: 148 kB
VmLib: 233692 kB
VmPTE: 19036 kB
VmSwap: 0 kB
HugetlbPages: 0 kB
CoreDumping: 1
THP_enabled: 1
Threads: 88
SigQ: 1/128063
SigPnd: 0000000000000000
ShdPnd: 0000000000000000
SigBlk: 0000000000002000
SigIgn: 0000000001001000
SigCgt: 1000000180012000
CapInh: 0000000000000000
CapPrm: 0000000000802000
CapEff: 0000000000802000
CapBnd: 0000003fffffffff
CapAmb: 0000000000000000
NoNewPrivs: 0
Seccomp: 0
Speculation_Store_Bypass: vulnerable
Cpus_allowed: ffff
Cpus_allowed_list: 0-15
Mems_allowed: 00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,0000000
0,00000000,00000000,00000001
Mems_allowed_list: 0
voluntary_ctxt_switches: 172786
nonvoluntary_ctxt_switches: 1930
Signal: 11
Uname: Linux 5.4.0-42-generic x86_64
UserGroups: adm cdrom dialout dip docker kvm lpadmin plugdev sambashare sudo vboxusers

Did anyone figure this bug out? Having same issue here. Ubuntu 18.04.5.