error: unsupported configuration: CPU topology doesn't match maximum vcpu count - on vm startup (Doc ID 2796403.1)

Last updated on SEPTEMBER 26, 2023

Applies to:

Symptoms

Customer increased memory for the VM.
VM startup fails with the below messages 

[root@exadm01 ~]# vm_maker --set --memory 96G --domain testvm.domain.com --restart-domain
[INFO] Memory set successfully to 98304MB for domain testvm.domain.com, restarting.
[INFO] Running 'virsh start testvm.domain.com'...
[EXCEPTION] internal error: The command 'virsh start testvm.domain.com' returned with exit status 1.
Command standard output is '
'.
Command error output is 'error: Failed to start domain testvm.domain.com
error: unsupported configuration: CPU topology doesn't match maximum vcpu count
'.

There are no issues with the CPU count/configuration:

[root@exadm01~]# vm_maker --list --vcpu --domain testvm.domain.com
testvm.domain.com : Current: 64 Restart: 64
 

Changes

 Customer made some changes to the XML file for the VM and had changed the value for "check" from "numa" to "none" during the changes - as below:

<cpu mode='host-passthrough' check='none'> from <cpu mode='host-passthrough' check='numa'>

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.