OSX-Host, WinXP in Box: VB only starts when Host is online

[Mufasa]

Hi everybody,
I'm having a big problem here with which I am fighting for some time already. The Virtual Box on my OSX does only start when I am online in a network (wlan or wired). But no connection I cannot start VB

I don't think this is a problem with the installed WinXP in VB but probably some VB configuration setting, though I hadn't have this problem on any other device before (neither Win, Mac, Linux nor BSD).

Appreciate every help or suggestion.

[mpack]

We will need precise error messages please. A VM log file would not hurt either.

Minimum information needed for assistance
viewtopic.php?f=24&t=48476

[Mufasa]

Thank you for your fast reply mpack

Here is a screenshot with the precise error message.
imageshack . us/a/img826/3120/vberror.png
(Please delete the spaces in the domains name. I am not allowed to post direct urls here yet, 'cause I just signed up. Have to be member for at least 1 day. Will change it when I have the rights here)

Can you tell me where I can find the VM log file? I'll search for it too...

[mpack]

There was no need to for you to post an obfuscated offsite image link - you can attach images directly here. I've done it for you this time.

The VM log file is called "VBox.log", and can be found in the "Logs" subfolder of your VM folder.

I'd appreciate it if you could also post the ".vbox" file from the VM folder, post it here as a .zip attachment.

One question? You use a removable wireless dongle for internet access? So by "online" you actually mean - when this USB device is plugged in?

[Mufasa]

Ah allright, thank you! Didn't how to attach files.... and now I see the tab for it

Ok, what is stored in the ".vbox"-file. Actually it is the airbook of my colleague and he is veeeeery sensitive with posting files from his computer.... that's why he even told me to black out his name in the screenshot...


No, there is no removable wireless dongle. With "online" I mean when it is connected to the wireless network with the built in adapter or the network cable is pluged in.

This is the log file:

[Mufasa]

I just found something on a wordpress blog by David Prager Banner.
But I'm not really sure if this is exactly the solution for this problem here. And he writes that I have to find out if it is en0 or en1. I don't know how to check which network adapter is used by the VM...

I don't want to send the whole text here.... and since I cannot post website adresses here yet, I think now I have to post an obfuscated link.
I'll change it when I get the rights to do it. Or can you change it for me?
http://brannerchinese.wordpress.com/201 ... not_found/

[mpack]

Actually, I see from the log that you are still running VirtualBox 3.2.6, so you don't have a .vbox file. There is a ".xml" file in the VM folder instead... and the very concept of "VM folder" doesn't mean what it did then, because files were scattered all over the place.

I do see a serious issue in the log file :-

00:00:00.556 Host RAM: 4096MB RAM, available: 170MB
...
00:00:00.636 RamSize <integer> = 0x0000000028000000 (671088640) [640MB]
...
00:00:00.639 VRamSize <integer> = 0x0000000002000000 (33554432) [32MB]

I.e. the VM is configured to use substantially more memory than is available on the host. On current VBox versions this would produce an error (a so-called "guru meditation"). I don't know if this is related to the problems you are seeing, but it certainly will not help.

[Mufasa]

Actually, I see from the log that you are still running VirtualBox 3.2.6, so you don't have a .vbox file. There is a ".xml" file in the VM folder instead... and the very concept of "VM folder" doesn't mean what it did then, because files were scattered all over the place.

Ok, that's good to know Do you think it would help to just upgrade my VirtualBox? Can I do this by simply exporting the VM, uninstall VB, install new VB and import VM or are there more things I have to take care of?

[mpack]

Upgrading VirtualBox would not fix your lack of memory. You should fix that first. If the bridged network problem is caused by a bug then yes I would certainly hope that it would have been fixed in the years since 3.2.6 was current.

Do not export/import. Just copy the .VirtualBox folder (plus contents) to external media as a backup (copy, not move/delete). Then uninstall VBox 3.2.6 and install a more recent version. I would suggest installing v4.1.22 as being the last "stable" version.

When the new VirtualBox starts it will find your existing VMs, i.e. for backwards compatibility it will continue using the old VM folder layout. Hence you should immediately clone your existing VMs using the new GUI cloning feature (right click the VM, select "Clone"). Choose "full clone" and "current state only" if the latter appears as an option. The clones will have the new VM format. After testing you can delete the original VM(s). Finally all your VMs will be converted, but the main VirtualBox control file will still be in the old format. To fix that you shut VBox down, delete the .VirtualBox\VirtualBox.xml file, then start VBox up again. The VMs will be gone, but you can add them back using the Machine|Add... menu item and selecting each .vbox file.

[Mufasa]

That damn OSX!! Couldn't find the .VirtualBox folder - it wasn't in the user home-folder where (I think) it is supposed to be, just like on linux. Also OSX doesn't have extra Program with the Program executable files in it like Windows.... f*** I hate this system
(Sorry that just had to be)

Now I just switched the Network to wireless (I think en0) in the VM configuration dialog.... and it runs with wireless now. Also I can start the VM when not connected. But now the VM doesn't have network connectivity when host computer is connected via network cable plug and wireless is off. Doesn't matter at all!

Anyway thanks a lot you for your support!

[mpack]

I'm afraid I have no experience with OS X. I believe that on Linux any folder that starts with a period '.' is hidden from non-admin users, I suspect the same is probably true on OS X.

[Mufasa]

Yes right, the same on OSX. FIrst I had to find out how to view the hidden folders.... only possible with an terminal code that also kills all open Finder windows. But still there was no .VirtualBox folder. There came some others, but only 4 or 5 folders. Thats too less for the amount of programs that are installed in that Airbook. I don't know where all there others could be. Also I tried to search for it in the whole computer... no result! Crazy thing!

Aah my colleague is happy now that it is working like this, so that's ok

Thank you

[rpmurray]

That damn OSX!! Couldn't find the .VirtualBox folder - it wasn't in the user home-folder where (I think) it is supposed to be, just like on linux. Also OSX doesn't have extra Program with the Program executable files in it like Windows.... f*** I hate this system

Noobs. VirtualBox stores it's files in the users Library folder (I believe the manual even says that. Damn, that needed to be said. )

If you're running a Mac OS earlier than 10.7 (Lion) then the path [hard drive]/Users/[your account]/Library/VirtualBox will get you there. If you're running Lion or Mountain Lion then hold down the option key while clicking on the Go menu in the Finder and the Library folder will be in the list.

[Mufasa]

Noobs.

*hehe* ok ok, when it comes to OSX.... maybe u'r right. For now!

Learning never stops

Thank you, I'll check the library folder.