> On 7 Jun 2018, at 15:52, [email protected] wrote:
> 
> Hello,
> 
> I ran into a similar error.
> After updating the management to oVirt Manager: CentOS 7.5  ovirt: 
> 4.2.3.8-1.el7
> I tried to put the 1st host into maintenance mode to do the update. Since ~ 
> 4h, the server tries to migrate all of the VMs without success.
> On the 'reception' host /var/log/libvirt/qemu shows following error:
> 2018-06-07T12:57:54.420311Z qemu-kvm: warning: CPU(s) not present in any NUMA 
> nodes: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
> 2018-06-07T12:57:54.420483Z qemu-kvm: warning: All CPU(s) up to maxcpus 
> should be described in NUMA config

these are not errors, just warns, unrelated

> 2018-06-07 13:00:03.692+0000: shutting down, reason=failed

what does it say on the source host?

> 
> physical Host:
> OS-Version:RHEL - 7 - 4.1708.el7.centos
> Kernelversion: 3.10.0 - 693.21.1.el7.x86_64
> KVM-Version: 2.9.0 - 16.el7_4.14.1
> LIBVIRT-Version: libvirt-3.2.0-14.el7_4.9
> VDSM-Version:vdsm-4.19.45-1.el7.centos

both hosts are exactly the same?
When was the original VM started, did you make any upgrades while it was 
running, perhaps a long time ago?

Thanks,
michal

> Kernel Features:PTI: 1, IBPB: 0, IBRS: 0
> 
> Hans-Joachim 
> _______________________________________________
> Users mailing list -- [email protected]
> To unsubscribe send an email to [email protected]
> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> oVirt Code of Conduct: 
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives: 
> https://lists.ovirt.org/archives/list/[email protected]/message/GT7WNZNMWV5SBRC3YWGS6D3LZACFXG7B/
_______________________________________________
Users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/[email protected]/message/7PA445NXNKFQJ45J377DXF2QGAXQBXB2/

Reply via email to