> On 30/10/2018 16:20, Gionatan Danti wrote: > > Hi Frediano, it really seems related to the NumLock state, because: > > > > - with client NumLock enabled and spice connected, chkdsk is skipped; > > - with client NumLock enabled but spice not connected, chkdsk is not > > skipped; > > - with client NumLock not enabled, chkdsk is not skipped. > > > > This behavior is consistent between two CentOS 7 hosts and > > Win2003/Win10/Win2016 as guests. I am using the spice client integrated > > within virt-manager. > > > > Any suggestion on how to avoid it (short that not using/connecting the > > Spice client)? > > > > Thanks. > > Hi all, > any suggestion on the matter? > > Thanks. > Beside turning off NumLock before rebooting any other quick one I don't have. In the current code the locks are synced from client to guest so if the guest change the locks (like during reboot as in this case) the client will try to revert back injecting keys. Frediano _______________________________________________ Spice-devel mailing list Spice-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/spice-devel