Date: Mon, 17 Apr 2017 08:21:10 +0000 From: bugzilla-noreply@freebsd.org To: vbox@FreeBSD.org Subject: maintainer-feedback requested: [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. Message-ID: <bug-218698-26505-AtNHsmKOu5@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-218698-26505@https.bugs.freebsd.org/bugzilla/> References: <bug-218698-26505@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
Graham Perrin <grahamperrin@gmail.com> has reassigned Bugzilla Automation <bugzilla@FreeBSD.org>'s request for maintainer-feedback to vbox@FreeBSD.org: 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. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218698 --- Description --- >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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-218698-26505-AtNHsmKOu5>