Custom Query (16363 matches)
Results (490 - 492 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #4411 | obsolete | Java and Xorg constant process activity renders Solaris guest unuseable | ||
| Description |
On 32-bit WinXP host with VT-x disabled for VM, Solaris 10 u7 32-bit guest is unusable because of constant java and Xorg process activity. No user processes running. 3.0.0 Solaris guest additions installed. |
|||
| #4417 | obsolete | Mouse area restricted under VB 3 and OpenGL | ||
| Description |
I'm not sure where this belongs ... I've setup a Windows XP (SP3) guest in VB 2.2.4, and successfully used the Half-Life I into it in full-screen OpenGL 800x600 mode, inside a Vista Ultimate SP1 x64 host (old Opterons, no VT instructions). I've switched to VB 3 to check the Direct3D support (it's looks terrible, but that's not what this bug is about). Since I couldn't use Direct3D, I tried the OpenGL again, and there seems to be some new bug with the mouse. In Half-Life, you don't have a mouse pointer, but a cross showing where you aim, and the mouse can control where you look. When using the mouse, it's like if it hits a wall on the right side at about 3/4 of the way, so I can't use the mouse to turn right. By moving the mouse slightly back to the left, and then far to the right, I can turn a bit more right, and eventually point where I want. It's like if the scroll area of the mouse is smaller the the actual screen resolution. |
|||
| #4422 | obsolete | USB WiFi Networking Conflict | ||
| Description |
On a WindowsXP host using wifi as its primary network connection (Realtek 8187B operating as a USB device), merely starting the VirtualBox application kills the host network. Disabling the "VirtualBox USB Monitor Driver" device in the WinXP device manager (as per workaround in http://www.virtualbox.org/ticket/1712) prevents the VirtualBox application from killing the host network. However, this precludes all but NAT networking for VirtualBox guests, and presumably breaks USB for guests. I confirm this bug is still present in VirtualBox 3.0.0. The first report of this bug was over 2 years ago in version 1.6.x (see http://www.virtualbox.org/ticket/845). The original workaround in that report (restarting host network adapter) does not work in 3.0.0. |
|||

