On 18/10/2018 09:12, Artem Pisarenko wrote:
> +To even prevent it from progressing during suspension, you can set it to
> +@code{vm} (virtual clock). Virtual clock is the clock seen by guest,
> +In icount mode of emulation its (long term) speed will be different from
> +any host clock, when icount configured to non-auto value or virtual cpu
> sleeping
> +is off, and no synchronization algorithm is active.
>
Slight rephrasing:
To even prevent the RTC from progressing during suspension, you can set
@option{clock} to @code{vm} (virtual clock). @samp{clock=vm} is
recommended especially in icount mode in order to preserve determinism;
however, note that in icount mode the speed of the virtual clock is
variable and can in general differ from the host clock.
(omitting the reference to -icount auto etc.)
Paolo
