Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 23 Sep 2019 15:59:06 -0000
From:      bugzilla-noreply@freebsd.org
To:        vbox@FreeBSD.org
Subject:   [Bug 240775] emulators/virtualbox-ose random crashes
Message-ID:  <bug-240775-26505@https.bugs.freebsd.org/bugzilla/>

next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D240775

            Bug ID: 240775
           Summary: emulators/virtualbox-ose random crashes
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: vbox@FreeBSD.org
          Reporter: 000.fbsd@quip.cz
          Assignee: vbox@FreeBSD.org
             Flags: maintainer-feedback?(vbox@FreeBSD.org)

We are using VirtualBox for a long time as headless on few machines. Some t=
imes
ago it started crashing guest running 1 - 2 weeks. No longer uptime possibl=
e.
Hosts and guest are running FreeBSD 11.3 amd64. (crashes were seen on 11.2 =
too
before upgrade), one guest running ubuntu-mini (crashes too)

Guest are running different services. One is busy serving Zabbix 4.0 server
(crashing more often), one is almost idle doing just IPSec gateway for other
machines in LAN.

Today 3 of 4 guests crashed almost at the same time:
on host 1 (only 1 guest running):
Sep 23 09:52:01 XXX kernel: pid 783 (VBoxHeadless), jid 0, uid 920: exited =
on
signal 11

on host 2 (3 guest running):
Sep 23 09:50:33 YYY kernel: pid 19569 (VBoxHeadless), jid 0, uid 920: exite=
d on
signal 11
Sep 23 09:50:40 YYY kernel: pid 19551 (VBoxHeadless), jid 0, uid 920: exite=
d on
signal 11

All guests has 1 CPU configured.

Am I the only one with this kind of problem?

What is the right way to debug this issue?

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-240775-26505>