VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (2374 - 2376 of 16363)

Ticket Resolution Summary Owner Reporter
#2304 invalid nat socks connector Imre Péntek
Description

If I figure out correctly the virtual network device "NAT" interprets individual outgoing packages and compiles them into a new TCP connection initiated by the physical machine. So it would be possible to attach a socks proxy for the nearer endpoint of the TCP connections. Also it would be useful for me.

#2305 worksforme Virtual Machine is not start Mikhail
Description
  • Arch Linux x86 32 bit;
  • kernel-2.6.26;
  • vbox-2.02.

When i try start the VM - virtual box failed to start the virtual machine, error:

VirtualBox kernel driver not installed. The vboxdrv kernel module was either not loaded or /dev/vboxdrv was not created for some reason. Re-setup the kernel module by executing '/etc/init.d/vboxdrv setup' as root. VBox status code: -4 (VERR_INVALID_HANDLE).

Result Code: NS_ERROR_FAILURE (0x80004005) Component: Console Interface: IConsole {d5a1cbda-f5d7-4824-9afe-d640c94c7dcf}

Kernel module vboxdrv is loaded, curent user added in group vboxusers, file /etc/init.d/vboxdrv is not found.

#2306 fixed where mouse is drawn on guest does not match mouse coordinates -> fixed in SVN Stéphane Charette
Description

I've observed this on Debian Etch 64-bit guest running on Ubuntu 8.04 64-bit host; VirtualBox 2.0.2.

With *some* guest screen resolutions (not all) the mouse seems to be drawn in the wrong location. Near the top of the screen, the mouse is OK. But as the mouse progresses through the Y axis towards the bottom of the screen, an offset appears between the drawn mouse and where X think the mouse is located. Near the bottom of the screen, I've seen a difference of maybe 100 pixels between the drawn mouse and where X thinks the mouse is located.

This is very obvious when dragging a window towards the bottom of the screen, or trying to click on a button located near the bottom of the screen. End result is you must click anywhere between 50 to 100 pixels "higher" than where you actually want to click.

Example resolution (/etc/X11/xorg.conf) where this problem does not happen: 1280x1024

Example resolutions where this problem occurs: 1400x940, 1152x864, 1200x950

Workaround: if I disable mouse integration then the mouse works fine.

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