VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (1576 - 1578 of 16363)

Ticket Resolution Summary Owner Reporter
#16994 duplicate Inaccessible lists texou
Description

Hi,

While Oracle assertions are for accessibility introducing VBox beta, I can say we are far from it. Beyond bugs I have submitted about crashes and I confirm with this release, a lot of widgets do not have any label on their widgets, hence a screen reader cannot tell what the button does. Filling the label area sends to qt-t-spi what an assistive technology needs to work properly.

Here is an examples:

  • Main window: all the items in the list where is the focus at runtime (so the VMs list) is quite, nothing is sent to qt-at-spi. A label problem on the widgets in the list, which are just missing or not connected to qt-at-spi.
#11684 obsolete Virtualbox periodically "Loses" vboxflt and vboxusb drivers after host reboot texneus
Description

After creating a crossbow virtual network adapter "vnic0" in the host OS, and creating an Ubuntu VM (in this case) named "Sub-Etha" with a bridged network adapter (bridged to the crossbow vnic0), the host intermittently will lose the subject drivers when the host is rebooted (using "shutdown -i6 -g0" from a command line) or is power cycled (using "shutdown -i5 -g0" from a command line). When the drivers are lost, Virtualbox will open as usual but attempting to start the Ubuntu VM results in the Virtualbox displaying the following error in a window after very briefly flashing the BIOS screen:

Failed to open session for the virtual machine Sub-Etha

Failed to open/create the internal network
'HostInterfaceNetworking-vnic0'
(VERR_SUPDRV_COMPONENT_NOT_FOUND).

Failed to attach the network LUN
(VERR_SUPDRV_COMPONENT_NOT_FOUND).

When this occurs, the vbox drivers can be verified as being missing:

# modinfo | grep -i vbox
170 fffffffff7b5a590    ce8 292   1  vboxnet (VirtualBox NetAdp 4.2.10r84104)
172 fffffffff80c9000  34ee0 291   1  vboxdrv (VirtualBox HostDrv 4.2.10r84104)
212 fffffffff7dc1dd8   4580 294   1  vboxusbmon (VirtualBox USBMon 4.2.10r84104)

The drivers can be re-installed as follows:

(shutdown Virtualbox)
# rem_drv vboxflt
# add_drv vboxflt

The drivers can be verified to be re-installed using the first command above:

# modinfo | grep -i vbox
170 fffffffff7b5a590    ce8 292   1  vboxnet (VirtualBox NetAdp 4.2.10r84104)
172 fffffffff80c9000  34ee0 291   1  vboxdrv (VirtualBox HostDrv 4.2.10r84104)
212 fffffffff7dc1dd8   4580 294   1  vboxusbmon (VirtualBox USBMon 4.2.10r84104)
219 fffffffff7dd8a80   7510 293   1  vboxflt (VirtualBox NetDrv 4.2.10r84104)
219 fffffffff7dd8a80   7510   -   1  vboxflt (VirtualBox NetMod 4.2.10r84104)
255 fffffffff8129000   7478 295   1  vboxusb (VirtualBox USB 4.2.10r84104)

(note the addition of the final three lines, 2 relating to vboxflt and 1 relating to vboxusb). The VM will now operate normally. However, the drivers will disappear again after an indeterminant number of host reboots, but is believed to be 10 or less.

NOTE1: This problem and above workaround is also documented in forum thread https://forums.virtualbox.org/viewtopic.php?f=11&t=40509 and dates to at least 2011 with Virtualbox 4.0.4. I could not find an existing bug report for this problem.

NOTE2: Host OS is Openindiana 151a7, however above thread shows issue has also occurred in Sun/Oracle Solaris hosts.

NOTE3: Virtualbox Extension Pack is not installed as it is not required for my VM.

NOTE4: The effect or symptoms of the lost USB driver is unknown - I'm not using any USB devices in the VM, but all three drivers are affected regardless.

NOTE5: Screenshot of error and log files attached.

#10565 invalid Machines are being lost intermittently and replaced with debian6.vbox and test.vbox Glenn McDonald
Description

I'm running the latest version, Windows Server 2008R2 host, Windows 7 guest.

I launch from a desktop icon with the following command:

"C:\Program Files\Oracle\VirtualBox\VirtualBox.exe" --comment "Windows 7 x64" --startvm "Windows7x64" --fullscreen

Every now and then I get an error message stating:

There is no virtual machine named Windows7x64 Could not find a registered machine named 'Windows7x64' Details Result Code: VBOX_E_OBJECT_NOT_FOUND (0x80BB0001) Component: VirtualBox Interface: IVirtualBox {c28be65f-1a8f-43b4-81f1eb60cb516e66}

After this occurs, if I launch the VirtualBox gui, I notice that my VM has disappeared and is replaced with two inaccessible vms:

debian6 (which it thinks is located at D:\VirtualBox\debian6\debian6.vbox) test (which it thinks is located at D:\VirtualBox\VM\test\test.vbox)

My VM is actually located at D:\VirtualMachines\Windows7x64

Every time this occurs I have to clone the VDI and re-build a virtual machine, which causes Windows to need to authenticate again.

I have no idea where it's getting this information from as my VirtualBox.xml file has the correct information in it.

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