On Tue, 01 Oct 2019 20:03:48 +0200, David C. Rankin
<[email protected]> wrote:
(sorry Frank, you get 2-copies, I just noticed I sent to you and not the
list)
On 09/30/2019 10:32 AM, Frank Batschulat wrote:
Sorry, see my latest update, I cannot confirm these problems exist.
https://www.virtualbox.org/ticket/18961
https://www.virtualbox.org/ticket/18961#comment:11
do you have the corresponding extension pack installed on the host?
Yes, I built it from testbuilds as well.
https://www.virtualbox.org/download/testcase/Oracle_VM_VirtualBox_Extension_Pack-5.2.33-133571.vbox-extpack
other then that, what are the detailed errors in your guest when
installing and building the guest additions?
No errors whatsoever during the module build stage. That's is what is so
puzzling. All guest modules other than vboxsf are fine. It's like the
build thinks things are all okay, but when a guest running the 5.3
kernel starts it never sees the vboxsf module.
For windows guest or guest running the 4.x kernel, there is no problem.
The vboxsf module is listed for example under openSUSE leap 15 and
access to the shared folders are fine, as they are for win7 guests.
However starting with the 5.2 kernel (or there about) guests simply do
not see the vboxsf module.
I am puzzled. Now we are starting to have problems with a 5.2 kernel as
well
and not only with a 5.3 kernel in the guest?
I also wonder about the PKGBUILD.txt doing a lot of stuff and installation
activity on the host we don't really care about this in the context of the
guest and its guest additions.
All we should care about is the guest additions ISO that is being
mounted into the guest and for which you then run the installation
script that comes with the guest additions. This should have output and
a log file in /var/log as I've shown in the bug for my testing.
In either case we should see some errors and we should also
be able to check for the guests vboxsf kernel module itself, it must be
there
in the guest when the build was successful.
So is ARCHLinux the guest ? Is it the host or is it both? I've taken it
as the problems happen with an ARCHLinux guest running a 5.3 kernel.
Where is this PKGBUILD.txt script executed? In the host? in the guest or
in both?
Rather then chasing this special installation procedure we should start by
verifying whether or not the public official installation archive from
virtualbox.org
including the guest additions that come with it plus the corresponding
extension pack
do work I suppose, since the inital problem target was a 5.3 kernel that
would
imply installing in the host since you explicitely want VBOX 5.2.x:
https://www.virtualbox.org/download/testcase/VirtualBox-5.2.33-133577-Linux_amd64.run
https://www.virtualbox.org/download/testcase/Oracle_VM_VirtualBox_Extension_Pack-5.2.33-133571.vbox-extpack
the guest additions usually come with the base package, but in any case
they
are also available from the web site:
https://www.virtualbox.org/download/testcase/VBoxGuestAdditions_5.2.33-133577.iso
This I suppose is with what we should start with because this is what is
working and
verified to work against a 5.3 kernel (Fedora 31).
thanks
--
frankB
Oracle Virtualbox Development
_______________________________________________
VBox-users-community mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/vbox-users-community
_______________________________________________
Unsubscribe:
mailto:[email protected]?subject=unsubscribe
