After reboot of host and guest of KVM, the bug disappeared for the moment