VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (2002 - 2004 of 16363)

Ticket Resolution Summary Owner Reporter
#16292 obsolete Virtualbox.exe "segfault" cepal
Description

bare-metal: HP Zbook G3 / 15" host OS: Win 7 / 64 / company-controlled updates Vbox: latest official = 5.1.10 r112026 + matching additions guest: Lubuntu (ubuntu + LXDE) 16.04 LTS / 64

description: randomly (within 2-3 hours from start) upon opening a new tab in Firefox in VM (or another new window/tab, ie e-mail in Thunderbird), the host's OS pops up following message and shuts the VM (but doesn't shut, if running the Virtualbox GUI app).

Windows Event message (same memory addresses each time): Application popup: VirtualBox.exe - Application Error : The instruction at 0xbefc53ad referenced memory at 0x000000d0. The memory could not be read.

#16288 obsolete 3D Acceleration Causes VBox to Crash at login Poison
Description

Clean install of Ubuntu. Problem occurs every single time. Occurs on other flavors of linux as well. This did not start happening until the most recent update to VBox. Prior, it was working fine. I have tried nearly every troubleshooting method I could find online.

Guest additions have been installed.

#16287 obsolete Error when starting a new VM Z Hopa
Description

Just did a fresh vanilla install of Fedora 25. Once it was up, went to Oracle and downloaded VirtualBox 5.1.10 for Fedora 25. Installed it, installed the extension pack, and rebooted. Then created a new VM. This VM does not start and throws the following errors:

First error dialog:

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

The virtual machine 'FreeBSD 9' has terminated unexpectedly during startup with exit code 1 (0x1).

Result Code: NS_ERROR_FAILURE (0x80004005)
Component: MachineWrap
Interface: IMachine {b2547866-a0a1-4391-8b86-6952d82efaa0}

Second error dialog (they pop up simultaneously):

Kernel driver not installed (rc=-1908)

The VirtualBox Linux kernel driver (vboxdrv) is either not loaded or there is a permission problem with /dev/vboxdrv. Please reinstall the kernel module by executing

'/sbin/vboxconfig'

as root.

where: suplibOsInit what: 3 VERR_VM_DRIVER_NOT_INSTALLED (-1908) - The support driver is not installed. On linux, open returned ENOENT. 

When I run the command it recommends, it prints the following:

[user0@host0 ~]$ sudo /sbin/vboxconfig
[sudo] password for use0: 
Created symlink /etc/systemd/system/multi-user.target.wants/vboxdrv.service → /usr/lib/systemd/system/vboxdrv.service.
Created symlink /etc/systemd/system/multi-user.target.wants/vboxballoonctrl-service.service → /usr/lib/systemd/system/vboxballoonctrl-service.service.
Created symlink /etc/systemd/system/multi-user.target.wants/vboxautostart-service.service → /usr/lib/systemd/system/vboxautostart-service.service.
Created symlink /etc/systemd/system/multi-user.target.wants/vboxweb-service.service → /usr/lib/systemd/system/vboxweb-service.service.
vboxdrv.sh: Building VirtualBox kernel modules.
This system is not currently set up to build kernel modules (system extensions).
Running the following commands should set the system up correctly:

  yum install kernel-core-devel-4.8.13-300.fc25.x86_64
(The last command may fail if your system is not fully updated.)
  yum install kernel-core-devel
vboxdrv.sh: failed: Look at /var/log/vbox-install.log to find out what went wrong.
This system is not currently set up to build kernel modules (system extensions).
Running the following commands should set the system up correctly:

  yum install kernel-core-devel-4.8.13-300.fc25.x86_64
(The last command may fail if your system is not fully updated.)
  yum install kernel-core-devel

There were problems setting up VirtualBox.  To re-start the set-up process, run
  /sbin/vboxconfig
as root.
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