Page 1 of 1
vbox 2.1.0 freezes when starting a machine
Posted: 23. Dec 2008, 19:29
by fernandoc1
Frequently when I try to start a Virtual Machine, it freezes in the screen with a progress bar saying: "starting machine" and the machine is never started.
Then I press ctrl+alt+del and end all the vbox processes, but the process related with the machine I tried to start, never get out of the processes tree in the task manager, no matter how many times I try to end and how many time I wait.
I think that it should be a problem in the networking system of the virtual box, becouse sometimes, it make windows crash in a blue screen and be restarted.
Do someone have a solution to this issue?
To explain better my situation, I'm using Windows XP x64, and using two network cards, and the virtual machine that I'm using makes use of both cards, in two network adapters separetedly.
Posted: 24. Dec 2008, 19:57
by shokti
have you tried to resume it? mine will freeze 3 time when i start it but it will continue when i resume it.
Posted: 24. Dec 2008, 22:53
by fernandoc1
The problem is that the machine does not start. You are thinking that the machine become paused, but the problem is that the machine don't start, I can't resume a machine that is being started.
Posted: 25. Dec 2008, 00:58
by Sasquatch
Does the log say anything? What about the Event Viewer?
Posted: 25. Dec 2008, 10:29
by lazrman778
fernandoc1, I noticed I have a similiar problem. I have a WinXPx64 host and a Vistax64 guest running the new v2.10 on 1 network interface. I see the problem only when Windows DirectSound and ICH A97 are enabled. When I choose the alternative Null Audio Driver, it boots properly. I can end all but 1 vbox process - which must be the hanging Vistax64. I have to reboot the host OS to reset Vista's status back to powered off. Could it be a sound driver issue?
Posted: 26. Dec 2008, 01:51
by fernandoc1
I haven't tried to disable the sound, but I think that the changes made in this new version delivered some instability to the system. I even tried some fatal blue screens while I were managing the network settings.
These choices to remove the VirtualBox TAP adapter were great, but still a little instable.
I'm confident that in the next realese the vbox will be better.
I wish I could help, providing log files data, but I can't understand the data on the log file.