Bug 218698 - emulators/virtualbox-ose since ~2017-03 guest machines no longer start, RTR3InitEx failed with rc=-8 (rc=-8) where: supR3HardenedMainInitRuntime what: 4 VERR_NO_MEMORY (-8) - Memory allocation failed.
Summary: emulators/virtualbox-ose since ~2017-03 guest machines no longer start, RTR3I...
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Some People
Assignee: Virtualbox Team (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-04-17 08:21 UTC by Graham Perrin
Modified: 2017-06-11 01:28 UTC (History)
0 users

See Also:
bugzilla: maintainer-feedback? (vbox)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Graham Perrin freebsd_committer freebsd_triage 2017-04-17 08:21:10 UTC
From <https://discourse.trueos.org/t/-/1249?u=grahamperrin> (2017-04-17): 

> VirtualBox not working properly 3-30-17 snapshot - Help and Support / External Packages - TrueOS Community

> Since the 3-30-17 update VirtualBox isn't launching my VMs. …

> RTR3InitEx failed with rc=-8 (rc=-8)
> 
> Please try reinstalling VirtualBox.
> 
> where: supR3HardenedMainInitRuntime what: 4 VERR_NO_MEMORY (-8) - Memory allocation failed.

I'm almost certain that: 

- there was an earlier report from another user of TrueOS
- the symptoms are as I observed on 2017-04-01 whilst using Gitter. 

Ignoring the 2017-03-29 time stamp at <https://gitter.im/BSDs/FreeBSD?at=58dc1abc7ea420cc421b2d9b> (the stamp is a bug in Gitter): 

> @grahamperrin tries, fails to start a VirtualBox guest

> @grahamperrin prepares to boot an inferior environment

> Third time lucky, 

$ about

===================
General information
===================

boot environment now (N) … 12.0-CURRENT-up-20170331_041352 N 2017-03-31
       after restart (R) … 12.0-CURRENT-up-20170330_080908 R 2017-03-30
boot loader …………………………………… BSD
            type ……………………… EFI
CPU ………………………………………………………… Intel(R) Core(TM) i7-5600U CPU @ 2.60GHz
    number of cores ……………… 4
host ……………………………………………………… momh167-gjp4-hpelitebook850g2-trueos.university.brighton.ac.uk
memory ………………………………………………… 16384 MB available, 12746 MB free
OS git branch ……………………………………………………………………………………… drm-next
OS git revision ………………………………………………………………………………… d44fdf245
OS kernel build time ………………………………………………………… Thu 2017 Mar 30 18:18:02 UTC
OS kernel identity …………………………………………… (uname -i) GENERIC
OS platform (architecture) ……………………… (uname -m) amd64
OS release level ………………………………………………… (uname -r) 12.0-CURRENT
OS version and patch level …… (freebsd-version) 12.0-CURRENT
TrueOS package set ………………… CUSTOM
TrueOS version …………………………… TrueOS-Desktop-201703201429
uptime ………………………………………………… 13 mins
user  …………………………………………………… grahamperrin

More (TrueOS Desktop):

    desktop environment …… KDE
    sound card driver ………… pcm1: <Realtek (0x0280) (Analog 2.0+HP/2.0)> on hdaa1  (1p:1v/1r:1v) default
    wireless driver ……………… iwm0
    X11 drivers ………………………… intel_drv.so 

$

> The boot environment from 2017-03-30 is good for VirtualBox.
Comment 1 Graham Perrin freebsd_committer freebsd_triage 2017-04-18 06:50:54 UTC
I aimed to make the issue reproducible with a fresh installation of FreeBSD-CURRENT. Unfortunately the hardware that I set aside for that task – the hardware that previously ran TrueOS Desktop – is bugged by what is probably an 'extension' of 211702; the installed FreeBSD host is illegible (not suitable for an installation of VirtualBox). 

I aim to perform a fresh installation of FreeBSD-CURRENT to different host hardware.
Comment 2 Graham Perrin freebsd_committer freebsd_triage 2017-04-21 05:46:31 UTC
Not reproducible with a boot environment named 

12.0-CURRENT-up-20170421_000145

– that's probably from https://builds.ixsystems.com/jenkins/job/TrueOS%20-%20Build%20All%20Packages/240/

> Started 19 hr ago
> Took 5 hr 34 min on Gauntlet
> Success Build #240 (Apr 20, 2017 10:21:38 AM) 

– and is probably UNSTABLE, with regard to https://builds.ixsystems.com/jenkins/view/Push/job/TrueOS%20-%20Push%20Packages%20(UNSTABLE)/38/

> Started 13 hr ago
> Took 6 hr 57 min on JenkinsJail
> Success Build #38 (Apr 20, 2017 4:30:08 PM) 

Unfortunately the first of the environments (12.0-CURRENT-up-20170331_041352) that were bugged, by 218698, has disappeared without explanation so my instinct is to refrain from closing this issue until after testing with at least one other machine. 

I still aim for: 

> … a fresh installation of FreeBSD-CURRENT. …

----

$ beadm list
BE                              Active Mountpoint  Space Created
failsafe                        -      -           17.6G 2017-03-08 02:52
12.0-CURRENT-up-20170330_080908 R      -           45.8G 2017-03-30 08:07
12.0-CURRENT-up-20170421_000145 -      -          260.2M 2017-04-20 23:09
12.0-CURRENT-up-20170421_061720 N      /           12.6G 2017-04-21 06:16
$ about

===================
General information
===================

boot environment now (N) … 12.0-CURRENT-up-20170421_061720 N 2017-04-21
       after restart (R) … 12.0-CURRENT-up-20170330_080908 R 2017-03-30
boot loader …………………………………… BSD
            type ……………………… EFI
CPU ………………………………………………………… Intel(R) Core(TM) i7-5600U CPU @ 2.60GHz
    number of cores ……………… 4
host ……………………………………………………… momh167-gjp4-hpelitebook850g2-trueos.university.brighton.ac.uk
memory ………………………………………………… 16384 MB available, 12661 MB free
OS git branch ……………………………………………………………………………………… drm-next
OS git revision ………………………………………………………………………………… 96a971c9a
OS kernel build time ………………………………………………………… Mon 2017 Apr 17 18:50:02 UTC
OS kernel identity …………………………………………… (uname -i) GENERIC
OS platform (architecture) ……………………… (uname -m) amd64
OS release level ………………………………………………… (uname -r) 12.0-CURRENT
OS version and patch level …… (freebsd-version) 12.0-CURRENT
TrueOS package set ………………… CUSTOM
TrueOS version …………………………… TrueOS-Desktop-201704202330
uptime ………………………………………………… 6 mins
user  …………………………………………………… grahamperrin

More (TrueOS Desktop):

    desktop environment …… KDE
    sound card driver ………… pcm1: <Realtek (0x0280) (Analog 2.0+HP/2.0)> on hdaa1  (1p:1v/1r:1v) default
    wireless driver ……………… iwm0
    X11 drivers ………………………… intel_drv.so 

$ 

(Luckily my preferred environment – 12.0-CURRENT-up-20170421_061720 – has not disappeared.)
Comment 3 Graham Perrin freebsd_committer freebsd_triage 2017-04-21 05:50:15 UTC
Re: comment #2

> … preferred environment – 12.0-CURRENT-up-20170421_061720 …

Sorry, that was a copy-and-paste error. My preferred environment is as shown in outputs from 'about' and 'beadm list': 

12.0-CURRENT-up-20170330_080908
Comment 4 Graham Perrin freebsd_committer freebsd_triage 2017-04-21 14:33:48 UTC
<https://gitter.im/trueos/troubleshooting?at=58f9e371d32c6f2f0928894c> (today): 

> yay, virtualbox is working after the upgrade!
Comment 5 Graham Perrin freebsd_committer freebsd_triage 2017-06-11 01:28:05 UTC
Fixed, I guess; no recent problems with VirtualBox.