virtualbox.org

VirtualBox 4.1.4 can't find its files where a previous version could.

Has some feature changed or a new bug been introduced where VB cannot use a non-booting volume?

I have the VM files on a non-booting volume where the "Ignore permissions on this volume" is enabled. Even when I use the "choose file" navigation window and show it directly where it is, it still gives me the same error. I've deleted the ~/Library/VirtualBox/ and removed the VM from the app gui and re-added it, but it's still a no-go.

I'd hate to go back to VMWare's crappy Fusion. But there's just this one Windoze app I need for like a minute or two.

Any thoughts or words of wisdom is appreciated.

-Daniel

If you just need one Windows application, do you also need the features of the latest VB? If not, then I suggest you downgrade to 4.0.12 and stick with that, or any other version you know that works.

What happens if you point to a file on your local hard drive or don't ignore the permissions of the other drive (or set the permissions straight)?

Thank you for your suggestions.

If you just need one Windows application, do you also need the features of the latest VB? If not, then I suggest you downgrade to 4.0.12 and stick with that, or any other version you know that works.

I only upgraded because the last version I had (4.0.4) wouldn't launch.

What happens if you point to a file on your local hard drive or don't ignore the permissions of the other drive (or set the permissions straight)?

I don't have a VM on my boot volume and I've never had any problem in the past using VMs from a non-booting volume with "Ignore permissions" ticked. VirtualPC (in the PPC days), SheepShaver, Fusion and a trial of Parallels and the earlier versions of VB have all worked in this type of situation. I just don't care to have a VM on my boot volume.

The volume where all my guest VMs are kept is a non-booting volume. I've always had it set to ignore permissions.

Thanks again,
-Daniel

Then I still recommend to check the permissions and change it if required. You can also try to start VirtualBox from a terminal, then you may see what the error is on the shell.

Then I still recommend to check the permissions and change it if required.

Administrator has read, write, execute permissions.

You can also try to start VirtualBox from a terminal, then you may see what the error is on the shell.

I opened VB from the Terminal.

Code: Select all

$ open /Applications/VirtualBox.app

I received no errors. Should I open using another command?

Thanks,
-Daniel

Today I tried VB on my experimental installation of ReactOS that I used with v 4.0.4, too. This worked. It is located in the same place as Windoze XP, but still VB says it cannot find the file to Windoze XP.

-Daniel

Ok, so it keeps telling something is missing. But, you never actually told us what it is, that's missing. Post a log of the VM when you start it. Attach it here using the attachment option.

The error message didn't give a file name or file type or any other info to diagnose the problem. I checked Console and there is no log relevant.
I tried again today to open the WinXP VM, but now it won't even recognize the Winbloze.vbox file as a legitimate file type. Whereas the ReactOS.vbox it does. However I can boot into Mac OS X 10.5.8 and run VB v 4.0.4 and both files are recognized and they work as well as one could expect.
(FWIW - I have 10.4.11, 10.5.8, 10.6.6, 10.7.1 Mac OSes - each partitioned - on this one HDD).

-Daniel

theDaniel wrote:(FWIW - I have 10.4.11, 10.5.8, 10.6.6, 10.7.1 Mac OSes - each partitioned - on this one HDD).

-Daniel

Are all those OS versions looking in the same user folder? Because if they each have their own user folders on each partition you'll only be able to start up a VM that you installed while running that version OS (unless you do some creative editing of the VirtualBox.XML file).

rpmurray wrote:Are all those OS versions looking in the same user folder?

No. I never would have thought of that, but it might be worth trying, not for VB, but just because. But I probably would run into problems because of differences in the OSes, especially OS 10.7.

rpmurray wrote:Because if they each have their own user folders on each partition you'll only be able to start up a VM that you installed while running that version OS (unless you do some creative editing of the VirtualBox.XML file).

Then that is probably why it won't work. The first reasonable answer/suggestion. Thanks a lot!

Yes, I see by the user's manual the Mac version is more limited than Windoze or Linux.

Thanks again,
-Daniel

rpmurray wrote: ... if they each have their own user folders on each partition you'll only be able to start up a VM that you installed while running that version OS (unless you do some creative editing of the VirtualBox.XML file).

With the inspiration of iroctw's post: http://forums.virtualbox.org/viewtopic. ... 17#p200917

I was able to deduce I could just copy files from partition 1: /Users/me/Library/VirtualBox/ to partition 4: /Users/me/Library/VirtualBox/
Seems to work....

Eventually I want to automate it such that when I login and use VB from one partition or the other, the files on the opposite partition are automatically updated. I have a first draft of an Applescript to do the automation.

Thank you everyone for your questions, comments and suggestions!

-Daniel

Wouldn't it be better and easier to create a separate partition to store the VMs on, which all supported OSX releases can draw from? You can easily change the default location of the VMs using the GUI, or set the VBOX_USER_HOME along with it to have the main settings file there too. That way, you save disk space (only one VM in one location, instead of one VM in multiple) and settings stay in sync without external interference.

Sasquatch wrote:Wouldn't it be better and easier to create a separate partition to store the VMs on, which all supported OSX releases can draw from? You can easily change the default location of the VMs using the GUI, or set the VBOX_USER_HOME along with it to have the main settings file there too. That way, you save disk space (only one VM in one location, instead of one VM in multiple) and settings stay in sync without external interference.

I'm not sure I follow you... I thought that that was what I am doing.

Not really. You are constantly moving and updating your /Users/username/Library/VirtualBox between the different OSes. With my idea, you have only one location where the VMs are stored, so a sync between the user folders are no longer required. E.g. you create a snapshot in 10.6, and you will see the difference in 10.7 without requiring any sync or update or anything.

Sasquatch wrote:Not really. You are constantly moving and updating your /Users/username/Library/VirtualBox between the different OSes. With my idea, you have only one location where the VMs are stored, so a sync between the user folders are no longer required. E.g. you create a snapshot in 10.6, and you will see the difference in 10.7 without requiring any sync or update or anything.

Maybe I'm misunderstanding... /Users/username/Library/VirtualBox/ is a directory into which are the following files are located: compreg.dat, VirtualBox.xml, VirtualBox.xml-prev, and xpti.dat. (Is there a way to change this placement?

Will VB follow Symlinks?) Without these files duplicated in partition 1/Users/username/Library/VirtualBox/ to partition 4/Users/username/Library/VirtualBox/ I get the "Error: File Not Found" when trying to setup a VM in the opposite partition using the same VM image.

The virtual machine is in partition 2/Guest OS Folder/Windows Drive Images/
The VM settings are in partition 2/Guest OS Folder/VBox ƒ/Stupid1-2/
There is no OS on partition 2.

BTW it's Mac OS X 10.5 and 10.7, not 10.6. Really, I only use 10.6 for testing software solutions for clients, etc, and don't have VB installed there.

virtualbox.org

Error: File Not Found

Error: File Not Found

Re: Error: File Not Found

Re: Error: File Not Found

Re: Error: File Not Found

Re: Error: File Not Found

Re: Error: File Not Found

Re: Error: File Not Found

Re: Error: File Not Found

Re: Error: File Not Found

Re: Error: File Not Found

Re: Error: File Not Found

Re: Error: File Not Found

Re: Error: File Not Found

Re: Error: File Not Found

Re: Error: File Not Found