VirtualBox

Ticket #17189 (new defect)

Opened 3 months ago

Last modified 6 weeks ago

New addons 5.2.1 Issues -> fixed in 5.2.2

Reported by: chad Owned by:
Priority: major Component: guest additions
Version: VirtualBox 5.2.0 Keywords:
Cc: Guest type: Linux
Host type: Linux

Description

1) the VBoxLinux.run script is no longer executable 2) I received an errror"failed: modprobe vboxsf ..." something like that

Change History

comment:1 Changed 3 months ago by chad

Scratch the 1st issue, I was looking at the wrong thing

Verifying archive integrity... All good.
Uncompressing VirtualBox 5.2.1 Guest Additions for Linux........
VirtualBox Guest Additions installer
Removing installed version 5.1.28 of VirtualBox Guest Additions...
Copying additional installer modules ...
Installing additional modules ...
VirtualBox Guest Additions: Building the VirtualBox Guest Additions kernel modules.
VirtualBox Guest Additions: Running kernel modules will not be replaced until the system is restarted
VirtualBox Guest Additions: Starting.
VirtualBox Guest Additions: modprobe vboxsf failed

comment:2 Changed 3 months ago by mrchin4da2009

I am having the same issue and I have tried using the other two images that are provided on the download page.

Host: Windows 7 Guest: Linux 4.4.90-28-default x86_64

dmesg output:

vboxsf: Unknown symbol VboxGuestIDC (err 0)
Last edited 3 months ago by mrchin4da2009 (previous) (diff)

comment:3 follow-up: ↓ 4 Changed 3 months ago by michael

The message "modprobe vboxsf failed" is just cosmetic, not a real problem, but I agree that it is confusing and should be fixed.

@mrchin4da2009 I am guessing that your issue is completely different, but you do not provide any information to let me tell, such as your distribution (wild guess: openSUSE?)

comment:4 in reply to: ↑ 3 Changed 3 months ago by mrchin4da2009

Replying to michael:

The message "modprobe vboxsf failed" is just cosmetic, not a real problem, but I agree that it is confusing and should be fixed.

@mrchin4da2009 I am guessing that your issue is completely different, but you do not provide any information to let me tell, such as your distribution (wild guess: openSUSE?)

Yes - OpenSuse Leap 42.3

I received the same error as stated for the modprobe. Additionally, none of the shared clipboard or shared files work. I have downgraded back to 5.1.30 and has corrected my issues.

Last edited 3 months ago by mrchin4da2009 (previous) (diff)

comment:5 Changed 2 months ago by ech68

Last edited 2 months ago by ech68 (previous) (diff)

comment:6 Changed 8 weeks ago by michael

Please try 5.2.2. Note that there are still problems with Linux VMs with 3D enabled, ticket #17190 is for that. And the message about "modprobe vboxsf failed" may still appear, as it is caused by the old Guest Additions which are being removed, not the new ones being installed.

comment:7 Changed 6 weeks ago by michael

  • Summary changed from New addons 5.2.1 Issues to New addons 5.2.1 Issues -> fixed in 5.2.2

Regarding the 3D issues, I hope that they are solved in the most recent development (not 5.2 series) test builds[1]. If not, please continue on ticket #17190, or open a new ticket if your issue is unrelated.

[1] https://www.virtualbox.org/wiki/Testbuilds

comment:8 Changed 6 weeks ago by TGOS

I'm having the same problem as mrchin4da2009. Installing guest additions also say

VirtualBox Guest Additions: modprobe vboxsf failed

So I ran "sudo modprobe vboxsf" and it says

modprobe: ERROR: could not insert 'vboxsf': Unknown symbol in module, or unknown parameter (see dmesg)

When calling "dmesg" it says:

vboxsf: Unknown symbol VBoxGuestIDC (err 0)

Since I also had the 3D problem, I'm running 5.2.97 r119529 withe the appropriate extension pack and I installed the guest additions included with that version. The guest system is a debian latest: SMP Debian 4.9.51-1 (2017-09-28) with all packets being up-to-date.

Last edited 6 weeks ago by TGOS (previous) (diff)

comment:9 Changed 6 weeks ago by michael

Please see comment 8. That is a problem of the old Additions version which is already installed, not the new one being installed, and should be fixed by a reboot.

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use