Opened 12 years ago
Closed 10 years ago
#11975 closed defect (fixed)
send SysRq key to linux guest (fixed in 4.3)
Reported by: | Leo | Owned by: | |
---|---|---|---|
Component: | guest control | Version: | VirtualBox 4.2.16 |
Keywords: | Cc: | ||
Guest type: | other | Host type: | other |
Description
Sending the SysRq key from host to guest doesn't work. (Tested on a windows and on a linux host with three different linux guests.)
send CTRL + ALT + SysRq + s
Host:
$ VBoxManage controlvm CD-Boot keyboardputscancode 1d 38 54 1f 9f d4 b8 9d
Guest:
# showkey kb mode was UNICODE [ if you are trying this under X, it might not work since the X server is also reading /dev/console ] press any key (program terminates 10s after last keypress)... keycode 28 release keycode 29 press keycode 56 press keycode 31 press keycode 31 release keycode 56 release keycode 29 release
(The SysRq key (scancode 0x54 = 84 dec) is missing.)
send just SysRq (press and release)
Host:
$ VBoxManage controlvm CD-Boot keyboardputscancode 54 9d
Guest:
# showkey kb mode was UNICODE [ if you are trying this under X, it might not work since the X server is also reading /dev/console ] press any key (program terminates 10s after last keypress)... keycode 28 release
sending ALT (dec 56) + SysRq in the VBox console window
Guest:
# showkey kb mode was UNICODE [ if you are trying this under X, it might not work since the X server is also reading /dev/console ] press any key (program terminates 10s after last keypress)... keycode 28 release keycode 56 press keycode 56 release keycode 56 press keycode 99 press keycode 99 release keycode 56 release
Change History (3)
comment:1 by , 11 years ago
comment:2 by , 10 years ago
At least example 1 (CTRL + ALT + SysRq + s) works now with VirtualBox 4.3.12. Thanks!
comment:3 by , 10 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Summary: | send SysRq key to linux guest → send SysRq key to linux guest (fixed in 4.3) |
OK, let's close this then... if there are remaining problems with the SysRq key, this ticket can of course be re-opened with detailed description of what's wrong.
Note:
See TracTickets
for help on using tickets.
Please check if this still occurs with the current VirtualBox 4.3 release.
You also probably realize that the second example is bogus, perhaps you meant '54 d4' instead of '54 9d'?