On Tue, 16 Apr 2013 09:08:12 +0200
Markus Armbruster wrote:
> Amos Kong writes:
>
> > (qemu) sendkey ctrl_r-scroll_lock-scroll_lock
> >
> > Executing this command could not let Windows guest panic, it caused by
>
> "could not"?
You can use Windows' editor to setup Windows to panic on a key se
On Tue, 16 Apr 2013 13:47:32 +0800
Amos Kong wrote:
> (qemu) sendkey ctrl_r-scroll_lock-scroll_lock
>
> Executing this command could not let Windows guest panic, it caused by
> the wrong order of releasing keys. This problem was introduced by
> commit e4c8f004c55d9da3eae3e14df740238bf805b5d6.
>
Amos Kong writes:
> (qemu) sendkey ctrl_r-scroll_lock-scroll_lock
>
> Executing this command could not let Windows guest panic, it caused by
"could not"?
> the wrong order of releasing keys. This problem was introduced by
> commit e4c8f004c55d9da3eae3e14df740238bf805b5d6.
>
> The right release
(qemu) sendkey ctrl_r-scroll_lock-scroll_lock
Executing this command could not let Windows guest panic, it caused by
the wrong order of releasing keys. This problem was introduced by
commit e4c8f004c55d9da3eae3e14df740238bf805b5d6.
The right release order should be starting from last item.
Signe