Page 2 of 2

Posted: 17. Sep 2008, 11:04
by dmfhhp
HI,
I see it with 1.6.6.
It worked perfect until last night. This morning it did not start,
vboxsvc and virtualbox.exe processes are visible in precexp (sysinternals). vmoxmange list vms seams to hange as well.
I guess it is the vboxsvc that hangs.

Repairinstall and a full uninstall/reinstall with reboot did not fix it.
BTW: The PC takes for ever to shutdown if the vboxsvc is running. It cannot be killed !

Yesterday I had a power loss, from recall I had vb running after it.
What does the vboxscv need as resources? I see a process above it that uses dcom. Could dcom be bad?

I you want, I drive the 10 minutes to Endersbach with the PC....

DF :-)

Possible solution

Posted: 17. Sep 2008, 14:36
by dmfhhp
Hi,
I managed to get it working (now with 2.02) and think it might help others...
I also think it is related to the USB redirction driver, but that is just gut feeling.
Here are my steps:
Win XP SP2, 3GB usable ram.
Usb Devices for VMs:
Siemens Gigaset sx353
Hand Held Products Barcode Reader 4600g with USB ComPort emulation
HTC Smart Phone XDA Diamond
They should not be connected to VMs after the renaming of the .virtualbox directory. Any other place of info? In the registry?
Steps:
Uninstall/reboot/install 2.02 did not help.
Renaming the .virtualbox directory in my user account did not help.
Because of the power outage, I set my system back two days ago. This includes a reboot.
Then I unplugged the USB devices that are connected to VMs.
As I unplugged the Siemens phone SX353, the screen went black (no BSOD, just dead). REBOOT with reset button.
Uninstall the V2.02
Reboot
Seeing some .dll files i the installation dir, deleted all 3 of them.
Checking the c:\Windows\INF dir for oemxx.inf files:
Found 6 files with "Sun Microsystems" in them (grep).
Deleted all 6 .inf and corrosponding .pnf files.
(note the oemxx. inf have different numbers (xx), this is caused by the OS)
In the c:\windows\system32\drivers I found a few vbox*.sys files, deleted all vbox*.* there.
Reboot
Install 2.02
Start and it showed the registration screen.
Stop, bring the old .virtualbox contents in place.
Everything seam to work now.

I hope it helps you.... good luck!

Forgot to mention..

Posted: 17. Sep 2008, 14:39
by dmfhhp
Sorry,
In the c:\WINDOWS\Prefetch I found two vb* files.
Deleted them as well before I reinstalled the last time.
Right now there is only one file there...

Posted: 17. Sep 2008, 15:32
by sandervl
Check here for a solution.

Posted: 18. Sep 2008, 09:57
by dmfhhp
Thanks, found it, sounds very similar to my problem.
Actually, as I booted the host this morining, the VB did start but no GUI showed up (as it was yesterday).
Last night one guest had trouble to shutdown (VB said aborted in the list).

I rebooted the host and unplugged all USB devices connected to VB. Then VB started up. Plugging in the phone sx353, the OS ned to install the VB driver, after that it worked in the guest. (the sx353 was unplugged at the first try anyway).

CLosing VB, wait until the svc is down, then plug in all USB devices for VB. Now VB started up just fine.
(Sidenote: Since 2.02 the host do not remember its monitor in a dual monitor environment - they always start on the left one)

DF :-) Gruß vom Wieslauftal.