#18577 closed defect (obsolete)
Virtual Box 6.0.6 Fails to upgrade Oracle Linux 6
Reported by: | DonC | Owned by: | |
---|---|---|---|
Component: | guest additions | Version: | VirtualBox 6.0.6 |
Keywords: | Cc: | ||
Guest type: | Linux | Host type: | Windows |
Description (last modified by )
When I try and upgrade a Linux 6( xxx) to use VB 6.0.6, I get the following errors:
Verifying archive integrity... All good. Uncompressing VirtualBox 6.0.6 Guest Additions for Linux........ VirtualBox Guest Additions installer Removing installed version 6.0.6 of VirtualBox Guest Additions... vboxadd-service.sh: Stopping VirtualBox Guest Addition service. You may need to restart your guest system to finish removing guest drivers. Copying additional installer modules ... Installing additional modules ... VirtualBox Guest Additions: Starting. VirtualBox Guest Additions: Building the VirtualBox Guest Additions kernel modules. This may take a while. VirtualBox Guest Additions: To build modules for other installed kernels, run VirtualBox Guest Additions: /sbin/rcvboxadd quicksetup <version> VirtualBox Guest Additions: or VirtualBox Guest Additions: /sbin/rcvboxadd quicksetup all VirtualBox Guest Additions: Building the modules for kernel 4.1.12-124.26.7.el6uek.x86_64. SELinux: Could not downgrade policy file /etc/selinux/targeted/policy/policy.24, searching for an older version. SELinux: Could not open policy file <= /etc/selinux/targeted/policy/policy.24: No such file or directory libsemanage.semanage_reload_policy: load_policy returned error code 2. SELinux: Could not downgrade policy file /etc/selinux/targeted/policy/policy.24, searching for an older version. SELinux: Could not open policy file <= /etc/selinux/targeted/policy/policy.24: No such file or directory libsemanage.semanage_reload_policy: load_policy returned error code 2. /usr/sbin/semanage: Could not commit semanage transaction VirtualBox Guest Additions: Running kernel modules will not be replaced until the system is restarted Building the VirtualBox Guest Additions kernel modules. This may take a while. To build modules for other installed kernels, run /sbin/rcvboxadd quicksetup <version> or /sbin/rcvboxadd quicksetup all Running kernel modules will not be replaced until the system is restarted vboxadd-service.sh: Starting VirtualBox Guest Addition service. Press Return to close this window...
What can I do to fix this. During reboot, I get the same error.
Attachments (3)
Change History (15)
by , 6 years ago
Attachment: | Linux 6.x-2019-04-18-18-43-39.log added |
---|
comment:1 by , 6 years ago
Not sure why it attached the log twice, but they are most likely the same.
comment:3 by , 6 years ago
You need to disable SecureBoot, or to sign the kernel modules yourself, Oracle doesn't provide signed kernels.
comment:4 by , 6 years ago
Okay - turning selinux to permissive solved the errors with selinux. However, now at each boot, I get this notice during boot...
Bringing up loopback interface: ^[[60G[^[[0;32m OK ^[[0;39m]^M Bringing up interface eth0: Determining IP information for eth0... done. ^[[60G[^[[0;32m OK ^[[0;39m]^M VirtualBox Guest Additions: Starting. VirtualBox Guest Additions: Building the VirtualBox Guest Additions kernel modules. This may take a while. VirtualBox Guest Additions: To build modules for other installed kernels, run VirtualBox Guest Additions: /sbin/rcvboxadd quicksetup <version> VirtualBox Guest Additions: or VirtualBox Guest Additions: /sbin/rcvboxadd quicksetup all VirtualBox Guest Additions: Running kernel modules will not be replaced until the system is restarted Starting auditd: ^[[60G[^[[0;32m OK ^[[0;39m]^M
Does this mean that the modules are rebuilding and not available?
comment:5 by , 6 years ago
No, that means that there was no error during the installation/compilation of the kernel modules, you don't see any errors, right?
comment:6 by , 6 years ago
Other than seeing this building going on at each boot, it seems to be working okay. Why is it that it "looks like" the modules are being built every time the machine is booted?
Is secure boot part of VirtualBox or are you talking about the machine BIOS?
comment:7 by , 6 years ago
Secure boot is a feature of the UEFI BIOS (if you will forgive the sloppy terminology use). In this case it refers to the host as we do not currently support it in the guest.
You should not get that rebuild notification on every boot. To investigate, please run
sh -x /sbin/rcvboxadd start
as root, capture the output and attach it to this ticket.
comment:9 by , 6 years ago
I just noticed that I said that the guest was Oracle Linux 9 - That is incorrect! DUH
The guest OS is Oracle Linux 6 (4.1.12-124.26.7.el6uek.x86_64). I am unsure how to change the title of the bug. Sorry - must have been very sleepy.
comment:10 by , 5 years ago
Still the same behavior with VB 6.0.10 with the current Linux 6 release.
comment:11 by , 5 years ago
Resolution: | → obsolete |
---|---|
Status: | new → closed |
I do not see this behavior complained about with both 6.0.14/18 and 6.1.2/4 on standard OL6 installation.
Have you enabled SELinux manually?
Is that problem still happening? If yes, please provide information on how to reproduce this problem and re-open the bug.
comment:12 by , 5 years ago
Description: | modified (diff) |
---|---|
Summary: | Virtual Box 6.0.6 Fails to upgrade Oracle Linux 9 → Virtual Box 6.0.6 Fails to upgrade Oracle Linux 6 |
Machine log file