After restarted libvirtd service, live migration VM hit an issue 'Target CPU check default does not match source none'
8:31 a.m.
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 think it should
be ‘custom’ mode by default . Furthermore , those two hosts for doing live migration have
almost the same capabilities as below.
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
9:17 p.m.
New subject: 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(a)hotmail.com> 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 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
12:06 a.m.
New subject: 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 <hhan@redhat.com<mailto:hhan@redhat.com>> 写道：
virsh capabilities|xmllint --xpath //cpu -
4:46 a.m.
New subject: 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 +0000, 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 terminal with the text. The output of dumpxml --inactive looks
suspicious as it wouldn't normally have check='full' in it unless it was
explicitly mentioned in the XML when the domain was defined.
Anyway, you did not mention how exactly you are migrating your domain,
i.e., the exact command and its parameters. The error message looks like
you're passing a custom XML to the migration command, is that the case?
If so, how does the XML looks like and how did you create it?
Jirka
772
days inactive
775
days old
3 comments
4 participants
participants (4)
-
Han Han -
Jiri Denemark -
liang chaojun -
梁朝军