[Bug 236996] emulators/virtualbox-ose RTR3InitEx failed with rc=-8 (rc=-8) – supR3HardenedMainInitRuntime what: 4 VERR_NO_MEMORY (-8) - Memory allocation failed

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Wed Apr 3 23:50:51 UTC 2019


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236996

            Bug ID: 236996
           Summary: emulators/virtualbox-ose RTR3InitEx failed with rc=-8
                    (rc=-8) – supR3HardenedMainInitRuntime what: 4
                    VERR_NO_MEMORY (-8) - Memory allocation failed
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: vbox at FreeBSD.org
          Reporter: grahamperrin at gmail.com
             Flags: maintainer-feedback?(vbox at FreeBSD.org)
          Assignee: vbox at FreeBSD.org

I have three guest machines, two of which are saved (from when VirtualBox was
last usable), all of which no longer start. 

Two modal dialogues appear. 

One: 

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

The other (underlying the first modal): 

> Failed to open a session for the virtual machine Lubuntu.
> 
> The virtual machine 'Lubuntu' has terminated unexpectedly during startup with exit code 1 (0x1).
> 
> Result Code: NS_ERROR_FAILURE (0x80004005)
> Component: MachineWrap
> Interface: IMachine {85cd948e-a71f-4289-281e-0ca7ad48cd89}

----

grahamperrin at momh167-gjp4-8570p:~ % date ; uname -v
Thu  4 Apr 2019 00:49:59 BST
FreeBSD 13.0-CURRENT r345754 GENERIC-NODEBUG 
grahamperrin at momh167-gjp4-8570p:~ % pkg query '%o %v %R' virtualbox-ose
virtualbox-ose-kmod
emulators/virtualbox-ose 5.2.26_3 poudriere
emulators/virtualbox-ose-kmod 5.2.26 poudriere
grahamperrin at momh167-gjp4-8570p:~ %

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


More information about the freebsd-emulation mailing list