aboutsummaryrefslogtreecommitdiff
path: root/numa.c
diff options
context:
space:
mode:
authorLaurent Vivier <lvivier@redhat.com>2019-05-29 18:07:47 +0200
committerEduardo Habkost <ehabkost@redhat.com>2019-06-07 15:28:46 -0300
commita5bf9fbcc92322e9919113c14dee9838bee4cab4 (patch)
tree4ce755f030232786cca4c7c5c93d1007422bd99e /numa.c
parent185b7ccc11354cbd69b6d53bf8d831dd964f6c88 (diff)
downloadqemu-a5bf9fbcc92322e9919113c14dee9838bee4cab4.zip
qemu-a5bf9fbcc92322e9919113c14dee9838bee4cab4.tar.gz
qemu-a5bf9fbcc92322e9919113c14dee9838bee4cab4.tar.bz2
numa: improve cpu hotplug error message with a wrong node-id
On pseries, core-ids are strongly binded to a node-id by the command line option. If an user tries to add a CPU to the wrong node, he has an error but it is not really helpful: qemu-system-ppc64 ... -smp 1,maxcpus=64,cores=1,threads=1,sockets=1 \ -numa node,nodeid=0 -numa node,nodeid=1 ... (qemu) device_add power9_v2.0-spapr-cpu-core,core-id=30,node-id=1 Error: node-id=1 must match numa node specified with -numa option This patch improves this error message by giving to the user the good node-id to use with the core-id he's providing Error: invalid node-id, must be 0 Signed-off-by: Laurent Vivier <lvivier@redhat.com> Message-Id: <20190529160747.778-1-lvivier@redhat.com> Reviewed-by: Igor Mammedov <imammedo@redhat.com> Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>
Diffstat (limited to 'numa.c')
-rw-r--r--numa.c4
1 files changed, 2 insertions, 2 deletions
diff --git a/numa.c b/numa.c
index 3875e1e..955ec0c 100644
--- a/numa.c
+++ b/numa.c
@@ -470,8 +470,8 @@ void numa_cpu_pre_plug(const CPUArchId *slot, DeviceState *dev, Error **errp)
"node-id", errp);
}
} else if (node_id != slot->props.node_id) {
- error_setg(errp, "node-id=%d must match numa node specified "
- "with -numa option", node_id);
+ error_setg(errp, "invalid node-id, must be %"PRId64,
+ slot->props.node_id);
}
}