Virtualbox 5.1.38 crashing on 18.3 sylvia x64

Questions about virtualization software
Forum rules
Before you post please read how to get help
Post Reply
dhdurgee
Level 4
Level 4
Posts: 297
Joined: Thu Jul 02, 2009 7:56 pm

Virtualbox 5.1.38 crashing on 18.3 sylvia x64

Post by dhdurgee » Mon Jul 02, 2018 3:11 pm

I am seeing crashes logged with virtualbox 5.1.38 on the system I am moving to 18.3 sylvia x64 when shutting down a w7pro virtualbox. Apport.log shows:

ERROR: apport (pid 5660) Mon Jul 2 13:55:46 2018: called for pid 4231, signal 11, core limit 0, dump mode 2
ERROR: apport (pid 5660) Mon Jul 2 13:55:46 2018: not creating core for pid with dump mode of 2
ERROR: apport (pid 5660) Mon Jul 2 13:55:46 2018: executable: /usr/lib/virtualbox/VirtualBox (command line "/usr/lib/virtualbox/VirtualBox --comment Windows\ 7\ Test --startvm f168e14b-8410-4ebf-ae98-a3a87be931c2 --no-startvm-errormsgbox")
ERROR: apport (pid 5660) Mon Jul 2 13:55:46 2018: debug: session gdbus call: (true,)

ERROR: apport (pid 5660) Mon Jul 2 13:55:46 2018: apport: report /var/crash/_usr_lib_virtualbox_VirtualBox.0.crash already exists and unseen, doing nothing to avoid disk usage DoS

I have another sylvia system running the same virtualbox and the same w7pro without seeing such problems. The problem appears to happen after w7 has finished its shutdown, so it is annoying as opposed to a big problem.

Can someone help me figure out how to correct this?

Dave

User avatar
catweazel
Level 17
Level 17
Posts: 7121
Joined: Fri Oct 12, 2012 9:44 pm
Location: Australian Antarctic Territory

Re: Virtualbox 5.1.38 crashing on 18.3 sylvia x64

Post by catweazel » Mon Jul 02, 2018 7:45 pm

dhdurgee wrote:
Mon Jul 02, 2018 3:11 pm
Can someone help me figure out how to correct this?
You might try a more recent version of VBox.
¡uʍop ǝpısdn sı buıɥʇʎɹǝʌǝ os ɐıןɐɹʇsnɐ ɯoɹɟ ɯ,ı

dhdurgee
Level 4
Level 4
Posts: 297
Joined: Thu Jul 02, 2009 7:56 pm

Re: Virtualbox 5.1.38 crashing on 18.3 sylvia x64

Post by dhdurgee » Tue Jul 03, 2018 7:06 am

catweazel wrote:
Mon Jul 02, 2018 7:45 pm
dhdurgee wrote:
Mon Jul 02, 2018 3:11 pm
Can someone help me figure out how to correct this?
You might try a more recent version of VBox.
I was afraid you might say that. I just got through yesterday dealing with a kernel update that broke things badly. I trust they will continue updates to the 4.13.x line of kernels, as the 4.15.x kernel was totally unusable on one of my systems.

The vbox I am running is the latest in the 5.1 line, so the only more recent is to switch to the 5.2 line. I will try on another system first and then consider this one after seeing how it goes.

Dave

Post Reply

Return to “Virtualization”