Custom Query (16363 matches)
Results (460 - 462 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #17682 | duplicate | vboxdrv.sh: failed: modprobe vboxpci failed at 4.15.11-1.el7.elrepo.x86_64 -> duplicate of #17683 | ||
| Description |
centos7 update kernel to 4.15.11 elrepo ,and vbox install have some problems with "vboxpci: Unknown symbol vfs_write (err 0)" uname -a Linux crmdev205 4.15.11-1.el7.elrepo.x86_64 #1 SMP Mon Mar 19 11:46:06 EDT 2018 x86_64 x86_64 x86_64 GNU/Linux
Verifying archive integrity... All good. Uncompressing VirtualBox for Linux installation............. VirtualBox Version 5.1.34 r121010 (2018-02-26T15:29:57Z) installer Removing previous installation of VirtualBox 5.1.32 r120294 from /opt/VirtualBox Installing VirtualBox to /opt/VirtualBox Python found: python, installing bindings... vboxdrv.sh: failed: modprobe vboxpci failed. Please use 'dmesg' to find out why. There were problems setting up VirtualBox. To re-start the set-up process, run
as root. VirtualBox has been installed successfully. You will find useful information about using VirtualBox in the user manual
and in the user FAQ We hope that you enjoy using VirtualBox. [root@crmdev205 soft]# dmesg | tail -f [1746570.104013] vboxdrv: Successfully loaded version 5.1.34 (interface 0x002a0000) [1746570.312366] VBoxNetFlt: Successfully started. [1746570.318263] VBoxNetAdp: Successfully started. [1746570.321467] vboxpci: Unknown symbol vfs_write (err 0) [1747176.620175] vboxdrv: Found 32 processor cores [1747176.635978] vboxdrv: TSC mode is Invariant, tentative frequency 1999998028 Hz [1747176.635979] vboxdrv: Successfully loaded version 5.1.34 (interface 0x002a0000) [1747176.840965] VBoxNetFlt: Successfully started. [1747176.844354] VBoxNetAdp: Successfully started. [1747176.846577] vboxpci: Unknown symbol vfs_write (err 0) |
|||
| #20965 | fixed | vboxdrv.sh asks user on Debian system to disable SecureBoot | ||
| Description |
In setup() of vboxdrv.sh there is following code if test -n "$HAVE_SEC_BOOT" &&
type update-secureboot-policy >/dev/null 2>&1; then
SHIM_NOTRIGGER=y update-secureboot-policy --new-key
fi
This leads to a prompt to disable SecureBoot. This is both unexpected and unwanted. Happening on Debian 11 |
|||
| #14665 | fixed | vboxdrv.service unit file contains an extra '$' character in the "After=" line -> fixed in 5.0.x and later as of October 9 2015 | ||
| Description |
Greetings, In Debian packages of VBox 5.0.6, the /etc/init.d scripts have been replaced with, among others, native systemd units in /lib/systemd/system. However, the /lib/systemd/system/vboxdrv.service file that is generated by the postinst-common.sh script based on LSB info in /usr/lib/virtualbox/vboxdrv.sh contains an extra '$' character in the "After=" line. After installing the Debian package of VBox 5.0.6, this line in the vboxdrv.service reads: After=$syslog.service As systemd does not recognize such service, it complains during system boot: Oct 04 10:23:32 rameau systemd[1]: [/lib/systemd/system/vboxdrv.service:5] Failed to add dependency on $syslog.service, ignoring: Invalid argument This error is caused by the /usr/lib/virtualbox/routines.sh that does not remove the '$' character from system facility names as parsed from the vboxdrv.sh file when these facilities are translated into systemd unit files. I am attaching a patch that corrects the routines.sh script so that any '$' characters read in names of system facilities from LSB tags are removed. The patch is based on an additional use of the tr tool to delete the unwanted characters. In Debian, the tr tool is a part of the coreutils package which is an essential package, and so does not incur any additional package dependency. Please consider integrating these corrections. Thank you! Best regards, Peter |
|||

