Custom Query (16363 matches)
Results (577 - 579 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #15088 | worksforme | vagrant+virtualbox. Need some advice. | ||
| Description |
vboxdrv kernel module doesn't autostart, therefore I have to exec manually "sudo /usr/lib/virtualbox/vboxdrv.sh" each time. I have tried installing Nvidia cuda on my PC, that has no nvidia graphic card. Now I uninstall already the cuda developers software , but consequences still occur: WARNING: The vboxdrv kernel module is not loaded. Either there is no module
dkms status vboxhost, 5.0.15, 3.10.0-327.4.5.el7.x86_64, x86_64: installed [andre@andre mail]$ sudo ln -s /usr/lib/virtualbox/vboxdrv.sh /sbin/rcvboxdrv [andre@andre mail]$ sudo /sbin/rcvboxdrv setup Stopping VirtualBox kernel modules [ OK ] Uninstalling old VirtualBox DKMS kernel modulesdepmod: ERROR: fstatat(6, nvidia.ko): No such file or directory
Trying to register the VirtualBox kernel modules using DKMSdepmod: ERROR: fstatat(6, nvidia.ko): No such file or directory
Starting VirtualBox kernel modules [ OK ] |
|||
| #10409 | worksforme | vBoxHeadless.exe has stopped working | ||
| Description |
Running a Windows 7 (x64) guest on a Windows 2008 host. I'm running the guest headless by starting with vboxmanage.exe using --headless. I'm running VirtualBox v4.1.12 (but this was also happening with 4.1.10). My guest OS is running nothing but iTunes. Quite a large iTunes Library, but it isn't very active. I'm syncing with a couple of iOS devices over wifi, which normally works fine. However, almost consistently, after a day or so, vboxheadless.exe crashes when I do "something" on the guest OS (eg, initiate a wifi sync, or RDC into the guest and do something in iTunes). The error I'm getting on the host is: vBoxHeadless.exe has stopped working Problem signature: Problem Event Name: APPCRASH Application Name: VBoxHeadless.exe Application Version: 0.0.0.0 Application Timestamp: 4f799967 Fault Module Name: VBoxDDU.dll Fault Module Version: 0.0.0.0 Fault Module Timestamp: 4f799939 Exception Code: c0000005 Exception Offset: 0000000000006e69 OS Version: 6.0.6002.2.2.0.274.10 Locale ID: 2057 Additional Information 1: 1980 Additional Information 2: 4516a63f978ac9b86b1db4b61c646754 Additional Information 3: 90bd Additional Information 4: f45d1954810729f2936aa6a736b2d63e |
|||
| #21041 | fixed | v6.1.37 Test Builds Fail to Install - Signature verification failed while checking integrity of driver package 'VBoxSup.inf' | ||
| Description |
Originally reported here: https://forums.virtualbox.org/viewtopic.php?f=15&t=106662v6.1.37 Test Build 152627... fails to install. It says: "Oracle VM VirtualBox 6.1.37 Setup Wizard ended prematurely" and VirtualBox Installer Installation failed! Error: Fatal error during installation. Tested on Windows 10 Release Preview (19045.1865), and Windows 11 Dev Channel (25169.1000) ... since those are all that I have readily available. Is the installer busted for this VirtualBox Test Build? Oracle VirtualBox v6.1.36 Build 152435 ... continues to install fine. And I'm nearly sure that all the v6.1.35 Test Builds installed fine, too, from my testing. =============================== Bug Details: When I run the installer with option "--logging", I'm able to get an install log file in C:\Users\{User}\AppData\Local\Temp See attached to compare these: VBoxInstallLog - 6.1.36 r152435.txt VBoxInstallLog - 6.1.37 r152676.txt The main problem appears to be: DIFXAPP: ERROR: Signature verification failed while checking integrity of driver package 'VBoxSup.inf' ('C:\Program Files\Oracle\VirtualBox\drivers\vboxsup\VBoxSup.inf'). (Error code 0x800B0109: A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider.) Is it possible that 6.1.35 Test Builds were WHQL signed, but 6.1.37 Test Builds are not? Note: I don't have my 6.1.35 Test Builds anymore, but I'm sure they worked. |
|||

