recipe for target 'vboxguest' failed

Discussions related to using VirtualBox on Linux hosts.
Post Reply
Paul.A
Posts: 2
Joined: 3. Dec 2019, 16:48

recipe for target 'vboxguest' failed

Post by Paul.A »

Using Version 6.0.14 r133895 (Qt5.9.5) on Ubuntu 18.04.3LTS (fully updated) with kernel 5.0.0-37-generic. I can no longer use the vboxguest (can't find version number, all .iso files dated 10 Oct. 2019) -- however the VM (XP Pro) boots without problems. From logs:

Code: Select all

Error building the module.  Build output follows.
make V=1 CONFIG_MODULE_SIG= -C /lib/modules/5.0.0-32-generic/build SUBDIRS=/tmp/vbox.0 SRCROOT=/tmp/vbox.0 -j8 modules
make[1]: warning: -jN forced in submake: disabling jobserver mode.
Makefile:223: ================= WARNING ================
Makefile:224: 'SUBDIRS' will be removed after Linux 5.3
Makefile:225: Please use 'M=' or 'KBUILD_EXTMOD' instead
Makefile:226: ==========================================
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)
/... snip .../ 
/tmp/vbox.0/r0drv/linux/memuserkernel-r0drv-linux.c: In function ‘VBoxGuest_RTR0MemUserIsValidAddr’:
/tmp/vbox.0/r0drv/linux/memuserkernel-r0drv-linux.c:69:55: error: macro "access_ok" passed 3 arguments, but takes just 2
     bool fRc = access_ok(VERIFY_READ, (void *)R3Ptr, 1);
                                                       ^
/tmp/vbox.0/r0drv/linux/memuserkernel-r0drv-linux.c:69:16: error: ‘access_ok’ undeclared (first use in this function)
     bool fRc = access_ok(VERIFY_READ, (void *)R3Ptr, 1);
                ^~~~~~~~~
/tmp/vbox.0/r0drv/linux/memuserkernel-r0drv-linux.c:69:16: note: each undeclared identifier is reported only once for each function it appears in
scripts/Makefile.build:284: recipe for target '/tmp/vbox.0/r0drv/linux/memuserkernel-r0drv-linux.o' failed
make[2]: *** [/tmp/vbox.0/r0drv/linux/memuserkernel-r0drv-linux.o] Error 1
make[2]: *** Waiting for unfinished jobs....
Makefile:1614: recipe for target '_module_/tmp/vbox.0' failed
make[1]: *** [_module_/tmp/vbox.0] Error 2
/tmp/vbox.0/Makefile.include.footer:106: recipe for target 'vboxguest' failed
make: *** [vboxguest] Error 2
modprobe vboxguest failed
Any suggestions would be welcomed.
Thanks -- Paul
socratis
Site Moderator
Posts: 27329
Joined: 22. Oct 2010, 11:03
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5
Location: Greece

Re: recipe for target 'vboxguest' failed

Post by socratis »

Paul.A wrote:Using Version 6.0.14 r133895 (Qt5.9.5) on Ubuntu 18.04.3LTS ... use the vboxguest
Are you trying to build the Guest Additions on the Host? The Guest Additions are for the Guest, and you wouldn't compile the Guest Additions for an XP Guest...
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Paul.A
Posts: 2
Joined: 3. Dec 2019, 16:48

Re: recipe for target 'vboxguest' failed

Post by Paul.A »

Many thanks. On verification, it's running in the virtual OS (Win XP Pro SP2), but is still creating the log entries that I included in my first post. -- Paul
socratis
Site Moderator
Posts: 27329
Joined: 22. Oct 2010, 11:03
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5
Location: Greece

Re: recipe for target 'vboxguest' failed

Post by socratis »

Paul.A wrote:it's running in the virtual OS (Win XP Pro SP2)
You mean the VM/Guest is WinXP SP2, right?
Paul.A wrote:but is still creating the log entries that I included in my first post.
Where does it create the entries? These don't look like entries that you'd get from a WinXP Guest Additions installation, something's not appropriately documented. Can you post a step-by-step scenario so that we can reproduce it?
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Post Reply