> On 28 Mar 2017, at 13:41, Jiří Sléžka <jiri.slezka@slu.cz> wrote:
>
> On 03/28/2017 12:34 AM, Jiří Sléžka wrote:
>> Hi all,
>>
>> I have just upgraded ovirt manager from 4.1.0 to 4.1.1, then I have
>> upgraded one host. After reboot and activation of this host some vms
>> started to migrate here.
>>
>> Some time after migration CPU of this vms go to 100% and vms become
>> unreachable.
>>
>> There is /var/log/libvirt/qemu/hypnos.log (hypnos is one of this vms)
>> https://pastebin.com/U30xfBMJ
>>
>> Powering off and starting again solve this but I would like to have a
>> glue what is happening.
>>
>> I suspect this line
>>
>> 2017-03-27T22:09:23.746710Z qemu-kvm: warning: TSC frequency mismatch
>> between VM (2600031 kHz) and host (2100024 kHz), and TSC scaling unavailable
>>
>> Original host uses "AMD Opteron(TM) Processor 6238" with "cpu MHz:
>> 2600.113" and upgraded host uses "AMD Opteron(tm) Processor 6172" with
>> "cpu MHz: 2100.097".
>
> It looks like it isn't problem with 4.1.1 at all.
>
> There is just missing tsc_scale cpu flag on our older AMD CPUs...
>
> http://unix.stackexchange.com/questions/296636/100-cpu-utilisation-and-hang-after-virsh-migrate
>
> This is probably unsolvable hw problem, right?

And this is without host-model CPU type?
That 6172 should be Opteron G3…is that what you have set in your Cluster?

Thanks,
michal