Re: After restarted libvirtd service, live migration VM hit an issue 'Target CPU check default does not match source none'

On Mon, Jun 13, 2022 at 05:06:50 +, liang chaojun wrote: > Thanks Han for your quick response. > > 1. Virsh dumpxml VM from source host machine. > [cid:fd7f5b1f-8551-4bf8-ae1a-30c7b95065db@jpnprd01.prod.outlook.com] Next time, please, paste text as text rather than attaching a screenshot of a

Re: After restarted libvirtd service, live migration VM hit an issue 'Target CPU check default does not match source none'

On Sun, Jun 12, 2022 at 9:31 PM 梁朝军 wrote: > Hi All, > > BTW, don't send the email to any member of the mail list. It is not someone's duty to answer it. Just only send it to the mail list. > After restarted the libvirtd service on the source host, we start live > migration VM to destination

After restarted libvirtd service, live migration VM hit an issue 'Target CPU check default does not match source none'

Hi All, After restarted the libvirtd service on the source host, we start live migration VM to destination host and often hit an issue 'unsupported configuration: Target CPU check default does not match source none’ We don’t configure any special setting for CPU model when start VM and I thin

Re: After restarted libvirtd service, live migration VM hit an issue 'Target CPU check default does not match source none'

Thanks Han for your quick response. 1. Virsh dumpxml VM from source host machine. [cid:fd7f5b1f-8551-4bf8-ae1a-30c7b95065db@jpnprd01.prod.outlook.com] 2, Attachments are the CPU capability information from both source and destination host machine. 在 2022年6月13日，上午10:17，Han Han mailto:h...@redha