VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (397 - 399 of 16363)

Ticket Resolution Summary Owner Reporter
#17990 duplicate vboxsf failed to compile on Fedora 28 with kernel 4.18 Thierry Lelegard
Description

Using VBox 5.2.18 r124319 on Windows 7 host with Fedora 28 guest.

Fedora 28 just switched from kernel 4.17 to 4.18. Since then, the vboxsf driver failed to compile in the guest additions.

$ uname -a
Linux vmfedora 4.18.5-200.fc28.x86_64 #1 SMP Tue Sep 4 15:56:14 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

Excerpt from /var/log/vboxadd-setup.log (full file attached):

/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)
                                                    ~~~~~~~~~~~~~~~~~^~

I assume that kernel 4.18 introduced a non-backward compatible change which must be handled in the driver source code.

#11642 duplicate vboxsf does not support hard or soft file symlinks RoelV
Description

[roel@localhost ssd]$ mount | grep "vboxsf" /ssd on /ssd type vboxsf (rw) ssd on /media/sf_ssd type vboxsf (gid=501,rw) [roel@localhost ssd]$ echo "test" > test1 [roel@localhost ssd]$ ln test1 test2 ln: creating hard link test2' => test1': Operation not permitted [roel@localhost ssd]$ ln -s test1 test2 ln: creating symbolic link `test2': Read-only file system [roel@localhost ssd]$ cd ~ [roel@localhost ~]$ echo "test" > test1 [roel@localhost ~]$ ln test1 test2 [roel@localhost ~]$ ln -s test1 test2 ln: creating symbolic link `test2': File exists [roel@localhost ~]$ rm test2 [roel@localhost ~]$ ln -s test1 test2 [roel@localhost ssd]$ tar -xf Percona-Server-5.6.8-alpha60.2-313.Linux.x86_64.tar.gz tar: Percona-Server-5.6.8-alpha60.2-313.Linux.x86_64/lib/libmysqlclient_r.a: Cannot create symlink to `libmysqlclient.a': Read-only file system tar: Percona-Server-5.6.8-alpha60.2-313.Linux.x86_64/lib/libmysqlclient.so: Cannot create symlink to `libmysqlclient.so.18': Read-only file system

Btw, the file system is definitely not read-only (and as a sidenote privileges are set to 777), as can be seen from the successful creation of test1 initially as per the above. It can also be seen by the fact that the tar is successful in extracting files, except for symlinks.

#11641 wontfix vboxsf does not seem to support BLKGETSIZE & BLKFLSBUF RoelV
Description
[roel@localhost ~]$ mount | egrep "sda|vboxsf"
/dev/sda1 on /boot type ext4 (rw)
/ssd on /ssd type vboxsf (rw)
ssd on /media/sf_ssd type vboxsf (gid=501,rw)
[roel@localhost ~]$ sudo hdparm -t /dev/sda1

/dev/sda1:
 Timing buffered disk reads:  492 MB in  3.01 seconds = 163.28 MB/sec
[roel@localhost ~]$ sudo hdparm -t /media/sf_ssd

/media/sf_ssd:
 BLKGETSIZE failed: Inappropriate ioctl for device

BLKFLSBUF failed: Inappropriate ioctl for device
[roel@localhost ~]$
[roel@localhost ~]$ sudo hdparm -t /ssd

/ssd:
 BLKGETSIZE failed: Inappropriate ioctl for device
BLKFLSBUF failed: Inappropriate ioctl for device
Batch Modify
Note: See TracBatchModify for help on using batch modify.
Note: See TracQuery for help on using queries.

© 2024 Oracle Support Privacy / Do Not Sell My Info Terms of Use Trademark Policy