Custom Query (16363 matches)
Results (406 - 408 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #19112 | worksforme | vboxsf (Guest Additions 6.0.14) fails to compile on Linux 3.16 | ||
| Description |
As the title says, vboxsf from Guest Additions 6.0.14 fails to compile on Linux 3.16. More precisely, I'm running VirtualBox 6.0.14, with guest lubuntu 14.04 (kernel 3.16.0-30), 64 bits, on a macOS 10.15 (Catalina) host. The vboxguest module is successfully compiled and loaded (verified with lsmod), but not vboxsf. I have searched the forum and see similar problems reported, and even a ticket (#18238: vboxsf module (6.0.0) does not compile for kernel 3.10 -> fixed after (not in) 5.2.22/6.0.0 or in test builds) but none of those are the same as the error I'm seeing. I noticed the problem when I noticed that my share folders were not working. After using lsmod and modprobe I found that vboxguest was loaded, but vboxsf was not. Furthermore, looking into the modules directory at /lib/modules/3.16.0-30-generic/misc shows only vboxguest.ko, but not vboxsf.ko. So I went to the guest additions source folder and tried to build it manually (running /opt/VBoxGuestAdditions-6.0.14/src/vboxguest-6.0.14/build_in_tmp --module-source vboxsf). This results in the following compilation error: gcc -Wp,-MD,/tmp/vbox.1/.regops.o.d -nostdinc -isystem /usr/lib/gcc/x86_64-linux-gnu/4.8/include -I./arch/x86/include -Iarch/x86/include/generated -Iinclude -I./arch/x86/include/uapi -Iarch/x86/include/generated/uapi -I./include/uapi -Iinclude/generated/uapi -include ./include/linux/kconfig.h -Iubuntu/include -D__KERNEL__ -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -Werror-implicit-function-declaration -Wno-format-security -m64 -mno-mmx -mno-sse -mno-80387 -mno-fp-ret-in-387 -mpreferred-stack-boundary=3 -mtune=generic -mno-red-zone -mcmodel=kernel -funit-at-a-time -maccumulate-outgoing-args -DCONFIG_X86_X32_ABI -DCONFIG_AS_CFI=1 -DCONFIG_AS_CFI_SIGNAL_FRAME=1 -DCONFIG_AS_CFI_SECTIONS=1 -DCONFIG_AS_FXSAVEQ=1 -DCONFIG_AS_CRC32=1 -DCONFIG_AS_AVX=1 -DCONFIG_AS_AVX2=1 -pipe -Wno-sign-compare -fno-asynchronous-unwind-tables -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -mno-avx -fno-delete-null-pointer-checks -O2 -Wframe-larger-than=1024 -fstack-protector -Wno-unused-but-set-variable -fno-omit-frame-pointer -fno-optimize-sibling-calls -fno-var-tracking-assignments -pg -mfentry -DCC_USING_FENTRY -Wdeclaration-after-statement -Wno-pointer-sign -fno-strict-overflow -fconserve-stack -Werror=implicit-int -Werror=strict-prototypes -DCC_HAVE_ASM_GOTO -Wno-declaration-after-statement -fno-pie -include /tmp/vbox.1//include/VBox/VBoxGuestMangling.h -fshort-wchar -O2 -I./include -I/tmp/vbox.1/ -I/tmp/vbox.1/include -I/tmp/vbox.1/r0drv/linux -D__KERNEL__ -DMODULE -DRT_WITHOUT_PRAGMA_ONCE -DRT_OS_LINUX -DIN_RING0 -DIN_RT_R0 -DIN_SUP_R0 -DVBOX -DVBOX_WITH_HGCM -DIN_MODULE -DIN_GUEST -DIN_GUEST_R0 -DRT_NO_EXPORT_SYMBOL -DVBOX_WITH_64_BITS_GUESTS -DRT_ARCH_AMD64 -DMODULE -D"KBUILD_STR(s)=#s" -D"KBUILD_BASENAME=KBUILD_STR(regops)" -D"KBUILD_MODNAME=KBUILD_STR(vboxsf)" -c -o /tmp/vbox.1/.tmp_regops.o /tmp/vbox.1/regops.c
/tmp/vbox.1/regops.c: In function ‘vbsf_iov_iter_get_pages_3_16’:
/tmp/vbox.1/regops.c:314:5: warning: passing argument 4 of ‘iov_iter_get_pages’ makes integer from pointer without a cast [enabled by default]
return iov_iter_get_pages(iter, papPages, cbMax, poffPg0);
^
In file included from /tmp/vbox.1/regops.c:36:0:
include/linux/uio.h:86:9: note: expected ‘unsigned int’ but argument is of type ‘size_t *’
ssize_t iov_iter_get_pages(struct iov_iter *i, struct page **pages,
^
/tmp/vbox.1/regops.c:314:5: error: too few arguments to function ‘iov_iter_get_pages’
return iov_iter_get_pages(iter, papPages, cbMax, poffPg0);
^
In file included from /tmp/vbox.1/regops.c:36:0:
include/linux/uio.h:86:9: note: declared here
ssize_t iov_iter_get_pages(struct iov_iter *i, struct page **pages,
^
/tmp/vbox.1/regops.c:315:1: warning: control reaches end of non-void function [-Wreturn-type]
}
^
make[2]: *** [/tmp/vbox.1/regops.o] Error 1
make[1]: *** [_module_/tmp/vbox.1] Error 2
make[1]: Leaving directory `/usr/src/linux-headers-3.16.0-30-generic'
make: *** [vboxsf] Error 2
So I looked for the problematic function signature and I found the "uio.h" header under /lib/modules/3.16.0-30-generic/build/include/linux, and surely enough, the signature for that function is ssize_t iov_iter_get_pages(struct iov_iter *i, struct page **pages,
size_t maxsize, unsigned maxpages, size_t *start);
and in regops.c, it is called in the following function: #if LINUX_VERSION_CODE >= KERNEL_VERSION(3, 16, 0) && LINUX_VERSION_CODE < KERNEL_VERSION(3, 16, 35)
/** This is for implementing cMaxPage on 3.16 which doesn't have it. */
static ssize_t vbsf_iov_iter_get_pages_3_16(struct iov_iter *iter, struct page **papPages,
size_t cbMax, unsigned cMaxPages, size_t *poffPg0)
{
if (!(iter->type & ITER_BVEC)) {
size_t const offPg0 = iter->iov_offset & PAGE_OFFSET_MASK;
size_t const cbMaxPages = ((size_t)cMaxPages << PAGE_SHIFT) - offPg0;
if (cbMax > cbMaxPages)
cbMax = cbMaxPages;
}
/* else: BVEC works a page at a time and shouldn't have much of a problem here. */
return iov_iter_get_pages(iter, papPages, cbMax, poffPg0);
}
Note that this function is defined explicitly for kernel version 3.16.0, but the function declared in uio.h has five parameters and it is being called with four arguments. |
|||
| #14598 | duplicate | vboxsf "Protocol Error" writing file with ":" colon character | ||
| Description |
VirtualBox version: 5.0.4 Running a Centos 6.5 guest on Mac OSX 10.10.5 host I am unable to create a file containing a ":" colon in a vboxsf directory within the guest. If I create the file on the host then it shows but with "?" in its ls descriptor. The following demonstrates the creation issue within the guest. Note that creating a file in /tmp on the guest is successful at the end. [vagrant@vagrant-centos64 testdir]$ df . Filesystem 1K-blocks Used Available Use% Mounted on TestDirCode 243924992 28710292 215214700 12% /var/lamp/code/testdir [vagrant@vagrant-centos64 testdir]$ mount |grep TestDirCode TestDirCode on /var/lamp/code/testdir type vboxsf (uid=500,gid=500,rw) [vagrant@vagrant-centos64 testdir]$ ls -ld . drwxr-xr-x 1 vagrant vagrant 68 Sep 16 08:30 . [vagrant@vagrant-centos64 testdir]$ echo > test [vagrant@vagrant-centos64 testdir]$ ls -l total 4 -rw-r--r-- 1 vagrant vagrant 1 Sep 16 08:31 test [vagrant@vagrant-centos64 testdir]$ echo > : -bash: :: Protocol error [vagrant@vagrant-centos64 testdir]$ echo > /tmp/: [vagrant@vagrant-centos64 testdir]$ ls -l /tmp/: -rw-rw-r-- 1 vagrant vagrant 1 Sep 16 08:31 /tmp/: If I create the file on the host it then ls reports it like this in the guest: [vagrant@vagrant-centos64 ~]$ ls -l /var/lamp/code/testdir/ ls: cannot access /var/lamp/code/testdir/:: No such file or directory total 4 ?????????? ? ? ? ? ? : -rw-r--r-- 1 vagrant vagrant 1 Sep 16 08:31 test |
|||
| #7414 | obsolete | vboxservice memory usage keeps growing | ||
| Description |
vboxservice keeps growing in memory footprint with time. It normally starts out at something like 22KB, but can grow into the hundreds of K until I reboot the virtual machine. IIRC, it was stable in vbox 3.1.4 and would hold at 22K forever running the exact same guest on the exact same host. |
|||

