Custom Query (16363 matches)
Results (1564 - 1566 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #8668 | obsolete | Problems with mouse in guest, secondary monitor and disabled mouse integration -> working after 4.3.10, please open new bugs for new issues | ||
| Description |
On host, two monitors, configured in extended desktop mode (e.g. I have one desktop spanning across two monitors) I have a guest OS that does not support guest addons (Linux based Android x86). The mouse integration is disabled in the guest settings. When I move the guest VM window to my secondary monitor, the mouse capturing functioniality starts acting realy weard (e.g. when I click inside the guest VM window to capture the mouse point, the mouse pointer appers on the host in the left/top position on the primary monitor, and the movement of the mouse cursor in the guest window stops and/or is erratic). Everything works fine as long as my guest VM window is on the primary monitor. Host OS is Windows 7 x64. |
|||
| #8674 | obsolete | 3D app reboots the guest OS if display is scaled | ||
| Description |
Only tested with a Windows XP guest: If VirtualBox is in Scale mode (Host+C) with 3D acceleration enabled, and a 3D app (in my case, StepMania 3.9a) is launched, the guest OS spontaneously reboots. Obviously, it would (probably) be quite difficult for VirtualBox to actually scale 3D accelerated output, so I'm not asking that this be made possible. Instead, it should probably stop the guest OS from creating the surface in the first place and return the same as it would if 3D acceleration were not enabled. (And if you want to know why I installed StepMania in a virtual machine, I was curious as to what the embedded OpenCandy code in the installer would do to the machine. I wasn't seriously wanting to play it. And then I was curious as to how it intersected with Scale mode, and bang, here's the bug :)) My host OS is Windows 7, with up-to-date drivers for my ATI Mobility Radeon HD 5650, and with Aero enabled, and I'm using VirtualBox 4.0.4. |
|||
| #8678 | obsolete | guest window size is ignored | ||
| Description |
Using a guest window with smaller size than the guest desktop (using scrollbars to access the different areas of the guest desktop) is not honoured between restarts. Setting a smaller window size on a 1600x1200 guest and shutting it down results in this data in the virtual machine xml file: <ExtraDataItem name="GUI/LastNormalWindowPosition" value="4,20,985,785"/> The above looks fine, but when starting up the guest again, it expands to a larger size and updates the stored window position to this larger size (noticeable after shutting down again): <ExtraDataItem name="GUI/LastNormalWindowPosition" value="4,20,1592,1155"/> Ticket #7042 is probably a related bug, where the guest window size is lost on every switch in and out of fullscreen. |
|||

