But I see another problem, I can't migrate server back for old-host with error:
Instance launched has CPU info: {"arch": "x86_64", "model":
"Cascadelake-Server", "vendor": "Intel", "topology": {"cells": 2, "sockets": 1,
"cores": 12, "threads": 2}, "features": ["ss", "invpcid", "vme", "sse4.2",
"acpi", "cx8", "ssse3", "adx", "clflush", "f16c", "pge", "avx512dq", "bmi1",
"tsc", "invtsc", "dtes64", "xtpr", "pschange-mc-no", "movbe", "lm", "nx",
"xsaves", "fpu", "spec-ctrl", "xsave", "avx2", "stibp", "sse2", "msr",
"rdrand", "avx512vl", "ht", "avx512f", "ds", "pcid", "smap", "pni", "arat",
"x2apic", "vmx", "tm", "tsc-deadline", "fxsr", "cx16", "ssbd", "pat",
"avx512cd", "ds_cpl", "abm", "lahf_lm", "mca", "ibrs-all", "sep", "xsavec",
"pse36", "sse4.1", "pse", "erms", "skip-l1dfl-vmentry", "smep", "fsgsbase",
"clflushopt", "tm2", "xsaveopt", "monitor", "apic", "mce", "dca", "pae", "avx",
"avx512vnni", "rdtscp", "smx", "tsc_adjust", "mtrr", "arch-capabilities",
"mmx", "mpx", "intel-pt", "3dnowprefetch", "avx512bw", "fma", "rdctl-no",
"pbe", "hle", "syscall", "pdcm", "rdseed", "pdpe1gb", "popcnt", "bmi2", "cmov",
"aes", "rtm", "est", "sse", "pclmuldq", "xgetbv1", "md-clear", "clwb", "pku",
"de"]}
CPU doesn't have compatibility. Refer to
http://libvirt.org/html/libvirt-libvirt-host.html#virCPUCompareResult
Exception during message handling: nova.exception.MigrationPreCheckError:
Migration pre-check error: Unacceptable CPU info: CPU doesn't have
compatibility. Refer to
http://libvirt.org/html/libvirt-libvirt-host.html#virCPUCompareResult
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/nova/virt/libvirt/driver.py", line
8402, in check_can_live_migrate_destination
self._compare_cpu(None, source_cpu_info, instance)
File "/usr/lib/python3/dist-packages/nova/virt/libvirt/driver.py", line
8772, in _compare_cpu
raise exception.InvalidCPUInfo(reason=m % {'ret': ret, 'u': u})
nova.exception.InvalidCPUInfo: Unacceptable CPU info: CPU doesn't have
compatibility.
virsh dumpxml instance
<cpu mode='custom' match='exact' check='full'>
<model fallback='forbid'>Cascadelake-Server</model>
<vendor>Intel</vendor>
<topology sockets='2' cores='1' threads='1'/>
<feature policy='require' name='ss'/>
<feature policy='require' name='vmx'/>
<feature policy='require' name='hypervisor'/>
<feature policy='require' name='tsc_adjust'/>
<feature policy='require' name='umip'/>
<feature policy='require' name='pku'/>
<feature policy='require' name='md-clear'/>
<feature policy='require' name='stibp'/>
<feature policy='require' name='arch-capabilities'/>
<feature policy='require' name='xsaves'/>
<feature policy='require' name='ibpb'/>
<feature policy='require' name='amd-stibp'/>
<feature policy='require' name='amd-ssbd'/>
<feature policy='require' name='skip-l1dfl-vmentry'/>
<feature policy='require' name='pschange-mc-no'/>
<feature policy='disable' name='avx512vnni'/>
<feature policy='disable' name='mpx'/>
<numa>
<cell id='0' cpus='0-1' memory='8388608' unit='KiB' memAccess='shared'/>
</numa>
</cpu>
Old host:
virsh domcapabilities |grep "Cascadelake-Server"
<model fallback='forbid'>Cascadelake-Server</model>
<model usable='no'>Cascadelake-Server-noTSX</model>
<model usable='no'>Cascadelake-Server</model>
New host:
virsh domcapabilities |grep "Cascadelake-Server"
<model fallback='forbid'>Cascadelake-Server</model>
<model usable='no'>Cascadelake-Server-noTSX</model>
<model usable='yes'>Cascadelake-Server</model>
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922907
Title:
Unable to use Skylake capability on Cascadelake server
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1922907/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
