Kernel crashes after boot on 5.2.8 with guest additions

[romano]

Hi,

I am using virtualbox, and my virtual machines are crashing on virtualbox 5.2.8 after installing Guest Additions. They are working on 5.1.x with and without Guest Additions.
I have seen many similar cases on the forum, but none with the same trace that I got, which I attach below. When they are displayed, the boot is interrupted. I can still still scroll though the traces using pg up/pg down.

Here are some indications on my investigations:
I have two machines, and while i saw the issue on both, it is much more frequent on one of the machine (Dual core i7 laptop).
It occurs at a time where the window is being resized, suggesting resolution changes.
It does not occurs after adding vboxvideo to `/etc/modprobe.d/blacklist.conf`. In this case, vboxvideo can be loaded afterwards and works.
It occurs less frequently when adding vboxvideo to `/etc/modules`.

Do you have any advice ?

Many thanks
Romano

VirtualBox_SDK vbox_12_04_2018_15_36_28.png (29.69 KiB) Viewed 3187 times

VirtualBox_SDK vbox_12_04_2018_15_36_49.png (26.96 KiB) Viewed 3187 times

[andyp73]

Do you have any advice ?

Do you have "3D Acceleration" enabled for the video in the guests? If so, can you try disabling it to see if that improves things?

If not, can you post the VBox.log file from the guest (zipped of course) having started the guest, seen the error / crash and having shutdown the guest - by force if necessary.

-Andy.

[romano]

3D Acceleration is not enabled

Here is the log file :

VBox.log.gz

(28.24 KiB) Downloaded 10 times

Best regards
R

[andyp73]

00:00:00.498980 Host RAM: 7677MB (7.4GB) total, 4309MB (4.2GB) available
00:00:00.563715 RamSize <integer> = 0x0000000100000000 (4 294 967 296, 4 096 MB, 4.0 GB)
00:00:00.564042 VRamSize <integer> = 0x0000000008000000 (134 217 728, 128 MB)

Whilst you haven't exceeded the available memory on your host you are getting very close to doing so. I would set the guest to use 2GB.

00:00:00.718992 CPUM: Physical host cores: 2
00:00:00.563711 NumCPUs <integer> = 0x0000000000000002 (2)

You appear to have two physical processor cores and have allocated both of them to the guest. I would try reducing this to 1.

-Andy.

[romano]

I have tried varying number of cores, amount of ram and video ram without success. I also tried different processor emulation options such as vt-x and friends. It also occurs on my other machine with has 4 cores, and a lot more ram and several coworker machines too.

Basically during the boot, the splashscreen (plymouth) uses DRM (direct rendering manager) to open display and close it after a few seconds, and then the X server starts a bit later.
I see the splashscreen so the DRM is properly opened, but then maybe then it is not closed at the right time or something happends during close.
In some cases there are some pieces of garbage on the screen after the splash is dismissed and before X start.

[romano]

Here is sample with a bit of garbage but I have seen much worse

VirtualBox_SDK vbox_12_04_2018_18_27_10.png (28.44 KiB) Viewed 3169 times

[romano]

The issue is still present in the testing version virtualbox 5.2.9 r121870

[socratis]

Can you disable the Sound in your VM and see if that makes a difference?
BTW, what's the guest OS? I see Ubuntu_64 selected, but I may have missed the complete details.

[romano]

Hi Socratis,
It's a custom OS based on ubuntu with xfce.
Disable sound does not help.
I'm trying to get some kernel debug traces, but to my surprise the serial port is extremely slow, a boot takes 5 minutes with the serial port enabled, but the issue still occured.
Best regards,
R

[socratis]

It's a custom OS based on ubuntu with xfce.

I hate to say it, but a custom OS would pretty much mean that you have to get your hands dirty, if you know what I mean, not VirtualBox

[romano]

Well I could simplify by saying it's an ubuntu with some extra packages.
I always have my hands dirty!