Fail to run
Fail to run
Failed to open a session for the virtual machine BackTrack5.
Failed to load VMMR0.r0 (VERR_SUPLIB_WORLD_WRITABLE).
Result Code: NS_ERROR_FAILURE (0x80004005)
Component: Console
Interface: IConsole {1968b7d3-e3bf-4ceb-99e0-cb7c913317bb}
I am having a problem with this I think I may have disabled a startup item that is causing this. Started after the last Xcode update yesterday. Have tried to deleting file and reinstall. Also have tried this in terminal:
sudo /Library/StartupItems/VirtualBox/VirtualBox restart
I spent 7 hours last night working on this so please don't tell me to search more because searching for "vertualbox on osx" or anything like it just leads to how to install osx in vertualbox.
running osx 10.8 and VB version 4.1.18 r78361 mac book air 2011
Like I said I did remove some startup items that may be causing this so if some one could maybe tell me what there startup items are that have to do with VBox I need the names so I can search for it and add it back into my startup items. If this isn't my problem any other help would be great.
Failed to load VMMR0.r0 (VERR_SUPLIB_WORLD_WRITABLE).
Result Code: NS_ERROR_FAILURE (0x80004005)
Component: Console
Interface: IConsole {1968b7d3-e3bf-4ceb-99e0-cb7c913317bb}
I am having a problem with this I think I may have disabled a startup item that is causing this. Started after the last Xcode update yesterday. Have tried to deleting file and reinstall. Also have tried this in terminal:
sudo /Library/StartupItems/VirtualBox/VirtualBox restart
I spent 7 hours last night working on this so please don't tell me to search more because searching for "vertualbox on osx" or anything like it just leads to how to install osx in vertualbox.
running osx 10.8 and VB version 4.1.18 r78361 mac book air 2011
Like I said I did remove some startup items that may be causing this so if some one could maybe tell me what there startup items are that have to do with VBox I need the names so I can search for it and add it back into my startup items. If this isn't my problem any other help would be great.
-
Perryg
- Site Moderator
- Posts: 34369
- Joined: 6. Sep 2008, 22:55
- Primary OS: Linux other
- VBox Version: OSE self-compiled
- Guest OSses: *NIX
Re: Fail to run
The error is telling you that you have permission issues (VERR_SUPLIB_WORLD_WRITABLE), that have been discussed here a lot, funny you missed it.
Anyway run the Repair Disk Permissions using DIsk Utility on your MAC host then it should work.
Anyway run the Repair Disk Permissions using DIsk Utility on your MAC host then it should work.
Re: Fail to run
Thank you, Thank you, Thank you, Thank you. IDK why I couldn't find it I kept ending up with how to install osx in VB but this worked and thank you again. 
-
jhelling
- Posts: 9
- Joined: 7. Aug 2012, 11:29
- Primary OS: Mac OS X other
- VBox Version: OSE other
- Guest OSses: 4.3
Re: Fail to run
Had the same kind a problem with my Mac OS X Server after upgrade to OS X Mountain Lion.
Found this post now after a week ... a week of looking around where Virtualbox for some reason worked for exactly one day.
Did not find this solution either ...
THANKS
a lot ... saves me a lot of effort!!!
Greetings,
Jan.
Found this post now after a week ... a week of looking around where Virtualbox for some reason worked for exactly one day.
Did not find this solution either ...
Greetings,
Jan.
Re: Fail to run
How would you go about repairing disk permissions if the guest OS you are trying to load is on an external hard drive? I assume that that the NS error failure 0x80004005 means something else in this case?
Thanks,
Nick
Thanks,
Nick
-
Perryg
- Site Moderator
- Posts: 34369
- Joined: 6. Sep 2008, 22:55
- Primary OS: Linux other
- VBox Version: OSE self-compiled
- Guest OSses: *NIX
Re: Fail to run
error failure 0x80004005 in and of itself is a generic error and without the rest of the error message or some other information it is impossible to tell what. The OP stated the world writable which pointed to the actual issue. What else can you offer?nickcapo wrote:How would you go about repairing disk permissions if the guest OS you are trying to load is on an external hard drive? I assume that that the NS error failure 0x80004005 means something else in this case?
Thanks,
Nick
Re: Fail to run
The only other part of the error message said "Callee RC" in front of the NS error failure. Does that help at all? I appreciate the help. This is driving me nuts. Clearly not a pro on virtualization.
-
Perryg
- Site Moderator
- Posts: 34369
- Joined: 6. Sep 2008, 22:55
- Primary OS: Linux other
- VBox Version: OSE self-compiled
- Guest OSses: *NIX
Re: Fail to run
Not really. Has this guest ever worked? Tell me how or what you did to install the guest?
Re: Fail to run
No, it hasn't. I just tried it again, using the following steps:
1) I clicked "New" on the VB Manager and went through the steps
2) Under "Virtual Hard Disk", I said "create new hard disk" and chose to save it as a VMDK because that is what I had saved XP as on my external hard drive
3) I went through the rest of the steps and hit create. Everything worked fine on that end.
4) I then went through the First Run Wizard and on "Select Installation Media" I tried to click on the folder to select the VDMK file on my external. I then got the following error:
Failed to open the CD/DVD image /Volumes/New Volume/vdisk0.vmdk.
The medium '/Volumes/New Volume/vdisk0.vmdk' can't be used as the requested device type.
Result Code: NS_ERROR_FAILURE (0x80004005)
Component: Medium
Interface: IMedium {53f9cc0c-e0fd-40a5-a404-a7a5272082cd}
Callee: IVirtualBox {c28be65f-1a8f-43b4-81f1-eb60cb516e66}
I have also attempted to "use an existing hard disk" but got the NS Error Failure(0x80004005) with nothing else written by it. I assume that I just did it wrong by choosing to "use an existing hard disk" on that attempt.
Thoughts?
1) I clicked "New" on the VB Manager and went through the steps
2) Under "Virtual Hard Disk", I said "create new hard disk" and chose to save it as a VMDK because that is what I had saved XP as on my external hard drive
3) I went through the rest of the steps and hit create. Everything worked fine on that end.
4) I then went through the First Run Wizard and on "Select Installation Media" I tried to click on the folder to select the VDMK file on my external. I then got the following error:
Failed to open the CD/DVD image /Volumes/New Volume/vdisk0.vmdk.
The medium '/Volumes/New Volume/vdisk0.vmdk' can't be used as the requested device type.
Result Code: NS_ERROR_FAILURE (0x80004005)
Component: Medium
Interface: IMedium {53f9cc0c-e0fd-40a5-a404-a7a5272082cd}
Callee: IVirtualBox {c28be65f-1a8f-43b4-81f1-eb60cb516e66}
I have also attempted to "use an existing hard disk" but got the NS Error Failure(0x80004005) with nothing else written by it. I assume that I just did it wrong by choosing to "use an existing hard disk" on that attempt.
Thoughts?
-
Perryg
- Site Moderator
- Posts: 34369
- Joined: 6. Sep 2008, 22:55
- Primary OS: Linux other
- VBox Version: OSE self-compiled
- Guest OSses: *NIX
Re: Fail to run
If using an existing HDD you must not use create new, but instead you select to use existing one.2) Under "Virtual Hard Disk", I said "create new hard disk" and chose to save it as a VMDK because that is what I had saved XP as on my external hard drive
Since you said that also failed I need to know how the original guest was created and you might as well post the names and extensions of the other files in the folder that has the original guest
Re: Fail to run
I used Paragon's Go Virtual Software to create the VMDK file. I clicked on the "P2V copy" option and it created the vdisk0.vmdk file, which is what I tried to use for my existing hard disk on VB Manager. The only other file on that external hard drive is E.ovf, which I believe was also created from the Go Virtual OS copy process.
-
Perryg
- Site Moderator
- Posts: 34369
- Joined: 6. Sep 2008, 22:55
- Primary OS: Linux other
- VBox Version: OSE self-compiled
- Guest OSses: *NIX
Re: Fail to run
I have never tried to use that software. Never really needed to but I suspect the *.ovf is the import file name. Try importing instead of creating and see if it gets you further.