Custom Query (16363 matches)
Results (1285 - 1287 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #17986 | obsolete | Menuet32 task switch bug in 5.2.18 | ||
| Description |
Menuet32 doesn't start anymore in any version after 4.2.38, including latest VB 5.2.18. So when updating from 4.2.38 to 4.3.0, Menuets blue setup screen works fine, but multitasking after that halts. Menuet32 uses TSSs (task state segments) for task switching. M32 available at Menuetos . net / download area Running VB on Windows 7 Home Service Pack 1, Intel Core i3, M 380, 2.53Ghz |
|||
| #17984 | duplicate | 5.2.18 r124319 Guest vboxsf not compiling for Fedora 28, no shared folders | ||
| Description |
Hi, I tested by installing both FC 28 32 and 64 bit. The same build issue can be reproduced. Compilation of module vboxsf fails. Building the main Guest Additions module.
Building the shared folder support module.
Error building the module:
make V=1 CONFIG_MODULE_SIG= -C /lib/modules/4.18.5-200.fc28.i686/build SUBDIRS=/tmp/vbox.0 SRCROOT=/tmp/vbox.0 -j1 modules
,,,
gcc -Wp,-MD,/tmp/vbox.0/.utils.o.d -nostdinc -isystem /usr/lib/gcc/i686-redhat-linux/8/include -I./arch/x86/include -I./arch/x86/include/generated -I./include -I./arch/x86/include/uapi -I./arch/x86/include/generated/uapi -I./include/uapi -I./include/generated/uapi -include ./include/linux/kconfig.h -include ./include/linux/compiler_types.h -D__KERNEL__ -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -fshort-wchar -Werror-implicit-function-declaration -Wno-format-security -std=gnu89 -fno-PIE -DCC_HAVE_ASM_GOTO -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -mno-avx -m32 -msoft-float -mregparm=3 -freg-struct-return -fno-pic -mpreferred-stack-boundary=2 -march=i686 -mtune=generic -Wa,-mtune=generic32 -ffreestanding -DCONFIG_AS_CFI=1 -DCONFIG_AS_CFI_SIGNAL_FRAME=1 -DCONFIG_AS_CFI_SECTIONS=1 -DCONFIG_AS_SSSE3=1 -DCONFIG_AS_CRC32=1 -DCONFIG_AS_AVX=1 -DCONFIG_AS_AVX2=1 -DCONFIG_AS_AVX512=1 -DCONFIG_AS_SHA1_NI=1 -DCONFIG_AS_SHA256_NI=1 -pipe -Wno-sign-compare -fno-asynchronous-unwind-tables -mindirect-branch=thunk-extern -mindirect-branch-register -DRETPOLINE -fno-delete-null-pointer-checks -Wno-frame-address -Wno-format-truncation -Wno-format-overflow -Wno-int-in-bool-context -O2 --param=allow-store-data-races=0 -Wframe-larger-than=1024 -fstack-protector-strong -Wno-unused-but-set-variable -Wno-unused-const-variable -fno-omit-frame-pointer -fno-optimize-sibling-calls -fvar-tracking-assignments -g -pg -mfentry -DCC_USING_FENTRY -Wdeclaration-after-statement -Wno-pointer-sign -fno-strict-overflow -fno-merge-all-constants -fmerge-constants -fno-stack-check -fconserve-stack -Werror=implicit-int -Werror=strict-prototypes -Werror=date-time -Werror=incompatible-pointer-types -Werror=designated-init -fmacro-prefix-map=./= -Wno-packed-not-aligned -mrecord-mcount -Wno-declaration-after-statement -fshort-wchar -include /tmp/vbox.0/include/VBox/VBoxGuestMangling.h -fno-pie -I/lib/modules/4.18.5-200.fc28.i686/build/include -I/tmp/vbox.0/ -I/tmp/vbox.0/include -I/tmp/vbox.0/r0drv/linux -I/tmp/vbox.0/vboxsf/ -I/tmp/vbox.0/vboxsf/include -I/tmp/vbox.0/vboxsf/r0drv/linux -D__KERNEL__ -DMODULE -DRT_OS_LINUX -DIN_RING0 -DIN_RT_R0 -DIN_SUP_R0 -DVBOX -DVBOX_WITH_HGCM -DIN_MODULE -DIN_GUEST_R0 -DRT_NO_EXPORT_SYMBOL -DRT_ARCH_X86 -DMODULE -DKBUILD_BASENAME='"utils"' -DKBUILD_MODNAME='"vboxsf"' -c -o /tmp/vbox.0/utils.o /tmp/vbox.0/utils.c
/tmp/vbox.0/utils.c: In function ‘sf_init_inode’:
/tmp/vbox.0/utils.c:165:28: error: passing argument 1 of ‘sf_ftime_from_timespec’ from incompatible pointer type [-Werror=incompatible-pointer-types]
sf_ftime_from_timespec(&inode->i_atime, &info->AccessTime);
^~~~~~~~~~~~~~~
/tmp/vbox.0/utils.c:53:53: note: expected ‘struct timespec *’ but argument is of type ‘struct timespec64 *’
static void sf_ftime_from_timespec(struct timespec *tv, RTTIMESPEC *ts)
~~~~~~~~~~~~~~~~~^~
/tmp/vbox.0/utils.c:166:28: error: passing argument 1 of ‘sf_ftime_from_timespec’ from incompatible pointer type [-Werror=incompatible-pointer-types]
sf_ftime_from_timespec(&inode->i_ctime, &info->ChangeTime);
^~~~~~~~~~~~~~~
/tmp/vbox.0/utils.c:53:53: note: expected ‘struct timespec *’ but argument is of type ‘struct timespec64 *’
static void sf_ftime_from_timespec(struct timespec *tv, RTTIMESPEC *ts)
~~~~~~~~~~~~~~~~~^~
/tmp/vbox.0/utils.c:167:28: error: passing argument 1 of ‘sf_ftime_from_timespec’ from incompatible pointer type [-Werror=incompatible-pointer-types]
sf_ftime_from_timespec(&inode->i_mtime, &info->ModificationTime);
^~~~~~~~~~~~~~~
/tmp/vbox.0/utils.c:53:53: note: expected ‘struct timespec *’ but argument is of type ‘struct timespec64 *’
static void sf_ftime_from_timespec(struct timespec *tv, RTTIMESPEC *ts)
~~~~~~~~~~~~~~~~~^~
/tmp/vbox.0/utils.c: In function ‘sf_setattr’:
/tmp/vbox.0/utils.c:377:54: error: passing argument 2 of ‘sf_timespec_from_ftime’ from incompatible pointer type [-Werror=incompatible-pointer-types]
sf_timespec_from_ftime(&info.AccessTime, &iattr->ia_atime);
^~~~~~~~~~~~~~~~
/tmp/vbox.0/utils.c:63:69: note: expected ‘struct timespec *’ but argument is of type ‘struct timespec64 *’
static void sf_timespec_from_ftime(RTTIMESPEC *ts, struct timespec *tv)
~~~~~~~~~~~~~~~~~^~
/tmp/vbox.0/utils.c:379:60: error: passing argument 2 of ‘sf_timespec_from_ftime’ from incompatible pointer type [-Werror=incompatible-pointer-types]
sf_timespec_from_ftime(&info.ModificationTime, &iattr->ia_mtime);
^~~~~~~~~~~~~~~~
/tmp/vbox.0/utils.c:63:69: note: expected ‘struct timespec *’ but argument is of type ‘struct timespec64 *’
static void sf_timespec_from_ftime(RTTIMESPEC *ts, struct timespec *tv)
~~~~~~~~~~~~~~~~~^~
cc1: some warnings being treated as errors
make[2]: *** [scripts/Makefile.build:318: /tmp/vbox.0/utils.o] Error 1
make[1]: *** [Makefile:1504: _module_/tmp/vbox.0] Error 2
make: *** [/tmp/vbox.0/Makefile.include.footer:101: vboxsf] Error 2
Before this, I had to yum install the following: sudo yum install gcc.i686 perl.i686 make before that the gcc kernel headers. |
|||
| #17983 | invalid | VM unlock | ||
| Description |
I am unable to unlock the VM image. I tried using right+ctrl key. Not if there is any other way. |
|||

