Opened 12 years ago
Closed 12 years ago
#11643 closed defect (invalid)
VM crashes on startup under OS X host
| Reported by: | TimSparrow | Owned by: | |
|---|---|---|---|
| Component: | other | Version: | VirtualBox 4.2.10 |
| Keywords: | crash | Cc: | |
| Guest type: | Windows | Host type: | Mac OS X |
Description
Created a win8 vm under Maс OS X host. Any time I try to start the VM, it crashes with the following error message:
VirtualBox VM 4.2.10 r84104 darwin.x86 (Mar 5 2013 12:16:54) release log 00:00:10.899069 Log opened 2013-03-25T14:48:20.496484000Z 00:00:10.899169 OS Product: Darwin 00:00:10.899218 OS Release: 10.8.0 00:00:10.899278 OS Version: Darwin Kernel Version 10.8.0: Tue Jun 7 16:33:36 PDT 2011; root:xnu-1504.15.3~1/RELEASE_I386 00:00:10.902508 DMI Product Name: MacBook1,1 00:00:10.905669 DMI Product Version: 1.0 00:00:10.905758 Host RAM: 2048MB total, 631MB available 00:00:10.905770 Executable: /Applications/VirtualBox.app/Contents/MacOS/../Resources/VirtualBoxVM.app/Contents/MacOS/VirtualBoxVM 00:00:10.905773 Process ID: 88493 00:00:10.905775 Package type: DARWIN_32BITS_GENERIC 00:00:10.928394 Installed Extension Packs: 00:00:10.928447 None installed! 00:00:11.125832 pdmR3LoadR0U: pszName="VMMR0.r0" rc=VERR_SUPLIB_OWNER_NOT_ROOT szErr="The owner is not root: '/Applications'" 00:00:11.125949 VMSetError: /Users/vbox/tinderbox/4.2-mac-rel/src/VBox/VMM/VMMR3/VM.cpp(602) int vmR3CreateU(UVM*, uint32_t, int (*)(VM*, vo id*), void*); rc=VERR_SUPLIB_OWNER_NOT_ROOT 00:00:11.125965 VMSetError: Failed to load VMMR0.r0 00:00:11.126387 ERROR [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={db7ab4ca-2a3f-4183-9243-c1208da92392} aComponent={Console} aText={Faile d to load VMMR0.r0 (VERR_SUPLIB_OWNER_NOT_ROOT)}, preserve=false 00:00:11.240686 Power up failed (vrc=VERR_SUPLIB_OWNER_NOT_ROOT, rc=NS_ERROR_FAILURE (0X80004005)) ==================================== The bug reproduces always. Also was observed in VB 4.2.8
Please read the error message you posted. It says that "/Applications" is not owned by root. VirtualBox will not start on such a system for security reasons. Please just chown all components of the path to root and VirtualBox will start again. This is not a VirtualBox bug but a problem with your environment.