Yosemite Bootcamp VM - VERR_ACCESS_DENIED

Discussions related to using VirtualBox on Mac OS X hosts.
Post Reply
square_eyes
Posts: 7
Joined: 17. Feb 2015, 13:07

Yosemite Bootcamp VM - VERR_ACCESS_DENIED

Post by square_eyes »

Hi, I can't seem to find too much about this issue online, I hope it's not unique to me so I can get some help.

I have tried several tutorials (will post soon due to restrictions) on how to set up my Bootcamp partition to be accessible via Virtualbox. I've done it before, from Mountain Lion, to have a Win 8 VM usable from my Bootcamp partition.

Now I have clean installed 10.10.2, I can't get it working. I dismount Bootcamp, create the vmdi in terminal, and set permissions. Oddly, I'm not asked to authenticate when setting the permission of the file to 777 (which this tutorial doesn't mention but others do).

When I try to add the disk when setting up the VM (even if I add it later as IDE ICH6) I get the following error...

Code: Select all

Failed to open the hard disk file /Users/square/BC8.vmdk.

Permission problem accessing the file for the medium '/Users/square/BC8.vmdk' (VERR_ACCESS_DENIED).

Result Code: VBOX_E_FILE_ERROR (0x80BB0004)
Component: Medium
Interface: IMedium {05f2bbb6-a3a6-4fb9-9b49-6d0dda7142ac}
Callee: IVirtualBox {fafa4e17-1ee2-4905-a10e-fe7c18bf5554}
Callee RC: VBOX_E_OBJECT_NOT_FOUND (0x80BB0001)
I have fixed various permissions, but am not sure as to which partition/disk I should be doing that. So I did all that I could from Disk Management. I even created a new user and tried it in that account but got the same error.

What else can I try?
JimBushWhack
Posts: 77
Joined: 1. Sep 2008, 23:07
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win XP on iMac; Win 7 on MacBook pro + bootcamp
Location: SF Bay Area; California, USA

Re: Yosemite Bootcamp VM - VERR_ACCESS_DENIED

Post by JimBushWhack »

The Bootcamp partition should be partition 4. You can check with this command via terminal:

sudo vboxmanage internalcommands listpartitions -rawdisk /dev/disk0

or open Disk Utility select your hard disk on the left pane and then select partition. This will show you what the partitions are.
square_eyes
Posts: 7
Joined: 17. Feb 2015, 13:07

Re: Yosemite Bootcamp VM - VERR_ACCESS_DENIED

Post by square_eyes »

Thanks for the reply, although I'm not sure how it applies to my error. I know Bootcamp partition is partition 4, that's what I set it as using the command...

"sudo vboxmanage internalcommands createrawvmdk -rawdisk /dev/disk0 -filename BC8.vmdk -partitions 4"

Here is the partition info...

Number Type StartCHS EndCHS Size (MiB) Start (Sect)
1 0x00 0 /0 /0 0 /0 /0 200 40
2 0x00 0 /0 /0 0 /0 /0 370979 409640
3 0x00 0 /0 /0 0 /0 /0 128 760176640
4 0x00 0 /0 /0 0 /0 /0 105343 760438784
5 0x00 0 /0 /0 0 /0 /0 451 976181248
square_eyes
Posts: 7
Joined: 17. Feb 2015, 13:07

Re: Yosemite Bootcamp VM - VERR_ACCESS_DENIED

Post by square_eyes »

Code: Select all

ls -l
Shows the owner of the two vmdk files as root, and not my username (-rwxrwxrwx). Could this be it? How could this have happened?
square_eyes
Posts: 7
Joined: 17. Feb 2015, 13:07

Re: Yosemite Bootcamp VM - VERR_ACCESS_DENIED

Post by square_eyes »

Also, I've just noticed my Bootcamp partition is over 100gb. I can't understand why because I set it to be 60GB when I used the Bootcamp assistant. It boots natively fine, so I don't know if this has anything to do with it.
square_eyes
Posts: 7
Joined: 17. Feb 2015, 13:07

Re: Yosemite Bootcamp VM - VERR_ACCESS_DENIED

Post by square_eyes »

Any ideas?
square_eyes
Posts: 7
Joined: 17. Feb 2015, 13:07

Re: Yosemite Bootcamp VM - VERR_ACCESS_DENIED

Post by square_eyes »

Nothing?
Vischo
Posts: 1
Joined: 2. May 2015, 15:28

Re: Yosemite Bootcamp VM - VERR_ACCESS_DENIED

Post by Vischo »

Hello Square,
First, check these things:
1. You have unmounted your bootcamp partition - right click on disk bootcamp...
2. You have modified the volume partition permissions with leading 'sudo', like this:
sudo chow 777 /dev/disk0s4
3. You have performed the chmod 777 command with leading 'sudo', like this:
sudo chmod square *.vmdk

It seems that it's only a permissions/ownership issue.
Post Reply