You are not logged in.

#1 2019-01-02 01:28:55

smitty1e
Member
Registered: 2016-06-11
Posts: 6

[SOLVED]--upstream issue--Kernel 4.20 and VBoxLinuxAdditions

I run Arch on a guest under VirtualBox, but the guest addition script fails after an Arch kernel upgrade.
After a pacman -Syu and taking the newest kernel, I tried mounted the guest additions cdrom and tried to compile the VBoxLinuxAdditions:

[root@archvbox linux-4.20.arch1]# /mnt/cdrom/VBoxLinuxAdditions.run
Verifying archive integrity... All good.
Uncompressing VirtualBox 5.2.22 Guest Additions for Linux........
VirtualBox Guest Additions installer
Removing installed version 5.2.22 of VirtualBox Guest Additions...
Copying additional installer modules ...
Installing additional modules ...
VirtualBox Guest Additions: Building the VirtualBox Guest Additions kernel modules.  This may take a while.

VirtualBox Guest Additions: Look at /var/log/vboxadd-setup.log to find out what went wrong
VirtualBox Guest Additions: Running kernel modules will not be replaced until the system is restarted
VirtualBox Guest Additions: Starting.
[root@archvbox linux-4.20.arch1]# head /var/log/vboxadd-setup.log
Building the main Guest Additions module.
Error building the module.  Build output follows.
make V=1 CONFIG_MODULE_SIG= -C /lib/modules/4.20.0-arch1-1-ARCH/build SUBDIRS=/tmp/vbox.0 SRCROOT=/tmp/vbox.0 -j1 modules
test -e include/generated/autoconf.h -a -e include/config/auto.conf || (                \
echo >&2;                                                       \
echo >&2 "  ERROR: Kernel configuration is invalid.";           \
echo >&2 "         include/generated/autoconf.h or include/config/auto.conf are missing.";\
echo >&2 "         Run 'make oldconfig && make prepare' on kernel src to fix it.";      \
echo >&2 ;                                                      \
/bin/false)

Dutifully, I tried to re-run the make targets against the kernel source tree:

[root@archvbox linux-4.20.arch1]# cd /usr/src/linux-4.20.arch1
[root@archvbox linux-4.20.arch1]# make oldconfig && make prepare
scripts/kconfig/conf  --oldconfig Kconfig
#
# configuration written to .config
#
scripts/kconfig/conf  --syncconfig Kconfig
make[1]: *** No rule to make target 'arch/x86/entry/syscalls/syscall_32.tbl', needed by 'arch/x86/include/generated/asm/syscalls_32.h'.  Stop.
make: *** [arch/x86/Makefile:233: archheaders] Error 2

It seems as though, perhaps, some files are missing/moved in the kernel distribution package?
Didn't find any obvious clues via Google. Do people have better things to do on New Year's?
Thanks,
Chris

Last edited by smitty1e (2019-01-05 17:56:46)

Offline

#2 2019-01-02 21:01:24

WFV
Member
From: right here right now ℶ
Registered: 2013-04-23
Posts: 235

Re: [SOLVED]--upstream issue--Kernel 4.20 and VBoxLinuxAdditions

Do people have better things to do on New Year's?

no - read the Wiki, don't need to run the guest iso CD.
install these in the guest instead:

community/virtualbox-guest-modules-arch 6.0.0-2
                  Virtualbox guest kernel modules for Arch Kernel
community/virtualbox-guest-utils 6.0.0-1
                  VirtualBox Guest userspace utilities

else if using dkms, then install the guest-dkms

Last edited by WFV (2019-01-02 21:01:43)

Offline

#3 2019-01-05 17:38:19

smitty1e
Member
Registered: 2016-06-11
Posts: 6

Re: [SOLVED]--upstream issue--Kernel 4.20 and VBoxLinuxAdditions

WFV,
Reading the wiki is always smart.
After

