Opened 11 years ago
Closed 9 years ago
#13016 closed defect (fixed)
newly launched VM fails with RPC_S_SERVER_UNAVAILABLE while Manager exits
Reported by: | Mihai Hanor | Owned by: | |
---|---|---|---|
Component: | other | Version: | VirtualBox 4.3.10 |
Keywords: | Cc: | ||
Guest type: | all | Host type: | Windows |
Description
Host: Windows 7 SP1 x64
I can reproduce this at will, using VirtualBox 4.3.10 and 4.3.11-93572. I actually stumble upon it while playing with the test build 4.3.11-93572.
Steps to reproduce:
- Start the VirtualBox Manager
- Start a VM from within the VB Manager and immediately press Alt+F4 to close the Manager. The two must be executed in quick succession (almost instantaneous). Or there must be something else to slow down the execution.
The VM fails to start with this error:
Callee RC: RPC_S_SERVER_UNAVAILABLE 0x800706BA (0x800706BA)
Change History (6)
comment:1 by , 11 years ago
comment:2 by , 10 years ago
4.3.16 has the same issue. The only difference, with 4.3.16, is that the existing VBoxSVC process crashes at exit.
comment:3 by , 10 years ago
This error code means that some VirtualBox component crashed. Most likely it's a very early crash during VM powerup. Log file might give hints (if it doesn't get created it's a very very early crash).
comment:4 by , 10 years ago
The only log that gets created is the VBoxStartup.log file. I thought that the RPC_S_SERVER_UNAVAILABLE error refers to the COM service not being available to the newly launched VirtualBox process, while the exiting Manager process closes it connection to the COM service (I have no idea how COM works). The COM service doesn't exit, it continues to run and to do its job for the existing VirtualBox processes and for new processes (if not launched in the same manner). I'll try the OSE build.
Another VM is successfully started, using the existing COM service.