Page 1 of 2 12 LastLast
Results 1 to 10 of 17

Thread: In VirtualBox 6.1.26 help needed for VirtualBox Guest Additions from Leap 15.3 to function

  1. #1

    Default In VirtualBox 6.1.26 help needed for VirtualBox Guest Additions from Leap 15.3 to function

    I. Background and Introduction

    My “host” operating system has been 64-bit Windows 10 Home Edition for a few years. In Oracle Virtual “Machine” (VM) VirtualBox I have since December of the year 2013 had an openSUSE operating system installed as a “guest” operating system or VM. In Leap-15.2 openSUSE from July 23, 2020 through May or so of the year 2021 a usually quite workable procedure for me to obtain working VirtualBox Guest Additions was by executing VBoxLinuxAdditions.run from Oracle Corporation’s VirtualBox after installing a kernel update in Leap 15.3 or a new version of VirtualBox in Windows 10. However, after upgrading Leap 15.2 to Leap 15.3 I could no longer reliably use this procedure to obtain working VirtualBox Guest Additions in Leap 15.3 with VirtualBox. That is I learned from Larry Finger and/or the Internet that the kernel code in Oracle Corporation’s VirtualBox was apparently for a version of the Linux kernel newer than supplied through openSUSE Leap repositories. So to enable Oracle Corporation’s VBoxLinuxAdditions.run to work properly in openSUSE Leap 15.3 currently requires an openSUSE Leap code writer or writers to backport some kernel code to probably produce a Leap-15.3, kernel-appropriate version of VBoxLinuxAdditions.run. But it appears that this backporting has not always been performed for each new version of VirtualBox from Oracle Corporation and for each new version of the Linux kernel supplied through openSUSE Leap repositories.

    So the alternative for obtaining working VirtualBox Guest Additions has been for me to, instead of producing VirtualBox Guest Additions from the latest version of Oracle Corporation’s VirtualBox, to try to use VirtualBox Guest Additions which come with the Linux kernel or else the VirtualBox Guest Additions in one of the virtualbox-… software packages, which in each of those cases is supplied through openSUSE Leap repositories. (Note that this makes a total of three sources for VirtualBox Guest Additions. And when all three of them are simultaneously installed, I don’t know for certain all of the openSUSE rules or priority for determining which of those three sets of VirtualBox Guest Additions will actually be used.) But I found that one or more functions of the VirtualBox Guest Additions in my Leap-15.3 installation could unfortunately rather easily be lost after making some software changes in that installation. These functions include the sharing of contents between my Windows-10 “host” and Leap-15.3 “guest” operating systems through a folder set up within VirtualBox for them to share and the copying and “pasting” of text via the computer “clipboard” between those two operating systems. And sometimes I saw that three question marks appeared in a window while “booting” my Leap-15.3 installation toward its graphical login screen.

    Thus far my sure means to recover from such malfunctions has been to restore data onto my computer’s internal hard-drive from a backup of those data previously written onto an external hard-drive drive when the VirtualBox Guest Additions were working well for me. However, recovering to a previous state of the computer software was not always a means to proceed with working VirtualBox Guest Additions through updated or altered computer software. So I would instead like to have a means to repair or reconfigure the VirtualBox Guest Additions after one or more of their functions have been lost due to some change in my Leap-15.3 computer software. My approach up to now to proceed onward from a working state of the VirtualBox Guest Additions has been one of attempting to learn what to do from postings on the Internet and to employ methods of guessing with trial and error. These approaches have recently been unproductive uses of my time, including the fact that the restoration of Leap-15.3 data from a hard-drive backup could take about nine hours of time. Furthermore the methods posters posted for obtaining working VirtualBox Guest Additions in versions of openSUSE prior to Leap 15.3 might not apply to Leap 15.3, due to changes in the openSUSE computer software over some years of time. So rather than continue in such a slow, trial-and-error approach I think it would make more sense for me to learn from people who already know how to recover or obtain the functions of VirtualBox Guest Additions from openSUSE Leap-15.3 repositories. So that is my goal here.

    II. Symptoms of My Troubles, Some of My Attempts to Remedy The Troubles, and Some of My Mysteries


    With the installed software packages

    virtualbox-guest-tools 6.1.26-lp153.2.9.3
    virtualbox-guest-x11 6.1.26-lp153.2.9.3
    virtualbox-guest-source 6.1.26-lp153.2.9.3
    virtualbox-kmp-default 6.1.26_k5.3.18_59.19-lp153.2.9.2
    virtualbox-kmp-preempt 6.1.26_k5.3.18_59.19-lp153.2.9.2,

    the running Linux kernel version 5.3.18-59.19-default,
    the installed Linux kernel versions kernel-default 5.3.18-59.24.1 and kernel-preempt 5.3.18-59.24.1, and

    the installed version 6.1.26r145957 (Qt5.6.2) of Oracle VM (Virtual Machine) VirtualBox from Oracle Corporation, Larry Finger on https://bugzilla.opensuse.org/show_bug.cgi?id=1187011 wrote that with virtualbox-guest-source installed the command “sudo /sbin/vboxguestconfig” one can “build” VirtualBox Guest Additions. In addition, in order for vboxguestconfig to be installed in my Leap-15.3 installation from experience on August 17, 2021 I found that it was necessary to have the software package virtualbox-guest-tools installed. Below I show you what occurred after entering the command ./vboxguestconfig in the directory /sbin as a “root” user.

    Code:
    linux-hdi0:/sbin # ./vboxguestconfig
    Kernel modules available. but we will continue...
    virtualbox-guest-source package version doesn't match the version of virtualbox package.
    This situation is probably not fatal, thus we will try to continue ..
    Building kernel modules...
    
    Build of VirtualBox guest kernel modules failed.
    Look at /var/log/virtualbox.log to find reasons.
    linux-hdi0:/sbin #
    
    /var/log/virtualbox.log
    
    === Building 'vboxguest' module ===
    make[1]: Entering directory '/usr/src/kernel-modules/additions/src/vboxguest'
    make V= CONFIG_MODULE_SIG= CONFIG_MODULE_SIG_ALL= -C /lib/modules/5.3.18-59.19-default/build M=/usr/src/kernel-modules/additions/src/vboxguest SRCROOT=/usr/src/kernel-modules/additions/src/vboxguest -j2 modules
    make[2]: Entering directory '/usr/src/linux-5.3.18-59.19-obj/x86_64/default'
      Building modules, stage 2.
      MODPOST 1 modules
    make[2]: Leaving directory '/usr/src/linux-5.3.18-59.19-obj/x86_64/default'
    make[1]: Leaving directory '/usr/src/kernel-modules/additions/src/vboxguest'
    
    === Building 'vboxsf' module ===
    make[1]: Entering directory '/usr/src/kernel-modules/additions/src/vboxsf'
    make V= CONFIG_MODULE_SIG= CONFIG_MODULE_SIG_ALL= -C /lib/modules/5.3.18-59.19-default/build M=/usr/src/kernel-modules/additions/src/vboxsf SRCROOT=/usr/src/kernel-modules/additions/src/vboxsf -j2 modules
    make[2]: Entering directory '/usr/src/linux-5.3.18-59.19-obj/x86_64/default'
      Building modules, stage 2.
      MODPOST 1 modules
    make[2]: Leaving directory '/usr/src/linux-5.3.18-59.19-obj/x86_64/default'
    make[1]: Leaving directory '/usr/src/kernel-modules/additions/src/vboxsf'
    
    === Building 'vboxvideo' module ===
    make[1]: Entering directory '/usr/src/kernel-modules/additions/src/vboxvideo'
    make V= CONFIG_MODULE_SIG= CONFIG_MODULE_SIG_ALL= -C /lib/modules/5.3.18-59.19-default/build M=/usr/src/kernel-modules/additions/src/vboxvideo SRCROOT=/usr/src/kernel-modules/additions/src/vboxvideo -j2 modules
    make[2]: Entering directory '/usr/src/linux-5.3.18-59.19-obj/x86_64/default'
      CC [M]  /usr/src/kernel-modules/additions/src/vboxvideo/vbox_drv.o
      CC [M]  /usr/src/kernel-modules/additions/src/vboxvideo/vbox_irq.o
    /usr/src/kernel-modules/additions/src/vboxvideo/vbox_drv.c:311:6: error: ‘DRIVER_PRIME’ undeclared here (not in a function); did you mean ‘DRIVER_NAME’?
          DRIVER_PRIME |
          ^~~~~~~~~~~~
          DRIVER_NAME
    make[4]: *** [/usr/src/linux-5.3.18-59.19/scripts/Makefile.build:288: /usr/src/kernel-modules/additions/src/vboxvideo/vbox_drv.o] Error 1
    make[4]: *** Waiting for unfinished jobs....
    make[3]: *** [/usr/src/linux-5.3.18-59.19/Makefile:1675: _module_/usr/src/kernel-modules/additions/src/vboxvideo] Error 2
    make[2]: *** [../../../linux-5.3.18-59.19/Makefile:179: sub-make] Error 2
    make[2]: Leaving directory '/usr/src/linux-5.3.18-59.19-obj/x86_64/default'
    make[1]: *** [/usr/src/kernel-modules/additions/src/vboxvideo/Makefile-footer.gmk:117: vboxvideo] Error 2
    make[1]: Leaving directory '/usr/src/kernel-modules/additions/src/vboxvideo'
    make: *** [Makefile:65: vboxvideo] Error 1
    Mystery 1

    Note that the major part of the version 6.1.26-lp153.2.9.3 of the Leap-15.3 software package virtualbox-guest-source at the time matched the major part of the version 6.1.26r145957 (Qt5.6.2) of VirtualBox. In addition virtualbox-guest-tools 6.1.26-lp153.2.9.3, virtualbox-guest-x11 6.1.26-lp153.2.9.3, virtualbox-kmp-default 6.1.26_k5.3.18_59.19-lp153.2.9.2,
    and virtualbox-kmp-preempt 6.1.26_k5.3.18_59.19-lp153.2.9.2 were installed. And even the version 5.3.18-59.19-default of the running Linux kernel matched the number 5.3.18_59.19 which appeared in the installed versions of virtualbox-kmp-default and virtualbox-kmp-preempt. Yet the output of vboxguestconfig included “virtualbox-guest-source package version doesn't match the version of virtualbox package.”

    Mystery 2

    After executing vboxguestconfig, /var/log/virtualbox.log included

    Code:
    /usr/src/kernel-modules/additions/src/vboxvideo/vbox_drv.c:311:6: error: ‘DRIVER_PRIME’ undeclared here (not in a function); did you mean ‘DRIVER_NAME’?
    , which appears to be evidence of a mismatch between two computer codes. Searching the Internet I found this same sort of message posted by poster IamSteve on https://www.virtualbox.org/ticket/19863. The writing following that posting is not very direct regarding the cause of such a message, but includes a mention of backporting associated with one or two versions of the Linux kernel. So this makes me wonder whether my trouble with a similar message could be due to missing kernel backporting code or not.

    I guess that the command “rcvboxadd setup” might have been a way fix or configure some faulty VirtualBox Guest Additions. This command was reported to have worked well in Leap 15.1 by the poster RustyPuma on https://forums.virtualbox.org/viewtopic.php?t=94359. However, no file named rcvboxadd was found in my Leap-15.3 installation!

    A major result:

    In a hard-drive backup including Leap 15.3 I had VirtualBox 6.1.22 from Oracle Corporation installed, which I think was “inherited” from my Leap-15.2 installation which was upgraded to Leap 15.3. I restored that Leap-15.3 installation onto my computer’s internal hard-disk drive. Then on October 8, 2021 in the directory /opt as a “root” user I entered the command ./uninstall.sh to uninstall the VirtualBox Guest Additions produced from Oracle Corporation’s VirtualBox 6.1.22. By that time I was working with VirtualBox-6.1.24 software packages from openSUSE, Leap-15.3 repositories; and since August 2, 2021 I had VirtualBox 6.1.26 installed in my “host,” Windows-10 operating system. So it makes sense to abandon something to do with VirtualBox 6.1.22 when working with VirtualBox 6.1.24 software packages from Leap-15.3 repositories. But the result of that uninstallation was that I lost the VirtualBox Guest Addition functions of the copying and “pasting” of text between my Windows-10 and Leap-15.3 operating systems; and the folders in my Leap-15.3 directory /media/sf_HostFolder, which corresponded to my Windows-10 directory C:\HostFolder, were invisible in Leap 15.3, while generally visible in Windows 10.---So, more simply, the file- and folder-sharing capabilities of the folder set up in VirtualBox to be shared between the Windows-10 “host” and Leap-15.3 “guest” operating systems were lost. So, with some mystery on my part, these important functions of the VirtualBox Guest Additions were evidently linked with the installation of the VirtualBox Guest Additions from Oracle Corporation’s VirtualBox 6.1.22 and not linked to the VirtualBox Guest Additions included in the Leap-15.3 virtualbox-… software packages or to the VirtualBox Guest Additions which have been reported by Larry Finger to be included in recent Leap Linux kernels. Updating multiple, Leap-15.3, virtualbox software packages to versions including “6.1.26” and updating the default and preempt versions of the Linux kernel from version 5.3.18-lp59.19 to version 5.3.18-lp59.24 appear to have restored the copying and “pasting” functions between the “host” and “guest” operating systems. But the folders in /media/sf_HostFolder were still invisible in Leap 15.3. And on at least one occasion I saw three question marks on a window while “booting” toward the Leap-15.3 graphical login screen.

  2. #2

    Default Re: In VirtualBox 6.1.26 help needed for VirtualBox Guest Additions from Leap 15.3 to function

    A difficulty in entering commands in the terminal computer program LXTerminal in my Leap-15.3 installation was that due to the malfunctioning or non-functioning VirtualBox Guest Additions, the window provided by VirtualBox 6.1.26 for the Lightweight X windows system, version 11 (X11), Desktop Environment (LXDE) in my Leap-15.3 installation was that that the useful part of the LXDE window was often not resizable. A consequence of this problem was that sometimes the lowest line of text in LXTerminal could not be read. Nevertheless I tried a few more things or else collected some information by entering some commands.
    As a regular user:

    Code:
    newbie@linux-hdi0:~> lsmod | grep vbox
    vboxguest             380928  5
    newbie@linux-hdi0:~>
    So vboxsf was not running.

    Code:
    newbie@linux-hdi0:~> su
    Password: 
    linux-hdi0:/home/newbie # systemctl start vboxadd-service
    Warning: The unit file, source configuration file or drop-ins of vboxadd-service.service changed on disk. Run 'systemctl daemon-reload' to reload units.
    linux-hdi0:/home/newbie # systemctl daemon-reload
    linux-hdi0:/home/newbie # systemctl start vboxadd-service
    Warning: The unit file, source configuration file or drop-ins of vboxadd-service.service changed on disk. Run 'systemctl daemon-reload' to reload units.
    linux-hdi0:/home/newbie # 
    
    linux-hdi0:/home/newbie # systemctl enable vboxadd-service
    Earlier after entering the above command I received the response of

    Code:
    Created symlink /etc/systemd/system/multi-user.target.wants/vboxadd-service.service→ /usr/lib/systemd/system/vboxadd-service.service
    Later after entering that same command I received just a prompt in response.

    Code:
    linux-hdi0:/home/newbie # systemctl start vboxadd-service
    Warning: The unit file, source configuration file or drop-ins of vboxadd-service.service changed on disk. Run 'systemctl daemon-reload' to reload units.
    linux-hdi0:/home/newbie # systemctl daemon-reload
    linux-hdi0:/home/newbie # systemctl start vboxadd-service
    Warning: The unit file, source configuration file or drop-ins of vboxadd-service.service changed on disk. Run 'systemctl daemon-reload' to reload units.
    linux-hdi0:/home/newbie # 
    
    linux-hdi0:/home/newbie # VBoxClient --version
    6.1.26_SUSEr145957
    linux-hdi0:/home/newbie #
    Conclusion

    So perhaps with my report of the above data a knowledgeable person can inform me what to do now to restore the resizability of the useful part of the LXDE window and the sharing of files and folders between my Windows “host” and Leap-15.3 “guest” operating systems. Another problem which occurred, recently on October 13, 2021, is that sometimes three question marks could be seen en route to the graphical login screen for Leap 15.3. The general problem for which I would like a solution is how to configure VirtualBox Guest Additions obtained from openSUSE Leap-15.3 repositories or to restore its functions after losing one or more of its functions. Again I could restore all of the functions of the VirtualBox Guest Additions from a hard-drive backup which includes a working Leap-15.3 installation. But for the purpose of accommodating future changes in the computer software in my Leap-15.3 installation, as well as future versions of VirtualBox from Oracle Corporation in my “host,” Windows-10 operating system, I would like to be able to do better than that.

  3. #3
    Join Date
    Jul 2018
    Location
    Loma Linda, Mo
    Posts
    644

    Default Re: In VirtualBox 6.1.26 help needed for VirtualBox Guest Additions from Leap 15.3 to function

    You do not want any of the preempt stuff - it breaks VirtualBox guest (it did mine). Some update that was broken downloaded them - they are for real time Linux.

    virtualbox-kmp-preempt 6.1.26_k5.3.18_59.19-lp153.2.9.2,

    kernel-preempt 5.3.18-59.24.1

    get rid of them and prevent them from reinstalling and validate they are locked.

    Code:
    zypper rm  virtualbox-kmp-preempt  kernel-preempt
    zypper al virtualbox-kmp-preempt  kernel-preempt
    zypper ll
    reboot linux without the preempt kernel that causes the issue.

    I found guest run better when I do not update virtualbox-guest-x11.

    this is my locked guest (I use MATE rather than LXDE as desktop)

    Code:
    VM1:~ # zypper ll
    
    # | Name                   | Type    | Repository
    --+------------------------+---------+-----------
    1 | kernel-preempt         | package | (any)
    2 | virtualbox-guest-x11   | package | (any)
    3 | virtualbox-kmp-preempt | package | (any)
    
    VM1:~ #
    OpenSUSE 15.3 with VirtualBox VM's (XP, 10, 11, Ubuntu MATE 20.04, OpenSUSE 15.3, Tumbleweed)
    Pi4 with OpenSUSE 15.3
    Unix since 1974 (pdp-11, Interdata, AT&T, Tandy, Convergent, Sun, IBM, NCR, and HP)
    Linux since 1995 (Mandrake, Fedora, CentOS, OpenSUSE)

  4. #4

    Default Re: In VirtualBox 6.1.26 help needed for VirtualBox Guest Additions from Leap 15.3 to function

    A correction: My reference for Larry Finger mentioning that in effect the VirtualBox Guest Additions are included in a recent Linux kernel from openSUSE should have been https://bugzilla.opensuse.org/show_bug.cgi?id=1174048 on the Internet instead of https://bugzilla.opensuse.org/show_bug.cgi?id=1187011. Sorry, I made that error. Also I should have had a “III.” before my word “Conclusion” earlier in this “thread” of postings.

    Thank you, poster larryr, for kindly taking some time to post some comments here. Unfortunately removing the preempt software packages from my present Leap-15.3 installation did not eliminate my problems with that installation. Given your comments concerning especially the preempt version of the Linux kernel causing you trouble in probably your Leap-15.3 installation, I think I should restore my Leap-15.3 Virtual “Machine” back to its working state with the preempt and default versions of the Linux kernel 5.3.18-59.19.1 from my hard-disk-drive backup written during October 7-8. 2021. Then after that I should try following your advice to remove the preempt software packages from my working Leap-15.3 installation and putting “locks” on those software packages and virtualbox-guest-x11 to prevent those software packages from being installed or updated in the future. I expect the restoration of my working Leap-15.3 installation from my hard-disk-drive backup to take about nine hours of time.

    Concerning the file rcvboxadd, based on at least https://www.virtualbox.org/wiki/LinuxAdditionsDebug I am now supposing that it might have appeared in a Linux “guest” Virtual “Machine” after installing VirtualBox Guest Additions from Oracle Corporation’s VirtualBox’s executable file VBoxLinuxAdditions.run rather than via VirtualBox Guest Additions obtained through openSUSE, Leap-15.3 repositories. So when I do not have VirtualBox Guest Additions installed by executing Oracle Corporation’s executable file VBoxLinuxAdditions.run, this hypothetical explanation would be consistent with me not finding the file rcvboxadd in my Leap-15.3 installation. If a future problem would arise with VirtualBox Guest Additions obtained through openSUSE repositories, rather than via their production by executing Oracle Corporation’s VirtualBox file VBoxLinuxAdditions.run, I am still interested in obtaining a possible Linux command to restore or reconfigure VirtualBox Guest Additions back to a working state.

  5. #5
    Join Date
    Mar 2011
    Location
    Sauerland
    Posts
    6,624

    Default AW: In VirtualBox 6.1.26 help needed for VirtualBox Guest Additions from Leap 15.3 to function

    Post:
    Code:
    zypper se -si kernel virtualbox
    Code:
    uname -a
    Your Text is not easy to read for me, please use more often the Return key.
    Last edited by Sauerland; 14-Oct-2021 at 12:46.

  6. #6
    Join Date
    Jul 2018
    Location
    Loma Linda, Mo
    Posts
    644

    Default Re: In VirtualBox 6.1.26 help needed for VirtualBox Guest Additions from Leap 15.3 to function

    If you have the Oracle VB extensions in 15.3 - I think they are in /opt

    I did that once by mistake and had to uninstall VB and all the rpm's with it.
    I think there was an uninstall script in the /opt folder as well.

    If you install OpenSUSE VirtualBox as a linux guest you should get a virtualbox-kmp-default for every kernel on your system - I never have to add guest additions to linux guest - just Windows.
    OpenSUSE 15.3 with VirtualBox VM's (XP, 10, 11, Ubuntu MATE 20.04, OpenSUSE 15.3, Tumbleweed)
    Pi4 with OpenSUSE 15.3
    Unix since 1974 (pdp-11, Interdata, AT&T, Tandy, Convergent, Sun, IBM, NCR, and HP)
    Linux since 1995 (Mandrake, Fedora, CentOS, OpenSUSE)

  7. #7

    Default Re: In VirtualBox 6.1.26 help needed for VirtualBox Guest Additions from Leap 15.3 to function

    Correction: Looking at my notes from past restorations of my Leap-15.3 installations, including their /home directories, it took about six and two-thirds hours instead of nine hours for me to extract about a 90- to 93-gigabyte, Leap-15.3 virtual disk image (.vdi) file from a previously written hard-disk-drive backup. Sorry, I made that error twice or once in this “thread” of postings.

    I think the VirtualBox Guest Additions kernel modules may be some .ko files contained in the Leap-15.3 software package virtualbox-kmp-default. Based on the version number of that package it appears that it has taken some time for Leap-15.3 developers to “catch up” with the latest released versions of both VirtualBox from Oracle Corporation and the Linux kernel from Leap-15.3 repositories. As for the VirtualBox Guest Additions, which according to Larry Finger are included in the Linux kernel (https://bugzilla.opensuse.org/show_bug.cgi?id=1174048 on the Internet) obtained from Leap-15.3 repositories, I have not studied the source code in the Leap-15.3 software package kernel-source-default to see whether the versions of VirtualBox Guest Additions included in a Linux kernel obtained from a Leap-15.3 repository are designed to match or not the installed version of VirtualBox installed in the “host” operating system and the Linux kernel in the Leap-15.3 “guest” operating system. But perhaps someone already knows whether or not the VirtualBox Guest Additions included in a Linux kernel obtained through Leap-15.3 repositories is designed to match the versions of both A) VirtualBox from Oracle Corporation that one is using and B) the Linux kernel in which VirtualBox Guest Additions are included and can testify to that matter here. And in my case I wonder if the version of VirtualBox in the Linux kernel came from /opt/VBoxGuestAdditions-6.1.22 or VirtualBox 6.1.26 installed in my Windows-10 “host” operating system, each of which probably came from Oracle Corporation.

    On October 8, 2021 I uninstalled the VirtualBox Guest Additions from Oracle Corporation’s VirtualBox via as a “root” user the command
    Code:
    ./uninstall.sh
    in the directory /opt/VBoxGuestAdditions-6.1.22. But after “rebooting” into Leap 15.3 with the Linux kernel 5.3.18-59.19-preempt the result was the loss of the copying and “pasting” of text between my Windows-10 “host” and Leap-15.3 “guest” operating systems and that the folders in the folder shared between Windows 10 and Leap 15.3 were invisible in Leap 15.3. Based on larryr’s writing in this “thread” of postings those losses could perhaps be attributed to the use of the Linux kernel 5.3.18-59.19-preempt. Another possibility is that the good functioning of the VirtualBox Guest Additions somehow depended on the VirtualBox Guest Additions 6.1.22 I installed from Oracle Corporation’s VirtualBox. Lately I have instead been operating with the VirtualBox Guest Additions 6.1.22 still installed while using VirtualBox 6.1.26 from Oracle Corporation and updating the Linux kernel from Leap 15.3 repositories.

    In my Leap-15.1 “guest” operating system with VirtualBox 6.1.10 in my Windows-10 “host” operating system on July 16, 2020 I lost the sharing of folders within the folder shared by my Windows-10 “host” and Leap “guest” operating systems after updating virtualbox-guest-x11, virtualbox-guest-tools, and virtualbox-kmp-default from versions 6.0.18.… to versions 6.0.22…. And this function was not restored by downgrading those three software packages back to versions 6.0.18…! And I don’t recall preempt versions of Linux kernels being available from Leap-15.1 repositories on July 16, 2020. My temporary solution during July 16-17, 2020 was to return to a working Leap-15.1 installation by means of a hard-disk-drive backup written on July 1-2, 2020.

    In my Leap-15.3 installation I have been experimenting with a fairly conservative approach in the hope of obtaining at least temporarily working VirtualBox Guest Additions, as outlined below.

    On October 16, 2021 I wrote a hard-disk-drive backup in which the VirtualBox Guest Additions work with

    a) protections against updating away from versions 6.1.24… of the software packages virtualbox-guest-x11, virtualbox-guest-tools, virtualbox-guest-source, and virtualbox-kmp-default;

    b) all preempt software packages have been uninstalled and kernel-preempt is listed in YaST2 (Yet another Setup Tool 2) as “taboo,” meaning to prevent kernel-preempt from being installed;

    c) I kept VirtualBox Guest Additions 6.1.22 from Oracle Corporation installed in Leap 15.3 and VirtualBox 6.1.26 installed in Windows 10;

    d) version 5.3.18-59.27.1 of kernel-default, kernel-devel, kernel-extra, and kernel-optional is installed, without protection against any of those software packages being updated.

    e) I think I probably inherited from a Leap-15.3 repository probably a prohibition against installing the software package Mesa-dri-nouveau.

    f) And since I found that on October 4, 2021 I had three question marks appear before reaching the Lightweight X Windows System, version 11 (X11), Desktop Environment (LXDE) in Leap 15.3 after on October 1, 2021 installing updates to probably at least the software packages

    ca-certificates-mozilla,
    kpartx,
    libmpath0,
    libpq5,
    multipath-tools,
    openSUSE-build-key,
    openSUSE-release,
    openSUSE-release-dvd, and
    openSUSE-release-ftp,

    I "locked" all of those software packages against being updated. In addition, in response to the “root”-user command
    Code:
    zypper locks
    the product Leap was listed as locked. Perhaps that item will disappear from that list of locked products and packages after locks are removed from the software packages

    openSUSE-build-key,
    openSUSE-release,
    openSUSE-release-dvd,
    openSUSE-release-ftp,

    and/or after a possible future software conflict permission is given to install some Leap-15.3 software package.

    Let me define this working state of Leap-15.3 installations as “October 16, 2021 Backup.” After writing that backup I was free to experiment by installing updates to that working installation. My first experiment was to update ca-certificates-mozilla, a software package which, based on its name, I expected to have nothing to do with the functions of VirtualBox Guest Additions in my Leap-15.3 installation. But the disappointing result was that after updating ca-certificates-mozilla in October 16, Backup, I lost the sharing of folders in the folder shared between my Windows-10 “host” and Leap-15.3 “guest” operating systems!

    Thank you, poster Sauerland, for also kindly taking some time to write something in this “thread” of postings. For poster Sauerland during the afternoon of October 16, 2021 in the state October 16, 2021 Backup, including when VirtualBox Guest Additions were working well, after “rebooting” into Leap 15.3 with Oracle Corporation’s VirtualBox 6.1.22 still installed, Linux kernel 5.3.18-59.27.1-default running, and Linux kernel 5.3.18-59.27.1-preempt not installed:

  8. #8

    Default Re: In VirtualBox 6.1.26 help needed for VirtualBox Guest Additions from Leap 15.3 to function

    Code:
    newbie@linux-hdi0:~> su
    Password: 
    linux-hdi0:/home/newbie # zypper se -si kernel virtualbox
    System management is locked by the application with pid 843 (/usr/bin/zypper).
    Close this application before trying again.
    linux-hdi0:/home/newbie # kill -9 843
    linux-hdi0:/home/newbie # zypper se -si kernel virtualbox
    Loading repository data...
    Reading installed packages...
    
    S  | Name                        | Type    | Version                          | Arch   | Repository
    ---+-----------------------------+---------+----------------------------------+--------+-------------------------------------------------------------
    i+ | kernel-default              | package | 5.3.18-59.27.1                   | x86_64 | Update repository with updates from SUSE Linux Enterprise 15
    i+ | kernel-default              | package | 5.3.18-59.19.1                   | x86_64 | Update repository with updates from SUSE Linux Enterprise 15
    i+ | kernel-default              | package | 5.3.18-59.16.1                   | x86_64 | Update repository with updates from SUSE Linux Enterprise 15
    i+ | kernel-default              | package | 5.3.18-59.10.1                   | x86_64 | Update repository with updates from SUSE Linux Enterprise 15
    i+ | kernel-default              | package | 5.3.18-57.3                      | x86_64 | Main Repository
    i+ | kernel-default              | package | 5.3.18-57.3                      | x86_64 | openSUSE-Leap-15.3-1
    i+ | kernel-default-devel        | package | 5.3.18-59.27.1                   | x86_64 | Update repository with updates from SUSE Linux Enterprise 15
    i+ | kernel-default-devel        | package | 5.3.18-59.19.1                   | x86_64 | Update repository with updates from SUSE Linux Enterprise 15
    i+ | kernel-default-devel        | package | 5.3.18-59.16.1                   | x86_64 | Update repository with updates from SUSE Linux Enterprise 15
    i+ | kernel-default-extra        | package | 5.3.18-59.27.1                   | x86_64 | Update repository with updates from SUSE Linux Enterprise 15
    i+ | kernel-default-extra        | package | 5.3.18-59.19.1                   | x86_64 | Update repository with updates from SUSE Linux Enterprise 15
    i+ | kernel-default-extra        | package | 5.3.18-59.16.1                   | x86_64 | Update repository with updates from SUSE Linux Enterprise 15
    i+ | kernel-default-extra        | package | 5.3.18-59.10.1                   | x86_64 | Update repository with updates from SUSE Linux Enterprise 15
    i+ | kernel-default-optional     | package | 5.3.18-59.27.1                   | x86_64 | Update repository with updates from SUSE Linux Enterprise 15
    i+ | kernel-default-optional     | package | 5.3.18-59.19.1                   | x86_64 | Update repository with updates from SUSE Linux Enterprise 15
    i+ | kernel-default-optional     | package | 5.3.18-59.16.1                   | x86_64 | Update repository with updates from SUSE Linux Enterprise 15
    i+ | kernel-devel                | package | 5.3.18-59.10.1                   | noarch | (System Packages)
    i+ | kernel-devel                | package | 5.3.18-59.27.1                   | noarch | Update repository with updates from SUSE Linux Enterprise 15
    i+ | kernel-devel                | package | 5.3.18-59.19.1                   | noarch | Update repository with updates from SUSE Linux Enterprise 15
    i+ | kernel-devel                | package | 5.3.18-59.16.1                   | noarch | Update repository with updates from SUSE Linux Enterprise 15
    i+ | kernel-firmware-all         | package | 20210208-2.4                     | noarch | Main Repository
    i+ | kernel-firmware-all         | package | 20210208-2.4                     | noarch | openSUSE-Leap-15.3-1
    i+ | kernel-firmware-amdgpu      | package | 20210208-2.4                     | noarch | Main Repository
    i+ | kernel-firmware-amdgpu      | package | 20210208-2.4                     | noarch | openSUSE-Leap-15.3-1
    i+ | kernel-firmware-ath10k      | package | 20210208-2.4                     | noarch | Main Repository
    i+ | kernel-firmware-ath10k      | package | 20210208-2.4                     | noarch | openSUSE-Leap-15.3-1
    i+ | kernel-firmware-ath11k      | package | 20210208-2.4                     | noarch | Main Repository
    i+ | kernel-firmware-ath11k      | package | 20210208-2.4                     | noarch | openSUSE-Leap-15.3-1
    i+ | kernel-firmware-atheros     | package | 20210208-2.4                     | noarch | Main Repository
    i+ | kernel-firmware-atheros     | package | 20210208-2.4                     | noarch | openSUSE-Leap-15.3-1
    i+ | kernel-firmware-bluetooth   | package | 20210208-2.4                     | noarch | Main Repository
    i+ | kernel-firmware-bluetooth   | package | 20210208-2.4                     | noarch | openSUSE-Leap-15.3-1
    i+ | kernel-firmware-bnx2        | package | 20210208-2.4                     | noarch | Main Repository
    i+ | kernel-firmware-bnx2        | package | 20210208-2.4                     | noarch | openSUSE-Leap-15.3-1
    i+ | kernel-firmware-brcm        | package | 20210208-2.4                     | noarch | Main Repository
    i+ | kernel-firmware-brcm        | package | 20210208-2.4                     | noarch | openSUSE-Leap-15.3-1
    i+ | kernel-firmware-chelsio     | package | 20210208-2.4                     | noarch | Main Repository
    i+ | kernel-firmware-chelsio     | package | 20210208-2.4                     | noarch | openSUSE-Leap-15.3-1
    i+ | kernel-firmware-dpaa2       | package | 20210208-2.4                     | noarch | Main Repository
    i+ | kernel-firmware-dpaa2       | package | 20210208-2.4                     | noarch | openSUSE-Leap-15.3-1
    i+ | kernel-firmware-i915        | package | 20210208-2.4                     | noarch | Main Repository
    i+ | kernel-firmware-i915        | package | 20210208-2.4                     | noarch | openSUSE-Leap-15.3-1
    i+ | kernel-firmware-intel       | package | 20210208-2.4                     | noarch | Main Repository
    i+ | kernel-firmware-intel       | package | 20210208-2.4                     | noarch | openSUSE-Leap-15.3-1
    i+ | kernel-firmware-iwlwifi     | package | 20210208-2.4                     | noarch | Main Repository
    i+ | kernel-firmware-iwlwifi     | package | 20210208-2.4                     | noarch | openSUSE-Leap-15.3-1
    i+ | kernel-firmware-liquidio    | package | 20210208-2.4                     | noarch | Main Repository
    i+ | kernel-firmware-liquidio    | package | 20210208-2.4                     | noarch | openSUSE-Leap-15.3-1
    i+ | kernel-firmware-marvell     | package | 20210208-2.4                     | noarch | Main Repository
    i+ | kernel-firmware-marvell     | package | 20210208-2.4                     | noarch | openSUSE-Leap-15.3-1
    i+ | kernel-firmware-media       | package | 20210208-2.4                     | noarch | Main Repository
    i+ | kernel-firmware-media       | package | 20210208-2.4                     | noarch | openSUSE-Leap-15.3-1
    i+ | kernel-firmware-mediatek    | package | 20210208-2.4                     | noarch | Main Repository
    i+ | kernel-firmware-mediatek    | package | 20210208-2.4                     | noarch | openSUSE-Leap-15.3-1
    i+ | kernel-firmware-mellanox    | package | 20210208-2.4                     | noarch | Main Repository
    i+ | kernel-firmware-mellanox    | package | 20210208-2.4                     | noarch | openSUSE-Leap-15.3-1
    i+ | kernel-firmware-mwifiex     | package | 20210208-2.4                     | noarch | Main Repository
    i+ | kernel-firmware-mwifiex     | package | 20210208-2.4                     | noarch | openSUSE-Leap-15.3-1
    i+ | kernel-firmware-network     | package | 20210208-2.4                     | noarch | Main Repository
    i+ | kernel-firmware-network     | package | 20210208-2.4                     | noarch | openSUSE-Leap-15.3-1
    i+ | kernel-firmware-nfp         | package | 20210208-2.4                     | noarch | Main Repository
    i+ | kernel-firmware-nfp         | package | 20210208-2.4                     | noarch | openSUSE-Leap-15.3-1
    i+ | kernel-firmware-nvidia      | package | 20210208-2.4                     | noarch | Main Repository
    i+ | kernel-firmware-nvidia      | package | 20210208-2.4                     | noarch | openSUSE-Leap-15.3-1
    i+ | kernel-firmware-platform    | package | 20210208-2.4                     | noarch | Main Repository
    i+ | kernel-firmware-platform    | package | 20210208-2.4                     | noarch | openSUSE-Leap-15.3-1
    i+ | kernel-firmware-prestera    | package | 20210208-2.4                     | noarch | Main Repository
    i+ | kernel-firmware-prestera    | package | 20210208-2.4                     | noarch | openSUSE-Leap-15.3-1
    i+ | kernel-firmware-qlogic      | package | 20210208-2.4                     | noarch | Main Repository
    i+ | kernel-firmware-qlogic      | package | 20210208-2.4                     | noarch | openSUSE-Leap-15.3-1
    i+ | kernel-firmware-radeon      | package | 20210208-2.4                     | noarch | Main Repository
    i+ | kernel-firmware-radeon      | package | 20210208-2.4                     | noarch | openSUSE-Leap-15.3-1
    i+ | kernel-firmware-realtek     | package | 20210208-2.4                     | noarch | Main Repository
    i+ | kernel-firmware-realtek     | package | 20210208-2.4                     | noarch | openSUSE-Leap-15.3-1
    i+ | kernel-firmware-serial      | package | 20210208-2.4                     | noarch | Main Repository
    i+ | kernel-firmware-serial      | package | 20210208-2.4                     | noarch | openSUSE-Leap-15.3-1
    i+ | kernel-firmware-sound       | package | 20210208-2.4                     | noarch | Main Repository
    i+ | kernel-firmware-sound       | package | 20210208-2.4                     | noarch | openSUSE-Leap-15.3-1
    i+ | kernel-firmware-ti          | package | 20210208-2.4                     | noarch | Main Repository
    i+ | kernel-firmware-ti          | package | 20210208-2.4                     | noarch | openSUSE-Leap-15.3-1
    i+ | kernel-firmware-ueagle      | package | 20210208-2.4                     | noarch | Main Repository
    i+ | kernel-firmware-ueagle      | package | 20210208-2.4                     | noarch | openSUSE-Leap-15.3-1
    i+ | kernel-firmware-usb-network | package | 20210208-2.4                     | noarch | Main Repository
    i+ | kernel-firmware-usb-network | package | 20210208-2.4                     | noarch | openSUSE-Leap-15.3-1
    i+ | kernel-macros               | package | 5.3.18-59.27.1                   | noarch | Update repository with updates from SUSE Linux Enterprise 15
    i+ | kernel-source               | package | 5.3.18-59.27.1                   | noarch | Update repository with updates from SUSE Linux Enterprise 15
    i+ | kernel-source               | package | 5.3.18-59.19.1                   | noarch | Update repository with updates from SUSE Linux Enterprise 15
    i+ | kernel-source               | package | 5.3.18-59.16.1                   | noarch | Update repository with updates from SUSE Linux Enterprise 15
    i+ | purge-kernels-service       | package | 0-8.3.1                          | noarch | Update repository with updates from SUSE Linux Enterprise 15
    i+ | texlive-l3kernel            | package | 2017.133.svn44483-5.18           | noarch | Main Repository
    i+ | texlive-l3kernel-doc        | package | 2017.133.svn44483-5.18           | noarch | Main Repository
    il | virtualbox-guest-source     | package | 6.1.24-lp153.2.6.1               | noarch | Main Update Repository
    il | virtualbox-guest-tools      | package | 6.1.24-lp153.2.6.1               | x86_64 | Main Update Repository
    il | virtualbox-guest-x11        | package | 6.1.24-lp153.2.6.1               | x86_64 | Main Update Repository
    il | virtualbox-kmp-default      | package | 6.1.24_k5.3.18_59.16-lp153.2.6.1 | x86_64 | Main Update Repository
    il | virtualbox-kmp-default      | package | 6.1.22_k5.3.18_59.5-lp153.2.3.2  | x86_64 | Main Update Repository
    il | virtualbox-kmp-default      | package | 6.1.20_k5.3.18_57-lp153.1.2      | x86_64 | Main Repository
    il | virtualbox-kmp-default      | package | 6.1.20_k5.3.18_57-lp153.1.2      | x86_64 | openSUSE-Leap-15.3-1
    
    
    For an extended search including not yet activated remote resources you may run
    'zypper search-packages' at any time.
    Do you want to run 'zypper search-packages' now? [yes/no/always/never] (no): yes
    
    Could not parse the options: ambiguous option: -si
    Could not search for the package: SocketError: Failed to open TCP connection to scc.suse.com:443 (getaddrinfo: Name or service not known)
    Could not search for the package: SocketError: Failed to open TCP connection to scc.suse.com:443 (getaddrinfo: Name or service not known)
    Could not search for the package: SocketError: Failed to open TCP connection to scc.suse.com:443 (getaddrinfo: Name or service not known)
    No package found
    
    linux-hdi0:/home/newbie # uname -a
    Linux linux-hdi0 5.3.18-59.27-default #1 SMP Tue Oct 5 10:00:40 UTC 2021 (7df2404) x86_64 x86_64 x86_64 GNU/Linux
    linux-hdi0:/home/newbie #

  9. #9

    Default Re: In VirtualBox 6.1.26 help needed for VirtualBox Guest Additions from Leap 15.3 to function

    After rebooting, installing the Leap-15.3 software package ca-certificates-mozilla, and finding folder sharing lost within the folder shared by Windows 10 and Leap 15.3 on the evening of October 16, 2021:

    Code:
    linux-hdi0:/home/newbie # zypper refresh
    Repository 'Packman Repository' is up to date.                                  
    Repository 'libdvdcss repository' is up to date.                                
    Repository 'openSUSE-Leap-15.3-1' is up to date.                                
    Repository 'Update repository of openSUSE Backports' is up to date.             
    Repository 'Non-OSS Repository' is up to date.                                  
    Repository 'Main Repository' is up to date.                                     
    Repository 'Update repository with updates from SUSE Linux Enterprise 15' is up
    to date.
                                                                                    
    Repository 'Main Update Repository' is up to date.                              
    Repository 'Update Repository (Non-Oss)' is up to date.                         
    All repositories have been refreshed.
    linux-hdi0:/home/newbie # zypper se -si kernel virtualbox
    Loading repository data...
    Reading installed packages...
    
    S  | Name                        | Type    | Version                          | Arch   | Repository
    ---+-----------------------------+---------+----------------------------------+--------+-------------------------------------------------------------
    i+ | kernel-default              | package | 5.3.18-59.27.1                   | x86_64 | Update repository with updates from SUSE Linux Enterprise 15
    i+ | kernel-default              | package | 5.3.18-59.19.1                   | x86_64 | Update repository with updates from SUSE Linux Enterprise 15
    i+ | kernel-default              | package | 5.3.18-59.16.1                   | x86_64 | Update repository with updates from SUSE Linux Enterprise 15
    i+ | kernel-default              | package | 5.3.18-59.10.1                   | x86_64 | Update repository with updates from SUSE Linux Enterprise 15
    i+ | kernel-default-devel        | package | 5.3.18-59.27.1                   | x86_64 | Update repository with updates from SUSE Linux Enterprise 15
    i+ | kernel-default-devel        | package | 5.3.18-59.19.1                   | x86_64 | Update repository with updates from SUSE Linux Enterprise 15
    i+ | kernel-default-devel        | package | 5.3.18-59.16.1                   | x86_64 | Update repository with updates from SUSE Linux Enterprise 15
    i+ | kernel-default-extra        | package | 5.3.18-59.27.1                   | x86_64 | Update repository with updates from SUSE Linux Enterprise 15
    i+ | kernel-default-extra        | package | 5.3.18-59.19.1                   | x86_64 | Update repository with updates from SUSE Linux Enterprise 15
    i+ | kernel-default-extra        | package | 5.3.18-59.16.1                   | x86_64 | Update repository with updates from SUSE Linux Enterprise 15
    i+ | kernel-default-extra        | package | 5.3.18-59.10.1                   | x86_64 | Update repository with updates from SUSE Linux Enterprise 15
    i+ | kernel-default-optional     | package | 5.3.18-59.27.1                   | x86_64 | Update repository with updates from SUSE Linux Enterprise 15
    i+ | kernel-default-optional     | package | 5.3.18-59.19.1                   | x86_64 | Update repository with updates from SUSE Linux Enterprise 15
    i+ | kernel-default-optional     | package | 5.3.18-59.16.1                   | x86_64 | Update repository with updates from SUSE Linux Enterprise 15
    i+ | kernel-devel                | package | 5.3.18-59.10.1                   | noarch | (System Packages)
    i+ | kernel-devel                | package | 5.3.18-59.27.1                   | noarch | Update repository with updates from SUSE Linux Enterprise 15
    i+ | kernel-devel                | package | 5.3.18-59.19.1                   | noarch | Update repository with updates from SUSE Linux Enterprise 15
    i+ | kernel-devel                | package | 5.3.18-59.16.1                   | noarch | Update repository with updates from SUSE Linux Enterprise 15
    i+ | kernel-firmware-all         | package | 20210208-2.4                     | noarch | Main Repository
    i+ | kernel-firmware-all         | package | 20210208-2.4                     | noarch | openSUSE-Leap-15.3-1
    i+ | kernel-firmware-amdgpu      | package | 20210208-2.4                     | noarch | Main Repository
    i+ | kernel-firmware-amdgpu      | package | 20210208-2.4                     | noarch | openSUSE-Leap-15.3-1
    i+ | kernel-firmware-ath10k      | package | 20210208-2.4                     | noarch | Main Repository
    i+ | kernel-firmware-ath10k      | package | 20210208-2.4                     | noarch | openSUSE-Leap-15.3-1
    i+ | kernel-firmware-ath11k      | package | 20210208-2.4                     | noarch | Main Repository
    i+ | kernel-firmware-ath11k      | package | 20210208-2.4                     | noarch | openSUSE-Leap-15.3-1
    i+ | kernel-firmware-atheros     | package | 20210208-2.4                     | noarch | Main Repository
    i+ | kernel-firmware-atheros     | package | 20210208-2.4                     | noarch | openSUSE-Leap-15.3-1
    i+ | kernel-firmware-bluetooth   | package | 20210208-2.4                     | noarch | Main Repository
    i+ | kernel-firmware-bluetooth   | package | 20210208-2.4                     | noarch | openSUSE-Leap-15.3-1
    i+ | kernel-firmware-bnx2        | package | 20210208-2.4                     | noarch | Main Repository
    i+ | kernel-firmware-bnx2        | package | 20210208-2.4                     | noarch | openSUSE-Leap-15.3-1
    i+ | kernel-firmware-brcm        | package | 20210208-2.4                     | noarch | Main Repository
    i+ | kernel-firmware-brcm        | package | 20210208-2.4                     | noarch | openSUSE-Leap-15.3-1
    i+ | kernel-firmware-chelsio     | package | 20210208-2.4                     | noarch | Main Repository
    i+ | kernel-firmware-chelsio     | package | 20210208-2.4                     | noarch | openSUSE-Leap-15.3-1
    i+ | kernel-firmware-dpaa2       | package | 20210208-2.4                     | noarch | Main Repository
    i+ | kernel-firmware-dpaa2       | package | 20210208-2.4                     | noarch | openSUSE-Leap-15.3-1
    i+ | kernel-firmware-i915        | package | 20210208-2.4                     | noarch | Main Repository
    i+ | kernel-firmware-i915        | package | 20210208-2.4                     | noarch | openSUSE-Leap-15.3-1
    i+ | kernel-firmware-intel       | package | 20210208-2.4                     | noarch | Main Repository
    i+ | kernel-firmware-intel       | package | 20210208-2.4                     | noarch | openSUSE-Leap-15.3-1
    i+ | kernel-firmware-iwlwifi     | package | 20210208-2.4                     | noarch | Main Repository
    i+ | kernel-firmware-iwlwifi     | package | 20210208-2.4                     | noarch | openSUSE-Leap-15.3-1
    i+ | kernel-firmware-liquidio    | package | 20210208-2.4                     | noarch | Main Repository
    i+ | kernel-firmware-liquidio    | package | 20210208-2.4                     | noarch | openSUSE-Leap-15.3-1
    i+ | kernel-firmware-marvell     | package | 20210208-2.4                     | noarch | Main Repository
    i+ | kernel-firmware-marvell     | package | 20210208-2.4                     | noarch | openSUSE-Leap-15.3-1
    i+ | kernel-firmware-media       | package | 20210208-2.4                     | noarch | Main Repository
    i+ | kernel-firmware-media       | package | 20210208-2.4                     | noarch | openSUSE-Leap-15.3-1
    i+ | kernel-firmware-mediatek    | package | 20210208-2.4                     | noarch | Main Repository
    i+ | kernel-firmware-mediatek    | package | 20210208-2.4                     | noarch | openSUSE-Leap-15.3-1
    i+ | kernel-firmware-mellanox    | package | 20210208-2.4                     | noarch | Main Repository
    i+ | kernel-firmware-mellanox    | package | 20210208-2.4                     | noarch | openSUSE-Leap-15.3-1
    i+ | kernel-firmware-mwifiex     | package | 20210208-2.4                     | noarch | Main Repository
    i+ | kernel-firmware-mwifiex     | package | 20210208-2.4                     | noarch | openSUSE-Leap-15.3-1
    i+ | kernel-firmware-network     | package | 20210208-2.4                     | noarch | Main Repository
    i+ | kernel-firmware-network     | package | 20210208-2.4                     | noarch | openSUSE-Leap-15.3-1
    i+ | kernel-firmware-nfp         | package | 20210208-2.4                     | noarch | Main Repository
    i+ | kernel-firmware-nfp         | package | 20210208-2.4                     | noarch | openSUSE-Leap-15.3-1
    i+ | kernel-firmware-nvidia      | package | 20210208-2.4                     | noarch | Main Repository
    i+ | kernel-firmware-nvidia      | package | 20210208-2.4                     | noarch | openSUSE-Leap-15.3-1
    i+ | kernel-firmware-platform    | package | 20210208-2.4                     | noarch | Main Repository
    i+ | kernel-firmware-platform    | package | 20210208-2.4                     | noarch | openSUSE-Leap-15.3-1
    i+ | kernel-firmware-prestera    | package | 20210208-2.4                     | noarch | Main Repository
    i+ | kernel-firmware-prestera    | package | 20210208-2.4                     | noarch | openSUSE-Leap-15.3-1
    i+ | kernel-firmware-qlogic      | package | 20210208-2.4                     | noarch | Main Repository
    i+ | kernel-firmware-qlogic      | package | 20210208-2.4                     | noarch | openSUSE-Leap-15.3-1
    i+ | kernel-firmware-radeon      | package | 20210208-2.4                     | noarch | Main Repository
    i+ | kernel-firmware-radeon      | package | 20210208-2.4                     | noarch | openSUSE-Leap-15.3-1
    i+ | kernel-firmware-realtek     | package | 20210208-2.4                     | noarch | Main Repository
    i+ | kernel-firmware-realtek     | package | 20210208-2.4                     | noarch | openSUSE-Leap-15.3-1
    i+ | kernel-firmware-serial      | package | 20210208-2.4                     | noarch | Main Repository
    i+ | kernel-firmware-serial      | package | 20210208-2.4                     | noarch | openSUSE-Leap-15.3-1
    i+ | kernel-firmware-sound       | package | 20210208-2.4                     | noarch | Main Repository
    i+ | kernel-firmware-sound       | package | 20210208-2.4                     | noarch | openSUSE-Leap-15.3-1
    i+ | kernel-firmware-ti          | package | 20210208-2.4                     | noarch | Main Repository
    i+ | kernel-firmware-ti          | package | 20210208-2.4                     | noarch | openSUSE-Leap-15.3-1
    i+ | kernel-firmware-ueagle      | package | 20210208-2.4                     | noarch | Main Repository
    i+ | kernel-firmware-ueagle      | package | 20210208-2.4                     | noarch | openSUSE-Leap-15.3-1
    i+ | kernel-firmware-usb-network | package | 20210208-2.4                     | noarch | Main Repository
    i+ | kernel-firmware-usb-network | package | 20210208-2.4                     | noarch | openSUSE-Leap-15.3-1
    i+ | kernel-macros               | package | 5.3.18-59.27.1                   | noarch | Update repository with updates from SUSE Linux Enterprise 15
    i+ | kernel-source               | package | 5.3.18-59.27.1                   | noarch | Update repository with updates from SUSE Linux Enterprise 15
    i+ | kernel-source               | package | 5.3.18-59.19.1                   | noarch | Update repository with updates from SUSE Linux Enterprise 15
    i+ | kernel-source               | package | 5.3.18-59.16.1                   | noarch | Update repository with updates from SUSE Linux Enterprise 15
    i+ | purge-kernels-service       | package | 0-8.3.1                          | noarch | Update repository with updates from SUSE Linux Enterprise 15
    i+ | texlive-l3kernel            | package | 2017.133.svn44483-5.18           | noarch | Main Repository
    i+ | texlive-l3kernel-doc        | package | 2017.133.svn44483-5.18           | noarch | Main Repository
    il | virtualbox-guest-source     | package | 6.1.24-lp153.2.6.1               | noarch | Main Update Repository
    il | virtualbox-guest-tools      | package | 6.1.24-lp153.2.6.1               | x86_64 | Main Update Repository
    il | virtualbox-guest-x11        | package | 6.1.24-lp153.2.6.1               | x86_64 | Main Update Repository
    il | virtualbox-kmp-default      | package | 6.1.24_k5.3.18_59.16-lp153.2.6.1 | x86_64 | Main Update Repository
    il | virtualbox-kmp-default      | package | 6.1.22_k5.3.18_59.5-lp153.2.3.2  | x86_64 | Main Update Repository
    il | virtualbox-kmp-default      | package | 6.1.20_k5.3.18_57-lp153.1.2      | x86_64 | Main Repository
    il | virtualbox-kmp-default      | package | 6.1.20_k5.3.18_57-lp153.1.2      | x86_64 | openSUSE-Leap-15.3-1
    
    
    For an extended search including not yet activated remote resources you may run
    'zypper search-packages' at any time.
    Do you want to run 'zypper search-packages' now? [yes/no/always/never] (no): no
    
    linux-hdi0:/home/newbie # uname -a
    Linux linux-hdi0.site 5.3.18-59.27-default #1 SMP Tue Oct 5 10:00:40 UTC 2021 (7df2404) x86_64 x86_64 x86_64 GNU/Linux
    linux-hdi0:/home/newbie # 
    
    linux-hdi0:/home/newbie # zypper locks
    
    #  | Name                           | Type    | Repository
    ---+--------------------------------+---------+-----------
    1  | Leap                           | product | (any)
    2  | Mesa-dri-nouveau               | package | (any)
    3  | kernel-preempt                 | package | (any)
    4  | kernel-preempt-devel           | package | (any)
    5  | kernel-preempt-extra           | package | (any)
    6  | kernel-preempt-livepatch-devel | package | (any)
    7  | kernel-preempt-optional        | package | (any)
    8  | kpartx                         | package | (any)
    9  | libmpath0                      | package | (any)
    10 | libpq5                         | package | (any)
    11 | multipath-tools                | package | (any)
    12 | openSUSE-build-key             | package | (any)
    13 | openSUSE-release               | package | (any)
    14 | openSUSE-release-dvd           | package | (any)
    15 | openSUSE-release-ftp           | package | (any)
    16 | virtualbox-guest-source        | package | (any)
    17 | virtualbox-guest-tools         | package | (any)
    18 | virtualbox-guest-x11           | package | (any)
    19 | virtualbox-kmp-default         | package | (any)
    20 | virtualbox-kmp-preempt         | package | (any)
    
    linux-hdi0:/home/newbie #
    Assuming that the installation of ca-certificates-mozilla had nothing to do with the functions of VirtualBox Guest Additions, I wonder if the process of updating Leap 15.3 via the “root”-user command
    Code:
    zypper update ca-certificates-mozilla
    or else just a “rebooting” somehow caused the loss of folder sharing in the folder shared by my Windows-10 “host” and Leap-15.3 “guest” operating systems.

  10. #10

    Default Re: In VirtualBox 6.1.26 help needed for VirtualBox Guest Additions from Leap 15.3 to function

    Thank you, posters larryr and Sauerland, for kindly taking some time to post some writing here.

    The kernel modules provided by virtualbox-kmp-default 6.1.24… are

    vboxdrv.ko,
    vboxguest.ko,
    vboxnetadp.ko,
    vboxnetflt.ko, and
    vboxsf.ko.

    The October 16, 2021 portion of the file \var\log\messages might contain some clues to my trouble of in my Leap-15.3 installation failing to see the folders in my “host,” Windows folder C:\HostFolder shared with my “guest,” Leap-15.3 installation as /media/sf_HostFolder within VirtualBox 6.1.24… And I had a second shared folder: C:\VirtualBox in Windows 10 and /media/sf_VirtualBox in Leap 15.3. During the afternoon of that day, when VirtualBox Guest Additions were working well, \var\log\messages had

    Code:
    2021-10-16T13:07:31.090293-04:00 linux-hdi0 vboxadd-service.sh: VirtualBox Guest Addition service started.
    2021-10-16T13:07:31.331442-04:00 linux-hdi0 kernel: [  128.912888] vboxsf: g_fHostFeatures=0x8000000f g_fSfFeatures=0x1 g_uSfLastFunction=29
    2021-10-16T13:07:31.331471-04:00 linux-hdi0 kernel: [  128.913099] vboxsf: Successfully loaded version 6.1.24_SUSE r145751
    2021-10-16T13:07:31.331477-04:00 linux-hdi0 kernel: [  128.913163] vboxsf: Successfully loaded version 6.1.24_SUSE r145751 on 5.3.18-59.16-default SMP mod_unload modversions  (LINUX_VERSION_CODE=0x50312)
    2021-10-16T13:07:31.360693-04:00 linux-hdi0 kernel: [  128.941010] 17:07:31.353934 automount vbsvcAutomounterMountIt: Successfully mounted 'HostFolder' on '/media/sf_HostFolder'
    2021-10-16T13:07:31.360729-04:00 linux-hdi0 kernel: [  128.943248] 17:07:31.356200 automount vbsvcAutomounterMountIt: Successfully mounted 'VirtualBox' on '/media/sf_VirtualBox'
    But there was a hint there that there might be future trouble with a tainting of the Linux kernel from

    Code:
    2021-10-16T13:06:57.858130-04:00 linux-hdi0 kernel: [   10.278377] vboxguest: module verification failed: signature and/or required key missing - tainting kernel
    2021-10-16T13:06:57.858160-04:00 linux-hdi0 kernel: [   10.422628] vgdrvHeartbeatInit: Setting up heartbeat to trigger every 2000 milliseconds
    2021-10-16T13:06:57.858166-04:00 linux-hdi0 kernel: [   10.423139] input: Unspecified device as /devices/pci0000:00/0000:00:04.0/input/input4
    From my reading of the Internet a tainted kernel is a kernel not supported by the community of, I presume in this case, Leap-15.3 code developers. The above, last-time-stamped line is a mystery for me.

    Code:
    2021-10-16T13:06:57.858169-04:00 linux-hdi0 kernel: [   10.433703] libata version 3.00 loaded.
    . However, there was apparently no apparent immediate trouble in loading the Linux kernel module vboxguest, based on

    Code:
    2021-10-16T13:06:57.858172-04:00 linux-hdi0 kernel: [   10.434605] vboxguest: Successfully loaded version 6.1.24_SUSE r145751
    2021-10-16T13:06:57.858175-04:00 linux-hdi0 kernel: [   10.434703] vboxguest: misc device minor 56, IRQ 20, I/O port d020, MMIO at 00000000f0400000 (size 0x400000)
    2021-10-16T13:06:57.858189-04:00 linux-hdi0 kernel: [   10.434707] vboxguest: Successfully loaded version 6.1.24_SUSE r145751 (interface 0x00010004)
    I presume that any change to the running Linux kernel would not be manifested until a later “boot” into Leap 15.3 using that tainted Linux kernel.

    Then beginning at about 2:34 p.m., Eastern Daylight Saving Time, on October 16, 2021 I began writing a backup of my computer’s internal hard-disk drive onto an external hard-disk drive, a state of my computer’s software I defined as “October 16, 2021 Backup.” That backup process took four hours, 47 minutes, and 48 seconds of time to copy approximately 277 gigabytes of data from my computer’s internal hard-disk drive with a capacity or approximately 486 gigabytes.

    Then during the evening of October 16, 2021 I “booted” into Leap 15.3 with the Linux kernel 5.3.18-59-27.1-default. Before unlocking and updating the software package ca-certificates-mozilla in /var/log /messages I had a very different set of messages from earlier that day:

    Code:
    2021-10-16T20:49:31.499121-04:00 linux-hdi0 vboxadd-service.sh: VirtualBox Guest Addition service started.
    2021-10-16T20:49:31.503474-04:00 linux-hdi0 kernel: [   63.547516] 00:49:31.502868 main     vbglR3GuestCtrlDetectPeekGetCancelSupport: Supported (#1)
    2021-10-16T20:49:31.816451-04:00 linux-hdi0 kernel: [   63.856958] 00:49:31.812437 automount Error: vbsvcAutomounterMountIt: Failed to mount 'HostFolder' on '/media/sf_HostFolder': No such device (-1,19)
    2021-10-16T20:49:31.835546-04:00 linux-hdi0 kernel: [   63.877133] 00:49:31.832610 automount Error: vbsvcAutomounterMountIt: Failed to mount 'VirtualBox' on '/media/sf_VirtualBox': No such device (-1,19)
    2021-10-16T20:49:32.847514-04:00 linux-hdi0 kernel: [   64.890281] 00:49:32.845703 automount Error: vbsvcAutomounterMountIt: Failed to mount 'HostFolder' on '/media/sf_HostFolder': No such device (-1,19)
    2021-10-16T20:49:32.860393-04:00 linux-hdi0 kernel: [   64.902969] 00:49:32.858564 automount Error: vbsvcAutomounterMountIt: Failed to mount 'VirtualBox' on '/media/sf_VirtualBox': No such device (-1,19)
    Note that this time the kernel module vboxsf was not successfully loaded. And since ‘HostFolder’ could not be mounted and no such device as /media/sf_HostFolder could be found, it is clear that the installation of the software package ca-certificates-mozilla later that evening in my Leap-15.3 installation could not have been the cause of those reported problems!

    In a search of the Internet I found a similar problem, including “vboxguest: module verification failed: signature and/or required key missing – tainting kernel” reported on https://www.virtualbox.org/ticket/15419 on the Internet and by Daniel Glasser on https://forums.virtualbox.org/viewtopic.php?f=3&t=77687. On the latter Web page Daniel Glasser wrote, “It seems as though GuestAdditions” (so probably VirtualBox Guest Additions) “is not signing, or is using the wrong key to sign, the kernel module it builds.” In the case of a tainted Linux kernel it is at least imaginable that a reinstallation of the Linux kernel could at least temporarily eliminate that tainting. However, if that reinstallation process would not cause any further problem, unless the cause of such tainting would be eliminated, I could expect the kernel to be tainted again by that cause after reinstalling that Linux kernel. And if the cause of folders being invisible in my shared folder is due to kernel tainting, then I could expect the folders to again be invisible in my shared folder. So in that case it would be better to find the exact cause of the kernel tainting and afterward to eliminate that cause. And unfortunately, although I don’t think I realized it when I wrote the backup of my internal hard-disk drive’s data onto an external hard-disk drive, I suppose that the Linux kernel 5.3.18-59.27.1-default in my hard-disk-drive backup may be tainted.

Page 1 of 2 12 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •