VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (1300 - 1302 of 16363)

Ticket Resolution Summary Owner Reporter
#16584 obsolete Trying to start a VM that worked and got the following thrown... FloydB
Description

NamedPipe#0 failed to bind to local socket /var/folders/13/jh1sz7f56_1_ybtkt_ptd2fm0000gn/T/gns3_vbox/bec267c4-793b-4ffa-b8fb-71ea51f655b9 (VERR_FILE_NOT_FOUND).

Result Code: NS_ERROR_FAILURE (0x80004005) Component: ConsoleWrap Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

#18318 duplicate Virtualbox leaves multiple services running after shutdown Fochi
Description

Bug description and How to reproduce: Linux creates 3 processes when you launch VirtualBox 6.x GUI: VBoxSVC, VBoxXPCOMIPCD and the VirtualBox application.

If you close the VirtualBox application, the process should end (as it occurs with VirtualBox 5.2 and older), but the VirtualBox 6.x process stays running in the background.

Every time you launch the VirtualBox application, a new VirtualBox process is created. All those processes stay running in background after you close each application.

When you reboot your desktop, VirtualBox will automatically launch as many copies of the VirtualBox GUI as you have opened and closed in your last desktop section. And as all of them will be opened again, every passing day you have to close more and more VirtualBox instances.

Affected versions: This bug was introduced in VirtualBox 6.0.0 Host : Linux Fedora 29 last update on 2019/01/16 Desktop: KDE5 Guests : There is no need to launch a Guest machine to see this bug.

I reverted to VirtualBox 5.2 and confirmed that the bug only exists in version 6.0.0 and above.

#8626 obsolete win7-64 host crashes vm window after hibernate FokeyJoe
Description

I have a Toshiba Satellite C660D running Windows 7 64-bit host. I'm running Ubuntu 32-bit 10.04 as guest. When I finish work for the evening, I pause the vm window, then put the host into hibernate. 10-20% of the time when I start the laptop again in the morning the VM window is unresponsive (i.e. doesn't repaint, menu not working, not responding notice in the window title). Virtualbox is still running okay, though, and claims the vm has been aborted. I'm attaching a log which does show some kind of error at the end.

Batch Modify
Note: See TracBatchModify for help on using batch modify.
Note: See TracQuery for help on using queries.

© 2024 Oracle Support Privacy / Do Not Sell My Info Terms of Use Trademark Policy