Custom Query (16363 matches)
Results (1300 - 1302 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #7300 | fixed | Guru meditation with large pages (pgmPoolTrackPhysExtDerefGCPhys) => Fixed in SVN | ||
| Description |
Guest: Windows 2008 R2 x64 Runs fine without large pages enabled, Guru meditation when booting guest after enabling large pages. |
|||
| #11018 | worksforme | Guest mouse not working | ||
| Description |
Hello, i recently installed VirtualBox 4.2.0 [and its extension pack] in order to run an OSX mountain lion guest on it. My OS [host type] is Windows 7, SP1, 64bit. i have a logitech cordless set [keyboard+mouse]. the keyboard model is: mk700, the mouse model is: mx620. whenever i try launching the virtual machine, and get to the boot screen, if i try clicking anywhere on the screen, i get promoted with a message about capturing the host mouse cursor. after clicking the "accept" button, the mouse cursor disappears and i cannot control the mouse, until i press the right control key to uncapture it. the keyboard is working, but the mouse is not recognized. since my set is connected via USB, i tried selecting the set in the USB devices list inside the VM, but whenever i choose the logitech cordless set, my keyboard and mouse stop responding within the VM, and the only way i can uncapture them is to physically remove the usb and plug it back again. |
|||
| #4152 | obsolete | VRDP screen flicker | ||
| Description |
Version 2.2.4 on Ubuntu 9.04 64 bit host running Windows XP 32 bit guest. On host there is no anomaly - everything is as expected (and same as in version 2.2.2). I start the guest. When I connect from a Windows XP machine via Remote Desktop Connection (default port, NULL authentication), the following happens: The screen appears normally with the Windows login prompt. Once I get past the login prompt and the desktop appears, the screen starts flickering on the remotely connected machine as well as on the Ubuntu host. The same setup was working perfectly in version 2.2.2. The 2.2.4 changelog states that a rare incorrect screen update was fixed - in my case an incorrect screen update is happening now. |
|||

