HostedEngine:
......
<model fallback='forbid'>Haswell-noTSX</model>
......

both of the hosts:
......
<model>Westmere</model>
......

others vms which can be migrated:
......
<model fallback='forbid'>Haswell-noTSX</model>
......



在 2020-09-17 03:03:24,"Strahil Nikolov" <hunter86_bg@yahoo.com> 写道: >Can you verify the HostedEngine's CPU ? > >1. ssh to the host hosting the HE >2. alias virsh='virsh -c qemu:///system?authfile=/etc/ovirt-hosted-engine/virsh_auth.conf' >3. virsh dumpxml HostedEngine > > >Then set the alias for virsh on all Hosts and 'virsh capabilites' should show the Hosts' <cpu><model> . > >Best Regards, >Strahil Nikolov > > > > > > >В сряда, 16 септември 2020 г., 10:16:08 Гринуич+3, ddqlo <ddqlo@126.com> написа: > > > > > >My gateway was not pingable. I have fixed this problem and now both nodes have a score(3400). >Yet, hosted engine could not be migrated. Same log in engine.log: >host filtered out by 'VAR__FILTERTYPE__INTERNAL' filter 'CPU' > > >在 2020-09-16 02:11:09,"Strahil Nikolov" <hunter86_bg@yahoo.com> 写道: >>Both nodes have a lower than the usual score (should be 3400 ). >>Based on the score you are probably suffering from gateway-score-penalty [1][2]. >>Check if your gateway is pingable. >> >>Best Regards, >>Strahil Nikolov >> >>1 - https://www.ovirt.org/images/Hosted-Engine-4.3-deep-dive.pdf(page 8) >>2 - /etc/ovirt-hosted-engine-ha/agent.conf  >> >> >> >> >> >> >>В вторник, 15 септември 2020 г., 04:49:48 Гринуич+3, ddqlo <ddqlo@126.com> написа: >> >> >> >> >> >>--== Host node28 (id: 1) status ==-- >> >>conf_on_shared_storage             : True >>Status up-to-date                  : True >>Hostname                           : node28 >>Host ID                            : 1 >>Engine status                      : {"reason": "vm not running on this host", "health": "bad", "vm": "down_unexpected", "detail": "unknown"} >>Score                              : 1800 >>stopped                            : False >>Local maintenance                  : False >>crc32                              : 4ac6105b >>local_conf_timestamp               : 1794597 >>Host timestamp                     : 1794597 >>Extra metadata (valid at timestamp): >>        metadata_parse_version=1 >>        metadata_feature_version=1 >>        timestamp=1794597 (Tue Sep 15 09:47:17 2020) >>        host-id=1 >>        score=1800 >>        vm_conf_refresh_time=1794597 (Tue Sep 15 09:47:17 2020) >>        conf_on_shared_storage=True >>        maintenance=False >>        state=EngineDown >>        stopped=False >> >> >>--== Host node22 (id: 2) status ==-- >> >>conf_on_shared_storage             : True >>Status up-to-date                  : True >>Hostname                           : node22 >>Host ID                            : 2 >>Engine status                      : {"health": "good", "vm": "up", "detail": "Up"} >>Score                              : 1800 >>stopped                            : False >>Local maintenance                  : False >>crc32                              : ffc41893 >>local_conf_timestamp               : 1877876 >>Host timestamp                     : 1877876 >>Extra metadata (valid at timestamp): >>        metadata_parse_version=1 >>        metadata_feature_version=1 >>        timestamp=1877876 (Tue Sep 15 09:47:13 2020) >>        host-id=2 >>        score=1800 >>        vm_conf_refresh_time=1877876 (Tue Sep 15 09:47:13 2020) >>        conf_on_shared_storage=True >>        maintenance=False >>        state=EngineUp >>        stopped=False >> >> >> >> >> >> >> >>在 2020-09-09 01:32:55,"Strahil Nikolov" <hunter86_bg@yahoo.com> 写道: >>>What is the output of 'hosted-engine --vm-status' on the node where the HostedEngine is running ? >>> >>> >>>Best Regards, >>>Strahil Nikolov >>> >>> >>> >>> >>> >>> >>>В понеделник, 7 септември 2020 г., 03:53:13 Гринуич+3, ddqlo <ddqlo@126.com> написа: >>> >>> >>> >>> >>> >>>I could not find any logs because the migration button is disabled in the web UI. It seems that the engine migration operation is prevented at first. Any other ideas? Thanks! >>> >>> >>> >>> >>> >>> >>> >>>在 2020-09-01 00:06:19,"Strahil Nikolov" <hunter86_bg@yahoo.com> 写道: >>>>I'm running oVirt 4.3.10 and I can migrate my Engine from node to node. >>>>I had one similar issue , but powering off and on the HE has fixed it. >>>> >>>>You have to check the vdsm log on the source and on destination in order to figure out what is going on. >>>>Also you might consider checking the libvirt logs on the destination. >>>> >>>>Best Regards, >>>>Strahil Nikolov >>>> >>>> >>>> >>>> >>>> >>>> >>>>В понеделник, 31 август 2020 г., 10:47:22 Гринуич+3, ddqlo <ddqlo@126.com> написа: >>>> >>>> >>>> >>>> >>>> >>>>Thanks! The scores of all nodes are not '0'. I find that someone has already asked a question like this. It seems that  this feature has been disabled in 4.3. I am not sure if it is enabled in 4.4. >>>> >>>> >>>>在 2020-08-29 02:27:03,"Strahil Nikolov" <hunter86_bg@yahoo.com> : >>>>>Have you checked under a shell the output of 'hosted-engine --vm-status' . Check the Score of the hosts. Maybe there is a node with score of '0' ? >>>>> >>>>>Best Regards, >>>>>Strahil Nikolov >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>>В вторник, 25 август 2020 г., 13:46:18 Гринуич+3, 董青龙 <ddqlo@126.com> написа: >>>>> >>>>> >>>>> >>>>> >>>>> >>>>>Hi all, >>>>>        I have an ovirt4.3.10.4 environment of 2 hosts. Normal vms in this environment could be migrated, but the hosted engine vm could not be migrated. Anyone can help? Thanks a lot! >>>>> >>>>>hosts status: >>>>> >>>>>normal vm migration: >>>>> >>>>>hosted engine vm migration: >>>>> >>>>> >>>>> >>>>>  >>>>>_______________________________________________ >>>>>Users mailing list -- users@ovirt.org >>>>>To unsubscribe send an email to users-leave@ovirt.org >>>>>Privacy Statement: https://www.ovirt.org/privacy-policy.html >>>>>oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ >>>>>List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/ZXHE2AJX42HNHOMYHTDCUUIU3VQTQTLF/ >>>> >>>> >>>> >>>> >>>>  >>>>_______________________________________________ >>>>Users mailing list -- users@ovirt.org >>>>To unsubscribe send an email to users-leave@ovirt.org >>>>Privacy Statement: https://www.ovirt.org/privacy-policy.html >>>>oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ >>>>List Archives: >>>>https://lists.ovirt.org/archives/list/users@ovirt.org/message/IAYLFLC6K42OUPZSZU3P3ZYAU66LGSCD/ >>> >>> >>> >>> >>>  >>>_______________________________________________ >>>Users mailing list -- users@ovirt.org >>>To unsubscribe send an email to users-leave@ovirt.org >>>Privacy Statement: https://www.ovirt.org/privacy-policy.html >>>oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ >>>List Archives: >>>https://lists.ovirt.org/archives/list/users@ovirt.org/message/23ZMAP5K7N5KKX3HOKUEJNVCBH7CY4ZL/ >> >> >> >> >>  > > > > >