Hi, So it seems we have a bug regarding the new vmx features when computing baseline CPU model. But it seems it's not the only thing... On Fri, May 24, 2024 at 01:20:32 +0800, d tbsky wrote: > Next test I add "vmx" feature to vm config(so it will look lik RHEL > 9.3 config). the xml are the same at both cpu. live migration failed > at both direction and error message are the same: "guest CPU doesn't > match specification: missing features: > vmx-apicv-register,vmx-apicv-vid,vmx-posted-intr". we can see these > features were disabled at running xml. > > running xml below: > <cpu mode="custom" match="exact" check="full"> > <model fallback="forbid">Haswell-noTSX-IBRS</model> > <vendor>Intel</vendor> > <topology sockets="1" dies="1" clusters="1" cores="1" threads="1"/> > <maxphysaddr mode="passthrough" limit="39"/> ... > <feature policy="disable" name="vmx-apicv-register"/> > <feature policy="disable" name="vmx-apicv-vid"/> ... > <feature policy="disable" name="vmx-posted-intr"/> ... > </cpu> Oh, are you saying that a domain with such active XML cannot be migrated and you see these three features reported as missing? Could you please provide debug logs from virtqemud (or libvirtd if you're running monolithic daemon) from both sides of migration covering the failed attempt? See https://libvirt.org/kbase/debuglogs.html for steps required to enable debug logs. Thanks, Jirka
