On 17/09/20 19:44, Dr. David Alan Gilbert wrote: >> This may happen with an older machine type when the destination is >> running an unfixed QEMU and the source has the fix, right? > Yes I think so. > >> The solution >> would be to introduce a flag for older machine types (or for new ones) >> like 'kvmclock_always'. > Yep sounds the normal answer. > (You might want to try it first to trigger the bug) >
Right -- unqueued it :) Paolo
