On 10/01/2019 03:15 PM, Frank Batschulat wrote:
> 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?
Yes, and I'm sorry here, I don't know the exact release the 5.2.x kernel'ed
guests stopped seeing the vboxsf module. I do know that prior to update of one
guest immediately before that last post, the guest was running the Archlinux
5.2.14 kernel and it exhibited the exact same problem I see with guests
running the 5.3 kernel. Honestly, I don't know where in the update of kernels
this died (Arch updates its kernel generally within a few days of the upstream
release, unless there are large hurdles to overcome in effected packages) This
generally means a new kernel every week or two.
>
> 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.
I just included the complete build script not knowing what, if any of it,
would be relevant to the inquiry. I figured better to provide the entire
example rather than risk trimming something of relevance.
>
> 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.
>
Now we are getting somewhere. The last log I have is:
-rw-r--r-- 1 david david 152 May 29 03:21 tmp/vboxadd-setup.log
$ cat tmp/vboxadd-setup.log
Building the main Guest Additions module for kernel 5.1.5-arch1-2-ARCH.
Building the shared folder support module.
Building the graphics driver module.
So it appears, for whatever reason, there has been no vboxadd-setup.log
generated since the 5.1.5 kernel on May 29. Everything for the current guest
additions are in /opt, e.g.
$ ls -1 /opt/VBoxGuestAdditions-5.2.30
bin
init
installer
lib
other
sbin
src
LICENSE
routines.sh
uninstall.sh
So why isn't it doing its thing? Did the naming of the script contained with
the guest additions change somewhere around that time? I also note there are
no systemd service files for any of the guest services either, if that makes
any difference.
The systemd service file for vboxadd-service is running and fine
$ sysctl status vboxadd-service
● vboxadd-service.service
Loaded: loaded (/opt/VBoxGuestAdditions-5.2.30/init/vboxadd-service;
enabled; vendor preset: disabled)
Active: active (running) since Tue 2019-10-01 16:47:08 CDT; 2min 26s ago
Process: 343 ExecStart=/opt/VBoxGuestAdditions-5.2.30/init/vboxadd-service
start (code=exited, status=0/SUCCESS)
Tasks: 8
Memory: 3.2M
CGroup: /system.slice/vboxadd-service.service
└─356 /usr/sbin/VBoxService --pidfile /var/run/vboxadd-service.sh
Oct 01 16:47:08 vl1 systemd[1]: Starting vboxadd-service.service...
Oct 01 16:47:08 vl1 vboxadd-service[343]: vboxadd-service.sh: Starting
VirtualBox Guest Addition service.
Oct 01 16:47:08 vl1 vboxadd-service.sh[347]: Starting VirtualBox Guest
Addition service.
Oct 01 16:47:08 vl1 vboxadd-service.sh[357]: VirtualBox Guest Addition service
started.
Oct 01 16:47:08 vl1 systemd[1]: Started vboxadd-service.service.
So the VBoxGuestAdditions-5.2.30 service is running without error running:
/opt/VBoxGuestAdditions-5.2.30/init/vboxadd-service start
> 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.
It must not be being built, there is no vboxsf module to be found.
>
> 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.
Archilinux is both the Host and Guest. Both running the 5.3-1 kernel.
>
> Where is this PKGBUILD.txt script executed? In the host? in the guest or
> in both?
>
It is executed when I build the virtulbox-bin-5 package. It is what other Arch
users can download to build and install the virtualbox 5.2.x release. It
translates the generic virtualbox...run file into a pacman package manager
package, e.g.
https://aur.archlinux.org/packages/virtualbox-bin-5/
> 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
>
These are the exact packages I am currently running. I updated everything to
build directly from the testcase repo with the 133577 vbox build and the
133571 extension pack. The packages built from them and installed and running
on the host are:
virtualbox-bin-5 5.2.33-1
virtualbox-ext-oracle-5 5.2.33-1
>
> 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
I'm stumped -- but I'm a pretty good monkey behind the keyboard and don't mind
getting any additional information you may want to see. Just let me know if
there is anything else I can provide.
--
David C. Rankin, J.D.,P.E.
_______________________________________________
VBox-users-community mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/vbox-users-community
_______________________________________________
Unsubscribe:
mailto:[email protected]?subject=unsubscribe
