Segfault from systemd in libc-2.28.9000.so -> systemd issue

[George R. Goffe]

Host is a Fedora Core 30 x86_64 system.

After an upgrade of VB software (VirtualBox-6.0.0_BETA1-126216-Linux_amd64.run/ an execution of /sbin/vboxconfig requested. Running this command resulted in the following messages and an apparent hang of the command.

Broadcast message from systemd-journald@fc30 (Sat 2018-11-10 20:42:45 PST):

systemd[1]: Caught <SEGV>, dumped core as pid 291430.

Broadcast message from systemd-journald@fc30 (Sat 2018-11-10 20:42:47 PST):

systemd[1]: Freezing execution.

2018 Nov 10 20:42:44 fc30 systemd[1]: segfault at ffffffffffffffc0 ip 00007f405743bd34 sp 00007ffe0391eb98 error 5 in libc-2.28.9000.so[7f40573c3000+14d000] 2018 Nov 10 20:42:44 fc30 Code: c1 e1 20 48 09 ca 48 89 f9 48 31 c1 48 83 e0 c0 48 d3 fa 48 85 d2 74 7e 48 0f bc c2 c3 66 0f 1f 84 00 00 00 00 00 48 83 e0 c0 <66> 0f 74 00 66 0f 74 48 10 66 0f 74 50 20 66 0f 74 58 30 66 0f d7 2018 Nov 10 20:42:45 fc30 Caught <SEGV>, dumped core as pid 291430. 2018 Nov 10 20:42:47 fc30 Freezing execution.

Failed to enable unit: Failed to activate service 'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms) Failed to enable unit: Failed to activate service 'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms)

[George R. Goffe]

Installation of VirtualBox-6.0-6.0.0_BETA1_125994_fedora26-1.x86_64.rpm failed in /sbin/vboxconfig. At which time I tried the developer version of VB listed above.

[Michael Thayer]

Sorry if it sounds like a dodge, but are you saying that systemd is faulting? If so, have you got in touch with any systemd people? I would like some clearer reason to think that this is a problem in VirtualBox and not just accidentally triggering a problem in systemd before I even consider it.

[George R. Goffe]

Michael,

In an attempt to install a newer version of VB I downloaded VirtualBox-6.0.0_BETA1-126579-Linux_amd64.run but could not run vboxconfig successfully. I have attached the log from that execution. Are you the guy to send this file to?

No, it doesn't sound like a dodge but I haven't been able to try to re-create the problem yet. It could be a fluke though.

Thanks for your response,

George...

[George R. Goffe]

Michael,

Systemd bug report at RedHat: ​https://bugzilla.redhat.com/show_bug.cgi?id=1649889

I also have a corefile if you want to see it. It might be early for you to even look at this.

Thanks,

George...

[Michael Thayer]

Regarding the modules build error: we have not yet added support for kernel 4.20, so it is expected. And no, I'm sorry but I don't want to see the core file.

[George R. Goffe]

Michael,

Ok.

Thanks for your help and your time.

Regards,

George...

[Michael Thayer]

Closing this. Please add a comment (or better, ask the systemd developers to do so) if after investigation on the systemd side it does look like VirtualBox is doing something wrong.