Custom Query (16363 matches)
Results (1186 - 1188 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #2047 | fixed | 1366x768 host resolution not supported in fullscreen or seamless mode => Fixed in SVN | ||
| Description |
My notebook (Sony VGN-TZ27GN) has screen resolution of 1366x768. In full screen mode, the guest resolution is 1360x768, centred in the screen, leaving 3 pixels empty at either side of the screen. In seamless mode, application windows are missing the right-most 3 pixels and gain an extra 3 pixels on the left, displaying the underlying desktop in the Guest (see attached screenshot). I've also attached the VBox.log showing (at 00:00:38.066) VMMDev::SetVideoModeHint detecting the correct resolution and then being set incorrectly with Display::handleDisplayResize(). |
|||
| #2048 | fixed | Linux - Disk I/O performance problems | ||
| Description |
Hello, I am running VirtualBox 1.6.4 on a Linux system with a Linux guest. I did I/O performance tests with the following setup:
So both commands overwrite the existing file without truncating it, the second command uses direct I/O for this task. The results are as follows: dd if=/dev/zero of=/test.file bs=4M count=1000 conv=notrunc & 1000+0 records in 1000+0 records out 4194304000 bytes (4.2 GB) copied, 416.406 s, 10.1 MB/s dd if=/dev/zero of=/test.file bs=4M count=1000 conv=notrunc oflag=direct & 1000+0 records in 1000+0 records out 4194304000 bytes (4.2 GB) copied, 108.356 s, 38.7 MB/s As one can see, the first command (normal I/O) is very slow, whereas direct I/O is resonably fast. Is there any explanation for this behavior? As far as I know, direct I/O circumvents buffering in the linux kernel, so there must be a performance bottleneck somewhere making normal I/O really slow. The underlying filesystems are all ext3, and the selected disk controller is SATA if that is important :) Best regards, Chris |
|||
| #2051 | fixed | vboxdrv and vboxnet don't automatically start with SabayonLinux | ||
| Description |
The files /etc/init.d/vboxdrv and /etc/init.d/vboxnet don't work with SabayonLinux. SabayonLinux contains both /etc/gentoo-release and /etc/sabayon-release files which confuses the vboxdrv and vboxnet scripts so they think that the OS is gentoo instead of sabayonlinux. The error produced by running either of these scripts is /etc/init.d/vboxdrv: line 97: /sbin/functions.sh: No such file or directory. This is because the functions.sh file, which in gentoo is placed in the /sbin/ folder, in SabayonLinux it is contained in the /lib/rc/sh/ folder, with a link from the /etc/init.d/ folder. E.g. /etc/init.d/functions.sh -> /lib/rc/sh/functions.sh. When the file VirtualBox-1.6.6-Linux_amd64.run is run, it reports that the vboxdrv module failed to be built. However, this is incorrect. It is built, but to load the modules you have to do it manually E.g modprobe vboxdrv. The /etc/init.d/vboxnet script, however, cannot be run manually. I have attached the vboxdrv and vboxnet scripts that I changed to recognize the SabayonLinux OS. However, they still don't launch automatically, even after adding them by using the rc-update add command. I don't think that either /etc/init.d/vboxdrv or /etc/init.d/vboxnet scripts work with openrc-0.2.5-r1 or baselayout-2.0.0 that SabayonLinux uses in it's latest 3.5 release. Hope this can be fixed soon. |
|||