sudo pacman -S virtualbox-guest-modules-arch virtualbox-guest-utils

rebooting and doing

sudo mount -t vboxsf host /mnt/host

here is my dmesg:

[   78.628545] sysfs: cannot create duplicate filename '/devices/virtual/bdi/vboxsf-host'
[   78.628551] CPU: 0 PID: 738 Comm: mount Tainted: G         C OE     4.20.0-arch1-1-ARCH #1
[   78.628552] Hardware name: innotek GmbH VirtualBox/VirtualBox, BIOS VirtualBox 12/01/2006
[   78.628553] Call Trace:
[   78.628585]  dump_stack+0x5c/0x80
[   78.628603]  sysfs_warn_dup.cold.0+0x17/0x2a
[   78.628613]  sysfs_create_dir_ns+0xa7/0xd0
[   78.628616]  kobject_add_internal+0xa5/0x250
[   78.628618]  kobject_add+0x7d/0xb0
[   78.628622]  ? preempt_count_add+0x79/0xb0
[   78.628628]  device_add+0x125/0x6c0
[   78.628637]  device_create_groups_vargs+0xd1/0xf0
[   78.628641]  device_create_vargs+0x12/0x20
[   78.628644]  bdi_register_va.part.2+0x23/0x190
[   78.628653]  super_setup_bdi_name+0x8e/0xf0
[   78.628663]  sf_fill_super+0x103/0x250 [vboxsf]
[   78.628666]  ? sf_remount_fs+0x60/0x60 [vboxsf]
[   78.628668]  mount_nodev+0x48/0xa0
[   78.628671]  sf_mount+0x31/0x50 [vboxsf]
[   78.628673]  mount_fs+0x3b/0x167
[   78.628677]  vfs_kern_mount.part.11+0x54/0x110
[   78.628679]  do_mount+0x1fd/0xc80
[   78.628683]  ? _copy_from_user+0x37/0x60
[   78.628685]  ? memdup_user+0x4b/0x70
[   78.628687]  ksys_mount+0xba/0xd0
[   78.628689]  __x64_sys_mount+0x21/0x30
[   78.628692]  do_syscall_64+0x5b/0x170
[   78.628698]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
[   78.628700] RIP: 0033:0x7f963ed8d68e
[   78.628702] Code: 48 8b 0d d5 17 0c 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 49 89 ca b8 a5 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d a2 17 0c 00 f7 d8 64 89 01 48
[   78.628703] RSP: 002b:00007ffc5fc20b08 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5
[   78.628705] RAX: ffffffffffffffda RBX: 0000560530fab400 RCX: 00007f963ed8d68e
[   78.628706] RDX: 0000560530fab610 RSI: 0000560530fab690 RDI: 0000560530fab670
[   78.628707] RBP: 00007f963eeb21c4 R08: 0000000000000000 R09: 0000000000000000
[   78.628708] R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
[   78.628709] R13: 0000000000000000 R14: 0000560530fab670 R15: 0000560530fab610
[   78.628713] kobject_add_internal failed for vboxsf-host with -EEXIST, don't try to register things with the same name in the same directory.

Offline

#4 2019-01-05 17:51:02

smitty1e
Member
Registered: 2016-06-11
Posts: 6

Re: [SOLVED]--upstream issue--Kernel 4.20 and VBoxLinuxAdditions

And, for a little more research, I see that this has more to do with the kernel proper, and is not an Arch thing.

This happened last year, too, and was fixed in the next VirtualBox upgrade.

I appreciate that the kernel guys think breaking userspace is a huge deal. I guess the virtualization API is different somehow, as mounting host storage seems a fairly regular point of breakage. But I an't smart enough to submit a patch, so I'll just enjoy getting what I paid for. ;-)

The S3 fallback plan, bite though it may, remains in effect.

Thanks!

Offline

#5 2019-01-05 18:39:45

loqs
Member
Registered: 2014-03-06
Posts: 7,294

