VirtualBox

Ticket #12547 (closed defect: obsolete)

Opened 7 years ago

Last modified 4 years ago

@ VM Machinestartup - EM: Failed to open a session for the virtual machine ...

Reported by: DavidDeb Owned by:
Component: VM control Version: VirtualBox 4.3.6
Keywords: E_FAIL (0x80004005) Cc:
Guest type: Windows Host type: Windows

Description

Hi,

after the update to 4.3.6 I get the following MSG when starting a VM for the SECOND time (the first start up after boot-up works OK)

Failed to open a session for the virtual machine ...

The VM session was closed before any attempt to power it on.

Result Code: E_FAIL (0x80004005) Component: SessionMachine Interface: ISession {12f4dcdb-12b2-4ec1-b7cd-ddd9f6c5bf4d}

Workaround (temporary I hope) : reboot the host machine

Host is: Win7 x64, Guest: WinXP x86

Is this related to Ticket #12424 ??

Thx 4 your attn. and best regards,

David D.

Change History

comment:1 Changed 7 years ago by DavidDeb

Multiple instances of VirtualBox.exe seem to have been started and only 'go away' after rebooting the host, some VMs in this condition do not start at all - just hang during init!

This seems to be more serious than my initial estimation.

comment:2 Changed 7 years ago by frank

How do you start the VM, I guess from the VM selector window? When the VM is terminated, do you terminate the VM selector window before you restart the VM or do you keep this window open? Please exactly describe as exactly as you can the steps how you start the VM(s).

comment:3 Changed 7 years ago by DavidDeb

Hi,

I always start the sessions from the selector window (keeping this window 'Open' until I am done with all VM tasks) - usually with 'double-click' on the VM in the list pane (left). When this issue first occurred, I shut down the selector window and restarted it, then tried to restart the session - this is when the described problem happens. Initially I rebooted the host to clear this, now I find 'Log-off / log-on' resolves the issue. All of the virtual machine processes are killed in the task manager / list and the VM can be started again seemingly normally.

Last edited 7 years ago by DavidDeb (previous) (diff)

comment:4 Changed 4 years ago by aeichner

  • Status changed from new to closed
  • Resolution set to obsolete

Please reopen if still relevant with a recent VirtualBox release.

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use