4.2.6 upgrade on OSX10.7.5 OWNER_NOT_ROOT

Discussions related to using VirtualBox on Mac OS X hosts.
Post Reply
zog
Posts: 3
Joined: 4. Jan 2013, 13:57

4.2.6 upgrade on OSX10.7.5 OWNER_NOT_ROOT

Post by zog »

I get this bizarre falling over on trying to run ANY pre-existing VM on my MacBook Pro since upgrading. I cannot use the software at all any more.

"Failed to open a session for the virtual machine Windows XP Professional.

Failed to load VMMR0.r0 (VERR_SUPLIB_OWNER_NOT_ROOT).

Result Code: NS_ERROR_FAILURE (0x80004005)
Component: Console
Interface: IConsole {db7ab4ca-2a3f-4183-9243-c1208da92392}"

It happens for my Fedora VM too.

My console log shows:-

04/01/2013 11:46:25.000 kernel: VirtualBoxVM (map: 0xffffff801274a9f8) triggered DYLD shared region unnest for map: 0xffffff801274a9f8, region 0x7fff8cc00000->0x7fff8ce00000. While not abnormal for debuggers, this increases system memory footprint until the target exits.

HELP HELP HELP

I am a simple user not a technogeek - I do not play with my machine settings etc. I have uninstalled VirtualBox 4.2.6, tried reinstalling - no joy. I tried installing 4.1.16, 4.1.10 still no joy

Any ideas from anyone please?
michaln
Oracle Corporation
Posts: 2973
Joined: 19. Dec 2007, 15:45
Primary OS: MS Windows 7
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Any and all
Contact:

Re: 4.2.6 upgrade on OSX10.7.5 OWNER_NOT_ROOT

Post by michaln »

Something messed up your directory/file permissions (something other than VirtualBox). It is unfortunately impossible to tell what it was, i.e. what not to do again. Some application installers have been known to do this. The VBox.log file may contain the full pathname of the affected file.

The system administrator (you?) needs to fix this, perhaps using the Disk Utility.
michaln
Oracle Corporation
Posts: 2973
Joined: 19. Dec 2007, 15:45
Primary OS: MS Windows 7
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Any and all
Contact:

Re: 4.2.6 upgrade on OSX10.7.5 OWNER_NOT_ROOT

Post by michaln »

Oh, and just to make it clear, uninstalling/reinstalling VirtualBox won't help if directory permissions got munged (the typical case). The system admin must fix it.
zog
Posts: 3
Joined: 4. Jan 2013, 13:57

Re: 4.2.6 upgrade on OSX10.7.5 OWNER_NOT_ROOT

Post by zog »

THNANKYOU THANKYOU - it looks like permissions on the Applications folder (see below)

HOW DO I RESET THESE? so owner is 'root'? I am not a UNIX chap??


The Vbox.log files says:_ VirtualBox VM 4.2.6 r82870 darwin.amd64 (Dec 19 2012 15:09:38) release log
00:00:00.354632 Log opened 2013-01-04T12:15:02.762594000Z
00:00:00.354649 OS Product: Darwin
00:00:00.354655 OS Release: 11.4.2
00:00:00.354670 OS Version: Darwin Kernel Version 11.4.2: Thu Aug 23 16:25:48 PDT 2012; root:xnu-1699.32.7~1/RELEASE_X86_64
00:00:00.355543 DMI Product Name: MacBookPro8,2
00:00:00.356119 DMI Product Version: 1.0
00:00:00.356127 Host RAM: 8192MB total, 4901MB available
00:00:00.356128 Executable: /Applications/VirtualBox.app/Contents/MacOS/../Resources/VirtualBoxVM.app/Contents/MacOS/VirtualBoxVM
00:00:00.356129 Process ID: 1314
00:00:00.356130 Package type: DARWIN_64BITS_GENERIC
00:00:00.358389 Installed Extension Packs:
00:00:00.358396 None installed!
00:00:00.359293 pdmR3LoadR0U: pszName="VMMR0.r0" rc=VERR_SUPLIB_OWNER_NOT_ROOT szErr="The owner is not root: '/Applications'"
00:00:00.359317 VMSetError: /Users/vbox/tinderbox/4.2-mac-rel/src/VBox/VMM/VMMR3/VM.cpp(602) int vmR3CreateU(UVM*, uint32_t, int (*)(VM*, void*), void*); rc=VERR_SUPLIB_OWNER_NOT_ROOT
00:00:00.359321 VMSetError: Failed to load VMMR0.r0
00:00:00.359384 ERROR [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={db7ab4ca-2a3f-4183-9243-c1208da92392} aComponent={Console} aText={Failed to load VMMR0.r0 (VERR_SUPLIB_OWNER_NOT_ROOT)}, preserve=false
00:00:00.394463 Power up failed (vrc=VERR_SUPLIB_OWNER_NOT_ROOT, rc=NS_ERROR_FAILURE (0X80004005))
zog
Posts: 3
Joined: 4. Jan 2013, 13:57

Re: 4.2.6 upgrade on OSX10.7.5 OWNER_NOT_ROOT

Post by zog »

Figured it out....

open TERMINAL

naviagte to root folder

cd \

then ls -l shows Applications

then

sudo chown root Applications

FIXED!!

now VM starts

thank you thank you thank you
Post Reply