Custom Query (16363 matches)
Results (1696 - 1698 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #1602 | duplicate | Wish for better support for virtual machnines with text console | ||
| Description |
This is a wish for VirtualBox enhancement. Text console in guest virtual machnine can be too small on monitor with high resolution. For example, I run MS-DOS virtual machine, it has display only 25x80 character and virtual machnine output is too small to read at screen with high resolution. I cannot increse output from virtual machine, as it maps video memory of virtual machine in ratio 1:1. When I switch to full screen, I see a lo of black space and in the middle of the screnn is small arrea with virtual machine screen, in the same size; no real advantage of full screen output. I think it can be improved, that you can (optionaly) map 1 pixel from VirtualMachine videoram to 1 (1x1), 4 (2x2) or 9 (3x3) pixels in host screen; can be configurable (auto, 1x, 2x, 3x, manual when window is resized). To implement something like magnifier. It is not difficult from my point of view. More advanced solution will alow to have full smooth screen resizing between ratio 1x to 4x; some interpolation has to be used in this case and it will have impact to performance of VirtualMachine. From my point of view smoth resizing is not necessary. |
|||
| #1603 | fixed | mount vboxsf filesystems automatically => Fixed in 1.6.2 | ||
| Description |
Please add code like the following to /etc/init.d/vboxvfs inside a Linux guest. This will mount and umount the 'vboxsf' filesystems mentioned in /etc/fstab whenever the vboxvfs kernel module is inserted or removed. Thanks. --- vboxvfs-ORG 2008-05-22 17:24:00.000000000 +0200
+++ vboxvfs 2008-05-23 16:14:16.000000000 +0200
@@ -140,16 +140,21 @@
fail "modprobe $modname failed"
}
}
+ # Now we can mount vboxsf filesystems mentioned in /etc/fstab
+ mount -a -t vboxsf
+
succ_msg
return 0
}
stop() {
begin "Stopping VirtualBox Additions shared folder support ";
- if running; then
- rmmod $modname || fail "Cannot unload module $modname"
- fi
- succ_msg
+ # must umount vboxsf filesystems first
+ umount -a -t vboxsf &&
+ if running; then
+ rmmod $modname || fail "Cannot unload module $modname"
+ fi &&
+ succ_msg
return 0
}
|
|||
| #1604 | wontfix | Shared Folders: Windows NT4 SP6 guest on Windows XP SP3 host. | ||
| Description |
According to the changelog: Shared Folders: made them work for NT4 guests But it did not work. After a fresh install of NT4 + SP6 + guest additions, the mouse integration was OK. Display enhancement was OK, but Shared Folders was not. The usual "net use X: \vboxsvr\..." command reported "System Error 53." I clicked Control Panel -> Devices, and "VirtualBox Shared Folders" entry was there, but wasn't started. When I tried to start it, I saw this: The C:\Windows\System32\drivers\VBoxSFNT.sys device driver could not locate the entry point ExFreePoolWithTag in driver ntoskrnl.exe" |
|||

