After vbox guest addition uninstallation: Kernel module is still existing

[jmar83_the2nd]

Hi there

My problem is: After vbox guest additions uninstallation, the Kernel module is still existing and will be loaded on start!?

The host i use is Windows 10 Pro x64.

I uninstalled the drivers with that command:
/usr/sbin/vbox-uninstall-guest-additions

After that, i've done a restart via "init 6".

Then, the file /usr/sbin/vbox-uninstall-guest-additions was deleted, i checked that with "cat /usr/sbin/vbox-uninstall-guest-additions" ... message: "File or directory was not found"

BUT: When i enter "modinfo vboxguest", it seems the kernel module still exists AND will be loaded on start:

Code: Select all

root@xxx-yyy-v5:~# modinfo vboxguest
filename:       /lib/modules/4.19.0-0.bpo.9-amd64/kernel/drivers/virt/vboxguest/vboxguest.ko
license:        GPL
description:    Oracle VM VirtualBox Guest Additions for Linux Module
author:         Oracle Corporation
alias:          pci:v000080EEd0000CAFEsv00000000sd00000000bc*sc*i*
depends:
retpoline:      Y
intree:         Y
name:           vboxguest
vermagic:       4.19.0-0.bpo.9-amd64 SMP mod_unload modversions
signat:         PKCS#7
signer:
sig_key:
sig_hashalgo:   md4

When i remember right, the kernel 4.19 is from the stretch-backports APT-repository, but that should no be the problem because i complied it with the correct kernel header files. (maybe that's not officially supported, but that doesn't matter regarding my question about a properly uninstallation)

So: How to uninstall ALL drivers files / directories / modules / entries properly? I don't like if i have critical systems in an inconsistent state like that!

Thank you very much for your feedbacks! :-)

[jmar83_the2nd]

It seems i'm not the only one that haves that issue...

viewtopic.php?f=3&t=96320

...but no anwser since more that 1/2 on the thread i linked here??

[jmar83_the2nd]

And same with "vboxvideo", equivalent to the linked thread:

Code: Select all

root@xxx-yyy-v5:~# modinfo vboxvideo
filename:       /lib/modules/4.19.0-0.bpo.9-amd64/kernel/drivers/staging/vboxvideo/vboxvideo.ko
license:        GPL and additional rights
description:    Oracle VM VirtualBox Graphics Card
author:         Oracle Corporation
alias:          pci:v000080EEd0000BEEFsv*sd*bc*sc*i*
depends:        drm,drm_kms_helper,ttm
staging:        Y
retpoline:      Y
intree:         Y
name:           vboxvideo
vermagic:       4.19.0-0.bpo.9-amd64 SMP mod_unload modversions
signat:         PKCS#7
signer:
sig_key:
sig_hashalgo:   md4
parm:           modeset:Disable/Enable modesetting (int)

[multiOS]

The method for uninstalling VirtualBox Guest Additions from a Linux ViM is described in the VirtualBox User Manual Section 4.2.2.4 and I don't see any similarity to the procedure you described.

[jmar83_the2nd]

Other way, same result...

So how to REALLY solve the problem?

[scottgus1]

Most definitely a Linux Guests problem. Seems the host isn't the issue, as GAs get installed on the guest.

[scottgus1]

As a suggestion, to prove this:

Other way, same result...

Start again with a fresh Linux guest, get the GAs installed, then use the Virtualbox method to unuinstall them. Post evidence to prove you get the same result.

[jmar83_the2nd]

Thank you for your feedback.

The problem was that the stretch-backports kernel 4.19.x was not 100% compatible with the vbox display drivers... no errors or warnings, but no fullscreen...

IMPORTANT: if you want stretch-backport Kernel, you have to install the DRIVERS FIRST (!!), and THEN the streck-backport-Kernel 4.19. The other way will cause an unsolvable (even with "aptitude") dependency problem!!

But on my Debian 9 i have start menu on boot process, and there i can select the old kernel so i saw. With that, full screen works again.

Maybe there is another virtual graphics adapter (3 virtual ones, 1 is "none" (headless mode??) in VirtualBox 6.x) that doesnt have that problem with Debian 9 stretch-backport-Kernel 4.19.x?

[scottgus1]

So just to clarify, was the issue with failed-to-uninstall GAs coming from the stretch-backports kernel?

Starting a guest "headless" really acts as "Screenless". The guest video still processes, it is ready for VRDPing or showing Detachable.

There is the fourth option "None" for video card type that would result in a truly "headless" guest with no video and needs SSH or text-only remoting in. Probably only for text-only-capable server OS's.

[jmar83_the2nd]

"So just to clarify, was the issue with failed-to-uninstall GAs coming from the stretch-backports kernel?"

I don't have any evidence for that. But maybe that's the reason. (?)

Should i start with original strech 4.9 kernel, then uninstall? Then look what's going on with the 2 kernel modules - they are still existing or not?

[scottgus1]

Unfortunately I have absolutely no idea how to troubleshoot anything inside a Linux OS. Every time I use Linux I have to live on Google.

But I would guess that if you start with a stock average Linux guest, install the GAs, then uninstall them, and don't see the GAs pieces left over, then try the same after putting in the backport kernel and find the GAs leave pieces behind post-backport-kernel, then that might help the devs look for a possible glitch.

[jmar83_the2nd]

OK, thx! :-)