Han Han
2022-Jun-13 02:17 UTC
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 ??? <jesonliang040705 at hotmail.com> wrote:> Hi All, > > BTW, don't send the email to any member of the mail list. It is notsomeone'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 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 > think it should be ?custom? mode by default . Furthermore , those two hosts > for doing live migration have almost the same capabilities as below. >Please provides the guest CPU XML, the CPU model of the src and the dst hosts: # virsh dumpxml YOUR_VM --inactive|xmllint --xpath //cpu - (VM is live) # virsh dumpxml YOUR_VM |xmllint --xpath //cpu - # virsh capabilities|xmllint --xpath //cpu -> It?s confused me why failed to check the cpu configuration after restart > libvitd service on source host? > > > > The libvirt version is 7.9.0, package: 1.el8 (Unknown, > 2021-11-28-22:35:11) private build > Host OS version : rhat8.4 > QEMU version: QEMU 5.1 private build > > Any comments are appreciated. > > > Thanks > >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://listman.redhat.com/archives/libvirt-users/attachments/20220613/9bdd8088/attachment-0001.htm> -------------- next part -------------- A non-text attachment was scrubbed... Name: ???? 2022-06-12 ??9.23.41.png Type: image/png Size: 96585 bytes Desc: not available URL: <http://listman.redhat.com/archives/libvirt-users/attachments/20220613/9bdd8088/attachment-0001.png>
liang chaojun
2022-Jun-13 05:06 UTC
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 at 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 <hhan at redhat.com<mailto:hhan at redhat.com>> ??? virsh capabilities|xmllint --xpath //cpu - -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://listman.redhat.com/archives/libvirt-users/attachments/20220613/fdd38e46/attachment-0001.htm> -------------- next part -------------- A non-text attachment was scrubbed... Name: ???? 2022-06-13 ??12.35.19.png Type: image/png Size: 71356 bytes Desc: ???? 2022-06-13 ??12.35.19.png URL: <http://listman.redhat.com/archives/libvirt-users/attachments/20220613/fdd38e46/attachment-0001.png> -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: source.capbilites.txt URL: <http://listman.redhat.com/archives/libvirt-users/attachments/20220613/fdd38e46/attachment-0002.txt> -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: dist.capbilites.txt URL: <http://listman.redhat.com/archives/libvirt-users/attachments/20220613/fdd38e46/attachment-0003.txt>