> On 7 Jun 2018, at 11:27, Balg, Andreas <[email protected]> wrote: > > > Hello, > > during updates of our physical nodes running ovirt 4.2.3 I had to live- > migrate all VMs to evacuate them from the hosts. This caused roughly > 10% of guests to end up crashed /shutdown after live migration. > > Errors in the Logs are: > > 2018-05-31T15:15:51.273805Z qemu-kvm: warning: All CPU(s) up to maxcpus > should be described in NUMA config, ability to start up with partial > NUMA mappings is obsoleted and will be removed in future > 2018-05-31T15:16:54.596554Z qemu-kvm: Unknown combination of migration > flags: 0 > 2018-05-31T15:16:54.597196Z qemu-kvm: error while loading state section > id 3(ram) > 2018-05-31T15:16:54.598491Z qemu-kvm: load of migration failed: Invalid > argument > 2018-05-31 15:16:55.010+0000: shutting down, reason=crashed
this is typically due to using some unsupported version. Can you include the whole qemu log and versions from both source and destination hypervisors, and verify there were no updates run while that VM was running? Thanks, michal > > > is there anything I can do about this? The hardware of all nodes is > 100% identical > > > -- > Andreas Balg > _______________________________________________ > 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/MCC47Y52B2NUB2GDTHDLCWUMR2FH2Q2C/ _______________________________________________ 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/5EE3BTMTYXKFDDSJCZXHISGC2ZB3HWAL/
