virtualbox.org

To wipe the drive clean and do a fresh install of virtualbox, what must I do?

Here's what I tried so far.

I ran the uninstall program and then removed the ~/VirtualBox VMs folder.
I ran the installer again from the dmg.

Three observations:

1) the initial four VM presets installed by the program, do not appear. I would like those back.
2) the VM that existed prior to this reinstall *does* appear. I want that gone.
3) when I launch the existing VM, I get FATAL No bootable medium found.

Ideas?

What does "initial 4 VM presets" refer to? There are no VMs bundled with VirtualBox.

Interesting! The very first time I installed virtualbox it nstalled 4 VMs. an XP, a Vista, and two Win 7's. I'm the only user, so I know it wasn't ever installed before. How did they get there? I have Parallels installed. Is it possible my VMs from Parallels are getting read by virtualbox?

More importantly, I just want to get virtualbox running on my Mac. When I follow the instructions in the manual, the vm I create throws that FATAl error I referred to in my last post. I'm really stuck. I know you said my case is over your head, but honestly, I'm just looking to do a common install. I have a MacBook Pro running Lion OS X. I'm willing to pay for profession support. What do you suggest?

carom wrote:Interesting! The very first time I installed virtualbox it nstalled 4 VMs. an XP, a Vista, and two Win 7's.

Nope, I'm afraid it didn't. For one thing it would be a breach of Microsoft licensing, since I assume you didn't pay for those installations.

Despite what you thought, you or someone else must have previously installed some version of VirtualBox on that PC. The VMs would have remained behind even if VBox itself was uninstalled. Once reinstalled, VirtualBox would pick up those VMs if they were available in a standard location, i.e. either current users doc folder, or as identified by a VBOX_USER_HOME environment variable. In fact you can check if the latter variable exists: if it does then it must have been created manually, because VirtualBox certainly doesn't set this by default.