Changes between Initial Version and Version 1 of Ticket #14302, comment 29
- Timestamp:
- Mar 7, 2016 9:33:14 AM (8 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #14302, comment 29
initial v1 3 3 Issue 1: a VM that starts in the background, affects the host LEDs state, even if the VM starts in the background (it must have something to do with the hardening process, the VM window never gets created in focus), while another host application window is in focus and it has continuous user keyboard input. See comment 3. Assuming the host has the NumLock key toggled on, test the issue by continuously pressing a keyboard keypad key in the host's text editor (e.g. pressing keypad key '4'), while the VM start.bat script starts and closes the VM in the background (assuming the VM starts with NumLock toggled off). 4 4 5 Issue 2: If the Windows host is put to sleep (S3) while a VM is running, if this VM's window was the the last window that was active (in focus), after resuming the host, the host key state is set to the last guest's key state. Example (see the attached Vbox.log ), where the host had only NumLock toggled on and the guest had only ScrollLock toggled on. There are events (setfocus and killfocus) that the VM window gets right before the host enters sleep or right after it resumes.5 Issue 2: If the Windows host is put to sleep (S3) while a VM is running, if this VM's window was the the last window that was active (in focus), after resuming the host, the host key state is set to the last guest's key state. Example (see the attached Vbox.log, it contains extra logging for the GUI group), where the host had only NumLock toggled on and the guest had only ScrollLock toggled on. There are events (setfocus and killfocus) that the VM window gets right before the host enters sleep or right after it resumes. 6 6 7 7 Issue 3: this might be intentional, but a VM with nothing to boot (displaying the "FATAL: no bootable medium found! System halted") forgets the guest key state when the window looses then regains focus. I think this is what Suncatcher_13 referred to in comment 26 issue 2. Maybe the VM should also check if the VM is halted, not to switch the key state.
