virtualbox.org

After restoring my hard drive from a Time Machine back-up (following a complete reinstall of Mavericks OSX 10.9.2) my Windows 7 would not load in Virtual Box. The error message was "Failed to load VMMR0.r0 (VERR_SUPLIB_OWNER_NOT_ROOT)". I uninstalled both VB and Windows. Reinstalled VB ver 4.3.10 r93012 and created a New VM for Windows 7. When I clicked to start it, the same message came up. Any help would be appreciated.

try running disk utility>repair permissions on your Mac. it is possible your permissions had an issue. which would have been saved to your backup. and of course copied back over when you restored.

Running Disk Permissions did fix the issue with the VM not starting. I had just done a Disk Permissions the previous day, but I guess something changed. Now that the VM is running, it's not finding the "boot" drive so that I can reload Windows. Any suggestions on the steps to take to get Windows reloaded on the VM?
Thanks.

Daterp wrote:Running Disk Permissions did fix the issue with the VM not starting. I had just done a Disk Permissions the previous day, but I guess something changed. Now that the VM is running, it's not finding the "boot" drive so that I can reload Windows. Any suggestions on the steps to take to get Windows reloaded on the VM?
Thanks.

I forget where the default machines folder is because I moved mine but just look for the VMs folder and inside that should be your Windows guest folder with it's .vdi. If you have to, remove the the guest from the VirtualBox list and use Add Machine to the menu and select the Windows .vbox file.

Additional information.
When I start the new VM, rather than get the "First Start Wizard", a message comes up that no bootable drive was found. Is there a way to get the "First Start Wizard" to display?

As the name implies, the first start wizard only appears at first start, and then only if you made no changes to the VM settings from the default template.

But, this shouldn't matter. Just attach your setup ISO to the VM and start the VM: that's all that the "first start wizard" does. I assume you understand that the wizard only applies when installing a new OS in a new VM. It has no purpose in an existing VM that was previously working.

I think I've finally got this to work after deleting the existing VM and starting again. Seems to be loading the OS now.
Thanks for your help.