Re: [SOLVED]--upstream issue--Kernel 4.20 and VBoxLinuxAdditions

smitty1e wrote:

And, for a little more research, I see that this has more to do with the kernel proper, and is not an Arch thing.

This happened last year, too, and was fixed in the next VirtualBox upgrade.

I appreciate that the kernel guys think breaking userspace is a huge deal. I guess the virtualization API is different somehow, as mounting host storage seems a fairly regular point of breakage. But I an't smart enough to submit a patch, so I'll just enjoy getting what I paid for. ;-)

The S3 fallback plan, bite though it may, remains in effect.

Thanks!

The issue you linked to was already fixed by arch https://git.archlinux.org/svntogit/comm … 68d1e240d3 then the fix was removed when upstream Oracle included it.
The interface the kernel provides to userspace should be stable but that does not include the interface as supplied by third party modules or interfaces that are not exported to userspace.
If it was that bug the module would not have built.

Offline

#6 2019-01-06 02:21:07

smitty1e
Member
Registered: 2016-06-11
Posts: 6

Re: [SOLVED]--upstream issue--Kernel 4.20 and VBoxLinuxAdditions

Well, it doesn't work with my current:

VirtualBox Version 5.2.22 r126460 (Qt5.6.2) running under Win10 ver 1709 build 16299.785

It had been broken last Fall, around 5.2.20, and then fixed (for a while) under 5.2.22. Different compile error this time under VBoxLinuxAdditions.run

#GoFigure

Offline

#7 2019-01-06 11:33:17

loqs
Member
Registered: 2014-03-06
Posts: 7,294

Re: [SOLVED]--upstream issue--Kernel 4.20 and VBoxLinuxAdditions

smitty1e wrote:

Well, it doesn't work with my current:

VirtualBox Version 5.2.22 r126460 (Qt5.6.2) running under Win10 ver 1709 build 16299.785

It had been broken last Fall, around 5.2.20, and then fixed (for a while) under 5.2.22. Different compile error this time under VBoxLinuxAdditions.run

#GoFigure

Why is a compile error from VBoxLinuxAdditions.run relevant if you are using virtualbox-guest-modules-arch and virtualbox-guest-utils?

pacman -Si virtualbox
Repository      : community
Name            : virtualbox
Version         : 6.0.0-1
Description     : Powerful x86 virtualization for enterprise as well as home use
Architecture    : x86_64
URL             : http://virtualbox.org
Licenses        : GPL  custom
Groups          : None
Provides        : None
Depends On      : glibc  openssl  curl  gcc-libs  libpng  python  sdl  libvpx
                  libxml2  procps-ng  shared-mime-info  zlib  libxcursor
                  libxinerama  libx11  libxext  libxmu  libxt  qt5-base
                  qt5-x11extras  VIRTUALBOX-HOST-MODULES
Optional Deps   : vde2: Virtual Distributed Ethernet support
                  virtualbox-guest-iso: Guest Additions CD image
                  virtualbox-ext-vnc: VNC server support
                  virtualbox-sdk: Developer kit
Conflicts With  : virtualbox-ose
Replaces        : virtualbox-ose
Download Size   : 61.28 MiB
Installed Size  : 175.52 MiB
Packager        : Christian Hesse <arch@eworm.de>
Build Date      : Wed 26 Dec 2018 21:56:59 GMT
Validated By    : MD5 Sum  SHA-256 Sum  Signature

Edit:
Is the issue still present with the current packages supplied by arch?

Last edited by loqs (2019-01-06 11:56:06)

Offline

#8 2019-01-09 01:35:09

smitty1e
Member
Registered: 2016-06-11
Posts: 6

Re: [SOLVED]--upstream issue--Kernel 4.20 and VBoxLinuxAdditions

Saved by VB6!

(I guess I could have phrased that differently.)

Thanks for your advice, mate.

Offline

Board footer

Powered by FluxBB