Custom Query (16363 matches)
Results (19 - 21 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #17726 | duplicate | Shared folder read errors | ||
| Description |
File reads from shared folder in the Linux kernel encounters errors. An easy way to test this is with a loop device. root@VirtualBox:~# dd if=/dev/zero of=/media/sf_z/test.dd count=1024 1024+0 records in 1024+0 records out 524288 bytes (524 kB, 512 KiB) copied, 0.0408967 s, 12.8 MB/s root@VirtualBox:~# losetup -f /media/sf_z/test.dd Errors will occur, and the kernel would not be able to identify the partitions because it can't read the image: [ 1174.109112] print_req_error: I/O error, dev loop0, sector 0 [ 1174.109141] print_req_error: I/O error, dev loop0, sector 0 [ 1174.109157] Buffer I/O error on dev loop0, logical block 0, async page read [ 1174.109255] print_req_error: I/O error, dev loop0, sector 0 [ 1174.109271] Buffer I/O error on dev loop0, logical block 0, async page read [ 1174.109293] print_req_error: I/O error, dev loop0, sector 0 [ 1174.109308] Buffer I/O error on dev loop0, logical block 0, async page read [ 1174.109329] print_req_error: I/O error, dev loop0, sector 0 [ 1174.109343] Buffer I/O error on dev loop0, logical block 0, async page read [ 1174.109365] print_req_error: I/O error, dev loop0, sector 0 [ 1174.109379] Buffer I/O error on dev loop0, logical block 0, async page read [ 1174.109401] print_req_error: I/O error, dev loop0, sector 0 [ 1174.109415] Buffer I/O error on dev loop0, logical block 0, async page read [ 1174.109442] print_req_error: I/O error, dev loop0, sector 24 [ 1174.109457] Buffer I/O error on dev loop0, logical block 3, async page read [ 1174.146072] print_req_error: I/O error, dev loop0, sector 0 [ 1174.146103] print_req_error: I/O error, dev loop0, sector 0 [ 1174.146119] Buffer I/O error on dev loop0, logical block 0, async page read [ 1174.146145] Buffer I/O error on dev loop0, logical block 0, async page read [ 1174.146168] Buffer I/O error on dev loop0, logical block 0, async page read
There is no problem if the image is copied from the shared folder into the VM first, then using Other information can be found here: [ 5.343584] vboxsf: Successfully loaded version 5.2.10 (interface 0x00010004)
[ 5.606238] VBoxService 5.2.10 r122406 (verbosity: 0) linux.amd64 (Apr 27 2018 11:36:11) release log
00:00:00.000045 main Log opened 2018-05-02T07:56:09.478284000Z
[ 5.606265] 00:00:00.000098 main OS Product: Linux
[ 5.606279] 00:00:00.000116 main OS Release: 4.13.0-21-generic
[ 5.606295] 00:00:00.000130 main OS Version: #24-Ubuntu SMP Mon Dec 18 17:29:16 UTC 2017
[ 5.606321] 00:00:00.000146 main Executable: /opt/VBoxGuestAdditions-5.2.10/sbin/VBoxService
00:00:00.000147 main Process ID: 697
00:00:00.000147 main Package type: LINUX_64BITS_GENERIC
[ 5.607246] 00:00:00.001076 main 5.2.10 r122406 started. Verbose level = 0
[ 5.624085] 00:00:00.017888 automount vbsvcAutoMountWorker: Shared folder 'z' was mounted to '/media/sf_z'
This bug has existed since 5.2.8; upgraded to 5.2.10 and it was still present. |
|||
| #17682 | duplicate | vboxdrv.sh: failed: modprobe vboxpci failed at 4.15.11-1.el7.elrepo.x86_64 -> duplicate of #17683 | ||
| Description |
centos7 update kernel to 4.15.11 elrepo ,and vbox install have some problems with "vboxpci: Unknown symbol vfs_write (err 0)" uname -a Linux crmdev205 4.15.11-1.el7.elrepo.x86_64 #1 SMP Mon Mar 19 11:46:06 EDT 2018 x86_64 x86_64 x86_64 GNU/Linux
Verifying archive integrity... All good. Uncompressing VirtualBox for Linux installation............. VirtualBox Version 5.1.34 r121010 (2018-02-26T15:29:57Z) installer Removing previous installation of VirtualBox 5.1.32 r120294 from /opt/VirtualBox Installing VirtualBox to /opt/VirtualBox Python found: python, installing bindings... vboxdrv.sh: failed: modprobe vboxpci failed. Please use 'dmesg' to find out why. There were problems setting up VirtualBox. To re-start the set-up process, run
as root. VirtualBox has been installed successfully. You will find useful information about using VirtualBox in the user manual
and in the user FAQ We hope that you enjoy using VirtualBox. [root@crmdev205 soft]# dmesg | tail -f [1746570.104013] vboxdrv: Successfully loaded version 5.1.34 (interface 0x002a0000) [1746570.312366] VBoxNetFlt: Successfully started. [1746570.318263] VBoxNetAdp: Successfully started. [1746570.321467] vboxpci: Unknown symbol vfs_write (err 0) [1747176.620175] vboxdrv: Found 32 processor cores [1747176.635978] vboxdrv: TSC mode is Invariant, tentative frequency 1999998028 Hz [1747176.635979] vboxdrv: Successfully loaded version 5.1.34 (interface 0x002a0000) [1747176.840965] VBoxNetFlt: Successfully started. [1747176.844354] VBoxNetAdp: Successfully started. [1747176.846577] vboxpci: Unknown symbol vfs_write (err 0) |
|||
| #791 | fixed | Incorrect mac address verifier -> fixed in SVN | ||
| Description |
if i go to linux debian etch latest host and i go into virtual machine network 0 menu and change the ethernet address to DEADBEEF0000 it reverts back to a random address. 00DEADBEEF00 works fine and on the windows host 1.5.2 DEADBEEF0000 works fine. even changing the mac in the xml fine under linux to DEADBEEF0000 doesnt work. |
|||

