[ovirt-users] HE vm fails to migrate due to host CPU incompatibility even after changing cluster CPU type

Sandro Bonazzola sbonazzo at redhat.com
Wed Mar 8 12:02:27 UTC 2017


On Sat, Mar 4, 2017 at 12:04 PM, Stefano Stagnaro <
stefanos at prismatelecomtesting.com> wrote:

> Hi guys,
>
> I've started an oVirt 4.1 HE deployment on a Broadwell based server. Then
> I added to HE a second, older host based on Nehalem. I've downgraded the
> cluster CPU type to Nehalem to accommodate host2 and it finally reached
> score 3400. However, when I try to migrate HE vm it fails with the
> following error:
>
> 2017-03-03 20:19:51,814 ERROR (migsrc/b0d38435) [virt.vm]
> (vmId='b0d38435-5774-4ca9-ad24-70b57b5bc25d') unsupported configuration:
> guest and host CPU are not compatible: Host CPU does not provide required
> features: pclmuldq, fma, pcid, x2apic, movbe, tsc-deadline, aes, xsave,
> avx, fsgsbase, bmi1, hle, avx2, smep, bmi2, erms, invpcid, rtm, rdseed,
> adx, smap, 3dnowprefetch; try using 'Broadwell-noTSX' CPU model
> (migration:265)
>
> I believe the problem is in the HE vm XML where the cpu is still
> configured as Broadwell. how can I change this specific setting without
> losing the deployment? Please find all the relevant logs at the following
> link: https://www.dropbox.com/sh/njl9aofhdw10ses/AADf2Ql4GKVIKcbgLivbmjC2a
>
> Besides that, I believe this is a wrong behavior because HE should follow
> cluster properties (otherwise do not reach score 3400); do you believe is
> it worth opening a issue on bugzilla?
>

I would consider opening a BZ to track this. Adding some people who may
have some insight on the issue.



>
> Thank you,
> Stefano.
>
> _______________________________________________
> Users mailing list
> Users at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>



-- 
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/users/attachments/20170308/dc47bc02/attachment.html>


More information about the Users mailing list