Description of problem:

The destination domain will be in paused status during virtual machine live migration. However, it looks like virt-launcher is continuously trying to set the guest time when the VM is paused and results in the below events every second.

~~~

{"component":"virt-launcher","kind":"","level":"warning","msg":"failed to sync guest time","name":"rhel8-organisational-pony","namespace":"nijin-cnv","pos":"manager.go:261","reason":"virError(Code=55, Domain=10, Message='Requested operation is not valid: domain is not running')","timestamp":"2022-03-15T07:16:14.786101Z","uid":"31323a86-8f9d-425b-aec9-5ac514e8279d"} {"component":"virt-launcher","kind":"","level":"warning","msg":"failed to sync guest time","name":"rhel8-organisational-pony","namespace":"nijin-cnv","pos":"manager.go:261","reason":"virError(Code=55, Domain=10, Message='Requested operation is not valid: domain is not running')","timestamp":"2022-03-15T07:16:15.785591Z","uid":"31323a86-8f9d-425b-aec9-5ac514e8279d"} {"component":"virt-launcher","kind":"","level":"warning","msg":"failed to sync guest time","name":"rhel8-organisational-pony","namespace":"nijin-cnv","pos":"manager.go:261","reason":"virError(Code=55, Domain=10, Message='Requested operation is not valid: domain is not running')","timestamp":"2022-03-15T07:16:16.794454Z","uid":"31323a86-8f9d-425b-aec9-5ac514e8279d"}

~~~

The error is expected from the libvirtd when the VM is paused:

~~~
virsh -r list |grep -i nijin_test_2
5 nijin_test_2 paused

virsh domtime nijin_test_2 --now
error: Requested operation is not valid: domain is not running
~~~

Version-Release number of selected component (if applicable):

kubevirt-hyperconverged-operator.v4.9.3

How reproducible:

100%

Steps to Reproduce:

1. Live migrate a virtual machine.
2. Watch for the logs in the destination virt-launcher pod.

Actual results:

"failed to sync guest time" log spam in destination virt-launcher pod during VM live migration

Expected results:

These logs spam the destination virt-launcher pod and hence I think shouldn't be logged during the migration.

Additional info: