VirtualBox

Ticket #8494 (new defect)

Opened 3 years ago

Last modified 22 months ago

VirtualBox Manager fails to open on Win7 64bit - may start once

Reported by: paineta Owned by:
Priority: major Component: GUI
Version: VirtualBox 4.0.4 Keywords: manager VboxSVC GUI control
Cc: Guest type: other
Host type: Windows

Description

Recently the VirtualBox Manager fails to open. After a reboot or reinstalling 4.0.4 it MAY start the first time, but if closed it will not reopen.

After starting the applicaiton and looking at the processes, VboxSVC.exe forks and appears to start under the svchost.exe, and the VirtualBox.exe process is started, but there is no GUI displayed.

If I kill the VboxSVC.exe process, then the manager GUI opens up, but of course there is nothing functional.

In starting VboxSVC or VirtualBox from the command line, I see no additional output.

Change History

comment:1 Changed 2 years ago by mauromol

I also have problems.

Many times VirtualBox won't start. If I look at the program manager, I see VBoxSVC.exe process take up to 40-50% CPU (I have two cores, so I think it's hogging one core). There's also VirtualBox.exe process that takes <0.01 CPU usage. If I try to start VirtualBox again, new VirtualBox.exe processes are created, but no GUI is shown. If I try to kill VBoxSVC.exe, if a VirtualBox.exe process is running, an error will appear from it saying: RC Chiamante: CO_E_SERVER_EXEC_FAILURE (0x80080005) If more than one VirtualBox.exe process is running, a new VBoxSVC.exe process is started automatically right after I killed it. I'm also pretty sure that sometimes a new VBoxSVC.exe process is automatically started immediately after killing a previous one even if no VirtualBox.exe process is running, but it doesn't happen always.

I am seeing this problem since VirtualBox 4.0.x, but recently (with 4.1.8) this seems to happen VERY often. I have to restart the system to be able to use Virtual Box again.

Please note that:

  • I'm also using Win7 64-bit as the host operating system
  • I often put my system to sleep or hibernate it; may this cause a problem when trying to run Virtual Box after restoring?

comment:2 Changed 2 years ago by mauromol

By the way, how can I add myself to Cc in this installation of Trac? It seems like it's impossible to change the issue (Cc field included).

comment:3 Changed 2 years ago by frank

To subscribe to another ticket, just post a comment to that ticket.

comment:4 Changed 2 years ago by mauromol

My actual problem seems to be the one depicted in the latest comments of #2274 and manifests whenever there's some sound being played while trying to start VBoxSVC.exe!

comment:5 Changed 22 months ago by jacksar

Commented on #2274 but maybe more appropriate here:

Another way to reproduce:

I am on a laptop using an up-to-date Windows 7 64-bit, VirtualBox 4.1.16

I have a USB sound card Muse Pocket LT3 from Hercules. If I play any music on my computer (like with Spotify) then I launch VirtualBox, vboxsvc.exe take 50% load and never start.

I have to kill vboxsvc.exe, close Spotify, launch Virtual Box again, and that work fine. However, if play music again while Virtual Box is running, vboxsvc.exe will start again to take 50% of my CPU after some hours...

On Windows 7, in my device manager, I have 3 audio drivers:

  • Intel(R) High Definition Audio HDMI
  • Muse Pocket LT3
  • Realtek High Definition Audio

I tried to disable only first, then only second, then only third, when I disable Muse Pocket LT3, I can listen music and start Virtual Box without any problem.

For me, the problem is linked with my external USB sound card, I don't know if it's the same with every USB sound cards.

Thank you.

PS: please stop requiring complex registration before submitting a bug report :/

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use