Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 03 Aug 2022 09:50:15 +0000
From:      bugzilla-noreply@freebsd.org
To:        ports-bugs@FreeBSD.org
Subject:   [Bug 265593] Virtualbox wil not start after upgrade to 6.1.36
Message-ID:  <bug-265593-7788@https.bugs.freebsd.org/bugzilla/>

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

            Bug ID: 265593
           Summary: Virtualbox wil not start after upgrade to 6.1.36
           Product: Ports & Packages
           Version: Latest
          Hardware: amd64
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: ports-bugs@FreeBSD.org
          Reporter: rol@robert-eckardt.de

After upgrading virtualbox from 6.1.32 to 6.1.36 VBoxSVC won't run as it
allocates memory until it runs out of swapspace.

A Windows 10 instance (6GB RAM) run as a guest on a FreeBSD 12.3-p5 host (3=
2GB
RAM, 4GB swap) with virtualbox-ose-6.1.32 (vfs.zfs.arc_max is set to 12GB).
Now, after upgrade to 6.1.36 VBoxSVC starts, allocates memory up to over 30=
 GB
until swapspace is exhausted.

I'm not conviced that it is releated to Virtualbox itself but rather to a
library or kernel functionality.
It seems to be a recurring error as it keeps popping up at least since 2013.

Besides, the dependencies of the port are incomplete as e.g. qt5-dbus-5.15.2
got upgraded to 5.15.5 but not qt5-core-5.15.2.

--=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-265593-7788>