Custom Query (16363 matches)
Results (2182 - 2184 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #184 | fixed | Invisible Cursor In Fullscreen Mode | ||
| Description |
Using WindowsXP as the host and Ubuntu 6.10 as the guest machine, my cursor is invisible in fullscreen modes higher than 1024x768. My guest machine (Windows XP) resolution is set to 1152x864. When attempting to run Ubuntu at fullscreen using 1152x864 and the vboxvideo device in xorg.conf, my cursor disappeared but mouse functionality remained. I was able to duplicate the same behavior using the vesa device at the same resolution. I resolved the issue of the disappearing cursor by starting the virtual machine in fullscreen, booting into Gnome, switching to VirtualBox windowed mode, logging out of Gnome and restarting the X server...at this point when VirtualBox regains mouse control the cursor is visible and I can switch to fullscreen resolution while maintaining the visibility of the cursor. After this workaround, the mouse works perfectly. |
|||
| #14089 | fixed | vboxsf module crashes during high load => Fixed in SVN / 6.0.6 | ||
| Description |
I was able to reproduce a vboxsf crash twice whilst running "npm install" on a shared directory, which triggers a lot of different file activity (create/link/read/syay etc).
My guest machine is;
My host machine is; |
|||
| #3783 | fixed | OSX Bridged Networking unreliable due to incorrect MTU setting! => Fixed in SVN | ||
| Description |
I setup a clean install of XP SP2 on VirtualBox on my new MacPro. I setup the network adapter (Intel Pro 1000 T Server) with Bridged mode. After getting into XP, I was getting an IP address from my router and a few websites would load, but others would not. For example google.com was OK but mozilla.com and microsoft.com would not load. Some experimenting pointed to an MTU issue. I determined this WAS due to the MTU setting. My testing showed that when using Bridged Mode and performing "ping -f" to my home network router, I could see that setting the ping packet size (-l flag) larger than 1467 caused the packets to timeout, and a size over 1472 to get the expected "Packet needs to be fragmented but DF set." When using an adaptor in NAT mode, this problem does not occur, and pings up to 1472 in size are allowed as expected. Setting the MTU lower in Windows XP registry and rebooting provides a workaround, and allows all websites and pages to load OK again. It's clear something about using Bridged mode is "padding" the packets with an additional 4 or 5 bits of data... For reference Windows XP's registry key for MTU size: System Key: [HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\[Adapter ID]] Value Name: MTU Data Type: REG_DWORD (DWORD Value) |
|||

