I just started using Virtualbox and I've got a question maybe someone here can answer.
I followed this guide to share my Windows 7 Bootcamp partition with Virtualbox:
http://luckyviplav.blogspot.com/2011/06/windows-7-on-mac-os-x-through-virtual.html
It worked great at first. I had to permanently unmount the Bootcamp drive in OSX, then create the win7raw.vmdk files, give myself access to those files, using "sudo chown filmbuff win7raw.vmdk", and create the virtual machine with Virtualbox. It all worked great and I booted Win7 no problem.
The issue that I'm having is that every time I shut down my Mac and restart it, I have to go through the whole process again. When I try to boot Win7 in Virtualbox I get "VERR_ACCESS_DENIED". I've tried doing the "sudo chown" command again and making sure the .vmdk files were marked read and write, but no joy. If I go through the process from the start it will work fine, until I shut down again. Any help?
The only theory I have is that a while ago I downloaded a client (from Macrumors) that was supposed to "fix" the Mountain Lion slow shutdown. I believe this client set my computer to repair permissions at every shutdown, which could be the problem. How do I fix that? I should make it clear that I don't really know what I'm doing in the terminal
I followed this guide to share my Windows 7 Bootcamp partition with Virtualbox:
http://luckyviplav.blogspot.com/2011/06/windows-7-on-mac-os-x-through-virtual.html
It worked great at first. I had to permanently unmount the Bootcamp drive in OSX, then create the win7raw.vmdk files, give myself access to those files, using "sudo chown filmbuff win7raw.vmdk", and create the virtual machine with Virtualbox. It all worked great and I booted Win7 no problem.
The issue that I'm having is that every time I shut down my Mac and restart it, I have to go through the whole process again. When I try to boot Win7 in Virtualbox I get "VERR_ACCESS_DENIED". I've tried doing the "sudo chown" command again and making sure the .vmdk files were marked read and write, but no joy. If I go through the process from the start it will work fine, until I shut down again. Any help?
The only theory I have is that a while ago I downloaded a client (from Macrumors) that was supposed to "fix" the Mountain Lion slow shutdown. I believe this client set my computer to repair permissions at every shutdown, which could be the problem. How do I fix that? I should make it clear that I don't really know what I'm doing in the terminal