Hi,
> From what I can see the guest OS will read this bitmap when it first
> probes the virtio device, and never updates it. If so, then is it
> actually a problem if we don't preserve the same map across save/
> restore/migrate ?
virtio-input config space size isn't fixed, instead it'll take
On Tue, Sep 12, 2017 at 01:37:37PM +0100, Daniel P. Berrange wrote:
> Replace the keymap_qcode table with automatically generated
> tables.
>
> Missing entries in keymap_qcode now fixed:
>
> Q_KEY_CODE_ASTERISK -> KEY_KPASTERISK
> Q_KEY_CODE_KP_MULTIPLY -> KEY_KPASTERISK
> Q_KEY_CODE_STOP -
Replace the keymap_qcode table with automatically generated
tables.
Missing entries in keymap_qcode now fixed:
Q_KEY_CODE_ASTERISK -> KEY_KPASTERISK
Q_KEY_CODE_KP_MULTIPLY -> KEY_KPASTERISK
Q_KEY_CODE_STOP -> KEY_STOP
Q_KEY_CODE_AGAIN -> KEY_AGAIN
Q_KEY_CODE_PROPS -> KEY_PROPS
Q_KEY_C
