VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (457 - 459 of 16363)

Ticket Resolution Summary Owner Reporter
#9287 duplicate vboxdrv: [ID 694835 kern.notice] NOTICE: kthread_t::t_pree mpt at 42 bernieh
Description

After upgrading to 4.1.0, the following messages are logged when solaris boots: vboxdrv: [ID 694835 kern.notice] NOTICE: kthread_t::t_pree mpt at 42 vboxdrv: [ID 694835 kern.notice] NOTICE: cpu_t::cpu_runrun

at 232

vboxdrv: [ID 694835 kern.notice] NOTICE: cpu_t::cpu_kprunr un at 233 When the VirtualBox command is executed, it segfaults and the following message appears in the system log: genunix: [ID 269049 kern.notice] NOTICE: VirtualBox[1586] attempt to execute non-executable data at 0xfffffd7ffedec640 by uid 1001

#8859 fixed vboxdrv: 'Default Stop'-value causing trouble on recent Debian and derivatives -> fixed as of 2 Aug 2011 Peter Mattern
Description

The "Default Stop" comment of vboxdrv comprises just run level 1.

On Debian lenny symbolic links K*vboxdrv are established in /etc/rc{0,1,6}.d nevertheless.
On Debian squeeze, a link K*vboxdrv is created in /etc/rc1.d only. Moreover, installing VirtualBox yields an error message

update-rc.d: warning: vboxdrv stop runlevel arguments (0 1 6) do not match LSB Default-Stop values (1)

which can be reproduced by running update-rc.d vboxdrv defaults.
The difference between lenny and squeeze is probably caused by different default behavior of update-rc.d.
Btw. I consider this error message to be buggy itself - should be "... arguments (1) ... values (0 1 6)".

According to http://forums.virtualbox.org/viewtopic.php?f=7&t=37659 Debian derivates seem to be affcted, too.

All other init-scripts belonging to VirtualBox 4.0.6 define 0, 1 and 6 as stop-runlevels, same thing for all init-scripts included in 3.2.12.

#7672 obsolete vboxdrv.sys driver is not uninstalled tunga
Description
  1. When you uninstall VirtualBox, the vboxdrv.sys driver is not uninstalled and the file remains in the c:\windows\system32\drivers\ folder.
  2. Sometimes Vista fails to boot due vboxdrv.sys.
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