External/libvirt
1
0
Fork 0
mirror of https://gitlab.com/libvirt/libvirt.git synced 2024-11-03 20:01:16 +00:00
Code Issues Packages Projects Releases Wiki Activity
95bd137216
libvirt/tests/qemuhotplugtestcpus/x86-modern-bulk-monitor.json

472 lines
9.4 KiB
JSON
Raw Normal View History

tests: hotplug: Add test infrastructure for testing qemu CPU hotplug code The cpu hotplug operation is rather complex so the testing code needs to provide quite lot of data and monitor conversations to successfully test it. The code mainly tests the selection of cpus according to the target count request.
2016-12-04 18:08:25 +00:00
{"execute":"query-hotpluggable-cpus","id":"libvirt-1"}
{
"return": [
{
"props": {
"core-id": 1,
"thread-id": 1,
"socket-id": 1
},
"vcpus-count": 1,
"type": "qemu64-x86_64-cpu"
},
{
"props": {
"core-id": 1,
"thread-id": 0,
"socket-id": 1
},
"vcpus-count": 1,
"type": "qemu64-x86_64-cpu"
},
{
"props": {
"core-id": 0,
"thread-id": 1,
"socket-id": 1
},
"vcpus-count": 1,
"type": "qemu64-x86_64-cpu"
},
{
"props": {
"core-id": 0,
"thread-id": 0,
"socket-id": 1
},
"vcpus-count": 1,
"qom-path": "/machine/unattached/device[5]",
"type": "qemu64-x86_64-cpu"
},
{
"props": {
"core-id": 1,
"thread-id": 1,
"socket-id": 0
},
"vcpus-count": 1,
"qom-path": "/machine/unattached/device[4]",
"type": "qemu64-x86_64-cpu"
},
{
"props": {
"core-id": 1,
"thread-id": 0,
"socket-id": 0
},
"vcpus-count": 1,
"qom-path": "/machine/unattached/device[3]",
"type": "qemu64-x86_64-cpu"
},
{
"props": {
"core-id": 0,
"thread-id": 1,
"socket-id": 0
},
"vcpus-count": 1,
"qom-path": "/machine/unattached/device[2]",
"type": "qemu64-x86_64-cpu"
},
{
"props": {
"core-id": 0,
"thread-id": 0,
"socket-id": 0
},
"vcpus-count": 1,
"qom-path": "/machine/unattached/device[0]",
"type": "qemu64-x86_64-cpu"
}
],
"id": "libvirt-23"
}
qemuhotplugtestcpus: Always use 'query-cpus-fast' Use the new command in the test suite by asserting the capability and adjusting test data to the correct field names as they changed compared to 'query-cpus'. Signed-off-by: Peter Krempa <pkrempa@redhat.com> Reviewed-by: Daniel Henrique Barboza <danielhb413@gmail.com>
2020-03-04 11:19:39 +00:00
{"execute":"query-cpus-fast","id":"libvirt-2"}
tests: hotplug: Add test infrastructure for testing qemu CPU hotplug code The cpu hotplug operation is rather complex so the testing code needs to provide quite lot of data and monitor conversations to successfully test it. The code mainly tests the selection of cpus according to the target count request.
2016-12-04 18:08:25 +00:00
{
"return": [
{
qemuhotplugtestcpus: Always use 'query-cpus-fast' Use the new command in the test suite by asserting the capability and adjusting test data to the correct field names as they changed compared to 'query-cpus'. Signed-off-by: Peter Krempa <pkrempa@redhat.com> Reviewed-by: Daniel Henrique Barboza <danielhb413@gmail.com>
2020-03-04 11:19:39 +00:00
"target": "x86",
tests: hotplug: Add test infrastructure for testing qemu CPU hotplug code The cpu hotplug operation is rather complex so the testing code needs to provide quite lot of data and monitor conversations to successfully test it. The code mainly tests the selection of cpus according to the target count request.
2016-12-04 18:08:25 +00:00
"current": true,
qemuhotplugtestcpus: Always use 'query-cpus-fast' Use the new command in the test suite by asserting the capability and adjusting test data to the correct field names as they changed compared to 'query-cpus'. Signed-off-by: Peter Krempa <pkrempa@redhat.com> Reviewed-by: Daniel Henrique Barboza <danielhb413@gmail.com>
2020-03-04 11:19:39 +00:00
"cpu-index": 0,
"qom-path": "/machine/unattached/device[0]",
tests: hotplug: Add test infrastructure for testing qemu CPU hotplug code The cpu hotplug operation is rather complex so the testing code needs to provide quite lot of data and monitor conversations to successfully test it. The code mainly tests the selection of cpus according to the target count request.
2016-12-04 18:08:25 +00:00
"pc": -2130415978,
"halted": true,
qemuhotplugtestcpus: Always use 'query-cpus-fast' Use the new command in the test suite by asserting the capability and adjusting test data to the correct field names as they changed compared to 'query-cpus'. Signed-off-by: Peter Krempa <pkrempa@redhat.com> Reviewed-by: Daniel Henrique Barboza <danielhb413@gmail.com>
2020-03-04 11:19:39 +00:00
"thread-id": 518291
tests: hotplug: Add test infrastructure for testing qemu CPU hotplug code The cpu hotplug operation is rather complex so the testing code needs to provide quite lot of data and monitor conversations to successfully test it. The code mainly tests the selection of cpus according to the target count request.
2016-12-04 18:08:25 +00:00
},
{
qemuhotplugtestcpus: Always use 'query-cpus-fast' Use the new command in the test suite by asserting the capability and adjusting test data to the correct field names as they changed compared to 'query-cpus'. Signed-off-by: Peter Krempa <pkrempa@redhat.com> Reviewed-by: Daniel Henrique Barboza <danielhb413@gmail.com>
2020-03-04 11:19:39 +00:00
"target": "x86",
tests: hotplug: Add test infrastructure for testing qemu CPU hotplug code The cpu hotplug operation is rather complex so the testing code needs to provide quite lot of data and monitor conversations to successfully test it. The code mainly tests the selection of cpus according to the target count request.
2016-12-04 18:08:25 +00:00
"current": false,
qemuhotplugtestcpus: Always use 'query-cpus-fast' Use the new command in the test suite by asserting the capability and adjusting test data to the correct field names as they changed compared to 'query-cpus'. Signed-off-by: Peter Krempa <pkrempa@redhat.com> Reviewed-by: Daniel Henrique Barboza <danielhb413@gmail.com>
2020-03-04 11:19:39 +00:00
"cpu-index": 1,
"qom-path": "/machine/unattached/device[2]",
tests: hotplug: Add test infrastructure for testing qemu CPU hotplug code The cpu hotplug operation is rather complex so the testing code needs to provide quite lot of data and monitor conversations to successfully test it. The code mainly tests the selection of cpus according to the target count request.
2016-12-04 18:08:25 +00:00
"pc": -2130415978,
"halted": true,
qemuhotplugtestcpus: Always use 'query-cpus-fast' Use the new command in the test suite by asserting the capability and adjusting test data to the correct field names as they changed compared to 'query-cpus'. Signed-off-by: Peter Krempa <pkrempa@redhat.com> Reviewed-by: Daniel Henrique Barboza <danielhb413@gmail.com>
2020-03-04 11:19:39 +00:00
"thread-id": 518292
tests: hotplug: Add test infrastructure for testing qemu CPU hotplug code The cpu hotplug operation is rather complex so the testing code needs to provide quite lot of data and monitor conversations to successfully test it. The code mainly tests the selection of cpus according to the target count request.
2016-12-04 18:08:25 +00:00
},
{
qemuhotplugtestcpus: Always use 'query-cpus-fast' Use the new command in the test suite by asserting the capability and adjusting test data to the correct field names as they changed compared to 'query-cpus'. Signed-off-by: Peter Krempa <pkrempa@redhat.com> Reviewed-by: Daniel Henrique Barboza <danielhb413@gmail.com>
2020-03-04 11:19:39 +00:00
"target": "x86",
tests: hotplug: Add test infrastructure for testing qemu CPU hotplug code The cpu hotplug operation is rather complex so the testing code needs to provide quite lot of data and monitor conversations to successfully test it. The code mainly tests the selection of cpus according to the target count request.
2016-12-04 18:08:25 +00:00
"current": false,
qemuhotplugtestcpus: Always use 'query-cpus-fast' Use the new command in the test suite by asserting the capability and adjusting test data to the correct field names as they changed compared to 'query-cpus'. Signed-off-by: Peter Krempa <pkrempa@redhat.com> Reviewed-by: Daniel Henrique Barboza <danielhb413@gmail.com>
2020-03-04 11:19:39 +00:00
"cpu-index": 2,
"qom-path": "/machine/unattached/device[3]",
tests: hotplug: Add test infrastructure for testing qemu CPU hotplug code The cpu hotplug operation is rather complex so the testing code needs to provide quite lot of data and monitor conversations to successfully test it. The code mainly tests the selection of cpus according to the target count request.
2016-12-04 18:08:25 +00:00
"pc": -2130415978,
"halted": true,
qemuhotplugtestcpus: Always use 'query-cpus-fast' Use the new command in the test suite by asserting the capability and adjusting test data to the correct field names as they changed compared to 'query-cpus'. Signed-off-by: Peter Krempa <pkrempa@redhat.com> Reviewed-by: Daniel Henrique Barboza <danielhb413@gmail.com>
2020-03-04 11:19:39 +00:00
"thread-id": 518294
tests: hotplug: Add test infrastructure for testing qemu CPU hotplug code The cpu hotplug operation is rather complex so the testing code needs to provide quite lot of data and monitor conversations to successfully test it. The code mainly tests the selection of cpus according to the target count request.
2016-12-04 18:08:25 +00:00
},
{
qemuhotplugtestcpus: Always use 'query-cpus-fast' Use the new command in the test suite by asserting the capability and adjusting test data to the correct field names as they changed compared to 'query-cpus'. Signed-off-by: Peter Krempa <pkrempa@redhat.com> Reviewed-by: Daniel Henrique Barboza <danielhb413@gmail.com>
2020-03-04 11:19:39 +00:00
"target": "x86",
tests: hotplug: Add test infrastructure for testing qemu CPU hotplug code The cpu hotplug operation is rather complex so the testing code needs to provide quite lot of data and monitor conversations to successfully test it. The code mainly tests the selection of cpus according to the target count request.
2016-12-04 18:08:25 +00:00
"current": false,
qemuhotplugtestcpus: Always use 'query-cpus-fast' Use the new command in the test suite by asserting the capability and adjusting test data to the correct field names as they changed compared to 'query-cpus'. Signed-off-by: Peter Krempa <pkrempa@redhat.com> Reviewed-by: Daniel Henrique Barboza <danielhb413@gmail.com>
2020-03-04 11:19:39 +00:00
"cpu-index": 3,
"qom-path": "/machine/unattached/device[4]",
tests: hotplug: Add test infrastructure for testing qemu CPU hotplug code The cpu hotplug operation is rather complex so the testing code needs to provide quite lot of data and monitor conversations to successfully test it. The code mainly tests the selection of cpus according to the target count request.
2016-12-04 18:08:25 +00:00
"pc": -2130415978,
"halted": true,
qemuhotplugtestcpus: Always use 'query-cpus-fast' Use the new command in the test suite by asserting the capability and adjusting test data to the correct field names as they changed compared to 'query-cpus'. Signed-off-by: Peter Krempa <pkrempa@redhat.com> Reviewed-by: Daniel Henrique Barboza <danielhb413@gmail.com>
2020-03-04 11:19:39 +00:00
"thread-id": 518295
tests: hotplug: Add test infrastructure for testing qemu CPU hotplug code The cpu hotplug operation is rather complex so the testing code needs to provide quite lot of data and monitor conversations to successfully test it. The code mainly tests the selection of cpus according to the target count request.
2016-12-04 18:08:25 +00:00
},
{
qemuhotplugtestcpus: Always use 'query-cpus-fast' Use the new command in the test suite by asserting the capability and adjusting test data to the correct field names as they changed compared to 'query-cpus'. Signed-off-by: Peter Krempa <pkrempa@redhat.com> Reviewed-by: Daniel Henrique Barboza <danielhb413@gmail.com>
2020-03-04 11:19:39 +00:00
"target": "x86",
tests: hotplug: Add test infrastructure for testing qemu CPU hotplug code The cpu hotplug operation is rather complex so the testing code needs to provide quite lot of data and monitor conversations to successfully test it. The code mainly tests the selection of cpus according to the target count request.
2016-12-04 18:08:25 +00:00
"current": false,
qemuhotplugtestcpus: Always use 'query-cpus-fast' Use the new command in the test suite by asserting the capability and adjusting test data to the correct field names as they changed compared to 'query-cpus'. Signed-off-by: Peter Krempa <pkrempa@redhat.com> Reviewed-by: Daniel Henrique Barboza <danielhb413@gmail.com>
2020-03-04 11:19:39 +00:00
"cpu-index": 4,
"qom-path": "/machine/unattached/device[5]",
tests: hotplug: Add test infrastructure for testing qemu CPU hotplug code The cpu hotplug operation is rather complex so the testing code needs to provide quite lot of data and monitor conversations to successfully test it. The code mainly tests the selection of cpus according to the target count request.
2016-12-04 18:08:25 +00:00
"pc": -2130415978,
"halted": true,
qemuhotplugtestcpus: Always use 'query-cpus-fast' Use the new command in the test suite by asserting the capability and adjusting test data to the correct field names as they changed compared to 'query-cpus'. Signed-off-by: Peter Krempa <pkrempa@redhat.com> Reviewed-by: Daniel Henrique Barboza <danielhb413@gmail.com>
2020-03-04 11:19:39 +00:00
"thread-id": 518296
tests: hotplug: Add test infrastructure for testing qemu CPU hotplug code The cpu hotplug operation is rather complex so the testing code needs to provide quite lot of data and monitor conversations to successfully test it. The code mainly tests the selection of cpus according to the target count request.
2016-12-04 18:08:25 +00:00
}
],
"id": "libvirt-22"
}
{
"execute": "device_add",
"arguments": {
"driver": "qemu64-x86_64-cpu",
"id": "vcpu5",
"core-id": 0,
qemu: command: Use all vCPU properties when creating args for vCPU hotplug As qemu documents we should use everything in the 'props' sub-object of the data returned by query-hotpluggable-cpus. Until now we only used everything we recognized, but that may break in cases when qemu introduces new fields. This change requires a fix to the test data as some fields were reordered. https://bugzilla.redhat.com/show_bug.cgi?id=1741658 Signed-off-by: Peter Krempa <pkrempa@redhat.com>
2019-08-29 13:15:23 +00:00
"thread-id": 1,
"socket-id": 1
tests: hotplug: Add test infrastructure for testing qemu CPU hotplug code The cpu hotplug operation is rather complex so the testing code needs to provide quite lot of data and monitor conversations to successfully test it. The code mainly tests the selection of cpus according to the target count request.
2016-12-04 18:08:25 +00:00
},
"id": "libvirt-3"
}
{"return": {}}
{"execute":"query-hotpluggable-cpus","id":"libvirt-4"}
{
"return": [
{
"props": {
"core-id": 1,
"thread-id": 1,
"socket-id": 1
},
"vcpus-count": 1,
"type": "qemu64-x86_64-cpu"
},
{
"props": {
"core-id": 1,
"thread-id": 0,
"socket-id": 1
},
"vcpus-count": 1,
"type": "qemu64-x86_64-cpu"
},
{
"props": {
"core-id": 0,
"thread-id": 1,
"socket-id": 1
},
"vcpus-count": 1,
"qom-path": "/machine/peripheral/vcpu5",
"type": "qemu64-x86_64-cpu"
},
{
"props": {
"core-id": 0,
"thread-id": 0,
"socket-id": 1
},
"vcpus-count": 1,
"qom-path": "/machine/unattached/device[5]",
"type": "qemu64-x86_64-cpu"
},
{
"props": {
"core-id": 1,
"thread-id": 1,
"socket-id": 0
},
"vcpus-count": 1,
"qom-path": "/machine/unattached/device[4]",
"type": "qemu64-x86_64-cpu"
},
{
"props": {
"core-id": 1,
"thread-id": 0,
"socket-id": 0
},
"vcpus-count": 1,
"qom-path": "/machine/unattached/device[3]",
"type": "qemu64-x86_64-cpu"
},
{
"props": {
"core-id": 0,
"thread-id": 1,
"socket-id": 0
},
"vcpus-count": 1,
"qom-path": "/machine/unattached/device[2]",
"type": "qemu64-x86_64-cpu"
},
{
"props": {
"core-id": 0,
"thread-id": 0,
"socket-id": 0
},
"vcpus-count": 1,
"qom-path": "/machine/unattached/device[0]",
"type": "qemu64-x86_64-cpu"
}
],
"id": "libvirt-23"
}
qemuhotplugtestcpus: Always use 'query-cpus-fast' Use the new command in the test suite by asserting the capability and adjusting test data to the correct field names as they changed compared to 'query-cpus'. Signed-off-by: Peter Krempa <pkrempa@redhat.com> Reviewed-by: Daniel Henrique Barboza <danielhb413@gmail.com>
2020-03-04 11:19:39 +00:00
{"execute":"query-cpus-fast","id":"libvirt-5"}
tests: hotplug: Add test infrastructure for testing qemu CPU hotplug code The cpu hotplug operation is rather complex so the testing code needs to provide quite lot of data and monitor conversations to successfully test it. The code mainly tests the selection of cpus according to the target count request.
2016-12-04 18:08:25 +00:00
{
"return": [
{
qemuhotplugtestcpus: Always use 'query-cpus-fast' Use the new command in the test suite by asserting the capability and adjusting test data to the correct field names as they changed compared to 'query-cpus'. Signed-off-by: Peter Krempa <pkrempa@redhat.com> Reviewed-by: Daniel Henrique Barboza <danielhb413@gmail.com>
2020-03-04 11:19:39 +00:00
"target": "x86",
tests: hotplug: Add test infrastructure for testing qemu CPU hotplug code The cpu hotplug operation is rather complex so the testing code needs to provide quite lot of data and monitor conversations to successfully test it. The code mainly tests the selection of cpus according to the target count request.
2016-12-04 18:08:25 +00:00
"current": true,
qemuhotplugtestcpus: Always use 'query-cpus-fast' Use the new command in the test suite by asserting the capability and adjusting test data to the correct field names as they changed compared to 'query-cpus'. Signed-off-by: Peter Krempa <pkrempa@redhat.com> Reviewed-by: Daniel Henrique Barboza <danielhb413@gmail.com>
2020-03-04 11:19:39 +00:00
"cpu-index": 0,
"qom-path": "/machine/unattached/device[0]",
tests: hotplug: Add test infrastructure for testing qemu CPU hotplug code The cpu hotplug operation is rather complex so the testing code needs to provide quite lot of data and monitor conversations to successfully test it. The code mainly tests the selection of cpus according to the target count request.
2016-12-04 18:08:25 +00:00
"pc": -2130415978,
"halted": true,
qemuhotplugtestcpus: Always use 'query-cpus-fast' Use the new command in the test suite by asserting the capability and adjusting test data to the correct field names as they changed compared to 'query-cpus'. Signed-off-by: Peter Krempa <pkrempa@redhat.com> Reviewed-by: Daniel Henrique Barboza <danielhb413@gmail.com>
2020-03-04 11:19:39 +00:00
"thread-id": 518291
tests: hotplug: Add test infrastructure for testing qemu CPU hotplug code The cpu hotplug operation is rather complex so the testing code needs to provide quite lot of data and monitor conversations to successfully test it. The code mainly tests the selection of cpus according to the target count request.
2016-12-04 18:08:25 +00:00
},
{
qemuhotplugtestcpus: Always use 'query-cpus-fast' Use the new command in the test suite by asserting the capability and adjusting test data to the correct field names as they changed compared to 'query-cpus'. Signed-off-by: Peter Krempa <pkrempa@redhat.com> Reviewed-by: Daniel Henrique Barboza <danielhb413@gmail.com>
2020-03-04 11:19:39 +00:00
"target": "x86",
tests: hotplug: Add test infrastructure for testing qemu CPU hotplug code The cpu hotplug operation is rather complex so the testing code needs to provide quite lot of data and monitor conversations to successfully test it. The code mainly tests the selection of cpus according to the target count request.
2016-12-04 18:08:25 +00:00
"current": false,
qemuhotplugtestcpus: Always use 'query-cpus-fast' Use the new command in the test suite by asserting the capability and adjusting test data to the correct field names as they changed compared to 'query-cpus'. Signed-off-by: Peter Krempa <pkrempa@redhat.com> Reviewed-by: Daniel Henrique Barboza <danielhb413@gmail.com>
2020-03-04 11:19:39 +00:00
"cpu-index": 1,
"qom-path": "/machine/unattached/device[2]",
tests: hotplug: Add test infrastructure for testing qemu CPU hotplug code The cpu hotplug operation is rather complex so the testing code needs to provide quite lot of data and monitor conversations to successfully test it. The code mainly tests the selection of cpus according to the target count request.
2016-12-04 18:08:25 +00:00
"pc": -2130415978,
"halted": true,
qemuhotplugtestcpus: Always use 'query-cpus-fast' Use the new command in the test suite by asserting the capability and adjusting test data to the correct field names as they changed compared to 'query-cpus'. Signed-off-by: Peter Krempa <pkrempa@redhat.com> Reviewed-by: Daniel Henrique Barboza <danielhb413@gmail.com>
2020-03-04 11:19:39 +00:00
"thread-id": 518292
tests: hotplug: Add test infrastructure for testing qemu CPU hotplug code The cpu hotplug operation is rather complex so the testing code needs to provide quite lot of data and monitor conversations to successfully test it. The code mainly tests the selection of cpus according to the target count request.
2016-12-04 18:08:25 +00:00
},
{
qemuhotplugtestcpus: Always use 'query-cpus-fast' Use the new command in the test suite by asserting the capability and adjusting test data to the correct field names as they changed compared to 'query-cpus'. Signed-off-by: Peter Krempa <pkrempa@redhat.com> Reviewed-by: Daniel Henrique Barboza <danielhb413@gmail.com>
2020-03-04 11:19:39 +00:00
"target": "x86",
tests: hotplug: Add test infrastructure for testing qemu CPU hotplug code The cpu hotplug operation is rather complex so the testing code needs to provide quite lot of data and monitor conversations to successfully test it. The code mainly tests the selection of cpus according to the target count request.
2016-12-04 18:08:25 +00:00
"current": false,
qemuhotplugtestcpus: Always use 'query-cpus-fast' Use the new command in the test suite by asserting the capability and adjusting test data to the correct field names as they changed compared to 'query-cpus'. Signed-off-by: Peter Krempa <pkrempa@redhat.com> Reviewed-by: Daniel Henrique Barboza <danielhb413@gmail.com>
2020-03-04 11:19:39 +00:00
"cpu-index": 2,
"qom-path": "/machine/unattached/device[3]",
tests: hotplug: Add test infrastructure for testing qemu CPU hotplug code The cpu hotplug operation is rather complex so the testing code needs to provide quite lot of data and monitor conversations to successfully test it. The code mainly tests the selection of cpus according to the target count request.
2016-12-04 18:08:25 +00:00
"pc": -2130415978,
"halted": true,
qemuhotplugtestcpus: Always use 'query-cpus-fast' Use the new command in the test suite by asserting the capability and adjusting test data to the correct field names as they changed compared to 'query-cpus'. Signed-off-by: Peter Krempa <pkrempa@redhat.com> Reviewed-by: Daniel Henrique Barboza <danielhb413@gmail.com>
2020-03-04 11:19:39 +00:00
"thread-id": 518294
tests: hotplug: Add test infrastructure for testing qemu CPU hotplug code The cpu hotplug operation is rather complex so the testing code needs to provide quite lot of data and monitor conversations to successfully test it. The code mainly tests the selection of cpus according to the target count request.
2016-12-04 18:08:25 +00:00
},
{
qemuhotplugtestcpus: Always use 'query-cpus-fast' Use the new command in the test suite by asserting the capability and adjusting test data to the correct field names as they changed compared to 'query-cpus'. Signed-off-by: Peter Krempa <pkrempa@redhat.com> Reviewed-by: Daniel Henrique Barboza <danielhb413@gmail.com>
2020-03-04 11:19:39 +00:00
"target": "x86",
tests: hotplug: Add test infrastructure for testing qemu CPU hotplug code The cpu hotplug operation is rather complex so the testing code needs to provide quite lot of data and monitor conversations to successfully test it. The code mainly tests the selection of cpus according to the target count request.
2016-12-04 18:08:25 +00:00
"current": false,
qemuhotplugtestcpus: Always use 'query-cpus-fast' Use the new command in the test suite by asserting the capability and adjusting test data to the correct field names as they changed compared to 'query-cpus'. Signed-off-by: Peter Krempa <pkrempa@redhat.com> Reviewed-by: Daniel Henrique Barboza <danielhb413@gmail.com>
2020-03-04 11:19:39 +00:00
"cpu-index": 3,
"qom-path": "/machine/unattached/device[4]",
tests: hotplug: Add test infrastructure for testing qemu CPU hotplug code The cpu hotplug operation is rather complex so the testing code needs to provide quite lot of data and monitor conversations to successfully test it. The code mainly tests the selection of cpus according to the target count request.
2016-12-04 18:08:25 +00:00
"pc": -2130415978,
"halted": true,
qemuhotplugtestcpus: Always use 'query-cpus-fast' Use the new command in the test suite by asserting the capability and adjusting test data to the correct field names as they changed compared to 'query-cpus'. Signed-off-by: Peter Krempa <pkrempa@redhat.com> Reviewed-by: Daniel Henrique Barboza <danielhb413@gmail.com>
2020-03-04 11:19:39 +00:00
"thread-id": 518295
tests: hotplug: Add test infrastructure for testing qemu CPU hotplug code The cpu hotplug operation is rather complex so the testing code needs to provide quite lot of data and monitor conversations to successfully test it. The code mainly tests the selection of cpus according to the target count request.
2016-12-04 18:08:25 +00:00
},
{
qemuhotplugtestcpus: Always use 'query-cpus-fast' Use the new command in the test suite by asserting the capability and adjusting test data to the correct field names as they changed compared to 'query-cpus'. Signed-off-by: Peter Krempa <pkrempa@redhat.com> Reviewed-by: Daniel Henrique Barboza <danielhb413@gmail.com>
2020-03-04 11:19:39 +00:00
"target": "x86",
tests: hotplug: Add test infrastructure for testing qemu CPU hotplug code The cpu hotplug operation is rather complex so the testing code needs to provide quite lot of data and monitor conversations to successfully test it. The code mainly tests the selection of cpus according to the target count request.
2016-12-04 18:08:25 +00:00
"current": false,
qemuhotplugtestcpus: Always use 'query-cpus-fast' Use the new command in the test suite by asserting the capability and adjusting test data to the correct field names as they changed compared to 'query-cpus'. Signed-off-by: Peter Krempa <pkrempa@redhat.com> Reviewed-by: Daniel Henrique Barboza <danielhb413@gmail.com>
2020-03-04 11:19:39 +00:00
"cpu-index": 4,
"qom-path": "/machine/unattached/device[5]",
tests: hotplug: Add test infrastructure for testing qemu CPU hotplug code The cpu hotplug operation is rather complex so the testing code needs to provide quite lot of data and monitor conversations to successfully test it. The code mainly tests the selection of cpus according to the target count request.
2016-12-04 18:08:25 +00:00
"pc": -2130415978,
"halted": true,
qemuhotplugtestcpus: Always use 'query-cpus-fast' Use the new command in the test suite by asserting the capability and adjusting test data to the correct field names as they changed compared to 'query-cpus'. Signed-off-by: Peter Krempa <pkrempa@redhat.com> Reviewed-by: Daniel Henrique Barboza <danielhb413@gmail.com>
2020-03-04 11:19:39 +00:00
"thread-id": 518296
tests: hotplug: Add test infrastructure for testing qemu CPU hotplug code The cpu hotplug operation is rather complex so the testing code needs to provide quite lot of data and monitor conversations to successfully test it. The code mainly tests the selection of cpus according to the target count request.
2016-12-04 18:08:25 +00:00
},
{
qemuhotplugtestcpus: Always use 'query-cpus-fast' Use the new command in the test suite by asserting the capability and adjusting test data to the correct field names as they changed compared to 'query-cpus'. Signed-off-by: Peter Krempa <pkrempa@redhat.com> Reviewed-by: Daniel Henrique Barboza <danielhb413@gmail.com>
2020-03-04 11:19:39 +00:00
"target": "x86",
tests: hotplug: Add test infrastructure for testing qemu CPU hotplug code The cpu hotplug operation is rather complex so the testing code needs to provide quite lot of data and monitor conversations to successfully test it. The code mainly tests the selection of cpus according to the target count request.
2016-12-04 18:08:25 +00:00
"current": false,
qemuhotplugtestcpus: Always use 'query-cpus-fast' Use the new command in the test suite by asserting the capability and adjusting test data to the correct field names as they changed compared to 'query-cpus'. Signed-off-by: Peter Krempa <pkrempa@redhat.com> Reviewed-by: Daniel Henrique Barboza <danielhb413@gmail.com>
2020-03-04 11:19:39 +00:00
"cpu-index": 5,
"qom-path": "/machine/peripheral/vcpu5",
tests: hotplug: Add test infrastructure for testing qemu CPU hotplug code The cpu hotplug operation is rather complex so the testing code needs to provide quite lot of data and monitor conversations to successfully test it. The code mainly tests the selection of cpus according to the target count request.
2016-12-04 18:08:25 +00:00
"pc": -2130415978,
"halted": true,
qemuhotplugtestcpus: Always use 'query-cpus-fast' Use the new command in the test suite by asserting the capability and adjusting test data to the correct field names as they changed compared to 'query-cpus'. Signed-off-by: Peter Krempa <pkrempa@redhat.com> Reviewed-by: Daniel Henrique Barboza <danielhb413@gmail.com>
2020-03-04 11:19:39 +00:00
"thread-id": 518297
tests: hotplug: Add test infrastructure for testing qemu CPU hotplug code The cpu hotplug operation is rather complex so the testing code needs to provide quite lot of data and monitor conversations to successfully test it. The code mainly tests the selection of cpus according to the target count request.
2016-12-04 18:08:25 +00:00
}
],
"id": "libvirt-22"
}
{
"execute": "device_add",
"arguments": {
"driver": "qemu64-x86_64-cpu",
"id": "vcpu6",
"core-id": 1,
qemu: command: Use all vCPU properties when creating args for vCPU hotplug As qemu documents we should use everything in the 'props' sub-object of the data returned by query-hotpluggable-cpus. Until now we only used everything we recognized, but that may break in cases when qemu introduces new fields. This change requires a fix to the test data as some fields were reordered. https://bugzilla.redhat.com/show_bug.cgi?id=1741658 Signed-off-by: Peter Krempa <pkrempa@redhat.com>
2019-08-29 13:15:23 +00:00
"thread-id": 0,
"socket-id": 1
tests: hotplug: Add test infrastructure for testing qemu CPU hotplug code The cpu hotplug operation is rather complex so the testing code needs to provide quite lot of data and monitor conversations to successfully test it. The code mainly tests the selection of cpus according to the target count request.
2016-12-04 18:08:25 +00:00
},
"id": "libvirt-6"
}
{"return": {}}
{"execute":"query-hotpluggable-cpus","id":"libvirt-7"}
{
"return": [
{
"props": {
"core-id": 1,
"thread-id": 1,
"socket-id": 1
},
"vcpus-count": 1,
"type": "qemu64-x86_64-cpu"
},
{
"props": {
"core-id": 1,
"thread-id": 0,
"socket-id": 1
},
"vcpus-count": 1,
"qom-path": "/machine/peripheral/vcpu6",
"type": "qemu64-x86_64-cpu"
},
{
"props": {
"core-id": 0,
"thread-id": 1,
"socket-id": 1
},
"vcpus-count": 1,
"qom-path": "/machine/peripheral/vcpu5",
"type": "qemu64-x86_64-cpu"
},
{
"props": {
"core-id": 0,
"thread-id": 0,
"socket-id": 1
},
"vcpus-count": 1,
"qom-path": "/machine/unattached/device[5]",
"type": "qemu64-x86_64-cpu"
},
{
"props": {
"core-id": 1,
"thread-id": 1,
"socket-id": 0
},
"vcpus-count": 1,
"qom-path": "/machine/unattached/device[4]",
"type": "qemu64-x86_64-cpu"
},
{
"props": {
"core-id": 1,
"thread-id": 0,
"socket-id": 0
},
"vcpus-count": 1,
"qom-path": "/machine/unattached/device[3]",
"type": "qemu64-x86_64-cpu"
},
{
"props": {
"core-id": 0,
"thread-id": 1,
"socket-id": 0
},
"vcpus-count": 1,
"qom-path": "/machine/unattached/device[2]",
"type": "qemu64-x86_64-cpu"
},
{
"props": {
"core-id": 0,
"thread-id": 0,
"socket-id": 0
},
"vcpus-count": 1,
"qom-path": "/machine/unattached/device[0]",
"type": "qemu64-x86_64-cpu"
}
],
"id": "libvirt-23"
}
qemuhotplugtestcpus: Always use 'query-cpus-fast' Use the new command in the test suite by asserting the capability and adjusting test data to the correct field names as they changed compared to 'query-cpus'. Signed-off-by: Peter Krempa <pkrempa@redhat.com> Reviewed-by: Daniel Henrique Barboza <danielhb413@gmail.com>
2020-03-04 11:19:39 +00:00
{"execute":"query-cpus-fast","id":"libvirt-8"}
tests: hotplug: Add test infrastructure for testing qemu CPU hotplug code The cpu hotplug operation is rather complex so the testing code needs to provide quite lot of data and monitor conversations to successfully test it. The code mainly tests the selection of cpus according to the target count request.
2016-12-04 18:08:25 +00:00
{
"return": [
{
qemuhotplugtestcpus: Always use 'query-cpus-fast' Use the new command in the test suite by asserting the capability and adjusting test data to the correct field names as they changed compared to 'query-cpus'. Signed-off-by: Peter Krempa <pkrempa@redhat.com> Reviewed-by: Daniel Henrique Barboza <danielhb413@gmail.com>
2020-03-04 11:19:39 +00:00
"target": "x86",
tests: hotplug: Add test infrastructure for testing qemu CPU hotplug code The cpu hotplug operation is rather complex so the testing code needs to provide quite lot of data and monitor conversations to successfully test it. The code mainly tests the selection of cpus according to the target count request.
2016-12-04 18:08:25 +00:00
"current": true,
qemuhotplugtestcpus: Always use 'query-cpus-fast' Use the new command in the test suite by asserting the capability and adjusting test data to the correct field names as they changed compared to 'query-cpus'. Signed-off-by: Peter Krempa <pkrempa@redhat.com> Reviewed-by: Daniel Henrique Barboza <danielhb413@gmail.com>
2020-03-04 11:19:39 +00:00
"cpu-index": 0,
"qom-path": "/machine/unattached/device[0]",
tests: hotplug: Add test infrastructure for testing qemu CPU hotplug code The cpu hotplug operation is rather complex so the testing code needs to provide quite lot of data and monitor conversations to successfully test it. The code mainly tests the selection of cpus according to the target count request.
2016-12-04 18:08:25 +00:00
"pc": -2130415978,
"halted": true,
qemuhotplugtestcpus: Always use 'query-cpus-fast' Use the new command in the test suite by asserting the capability and adjusting test data to the correct field names as they changed compared to 'query-cpus'. Signed-off-by: Peter Krempa <pkrempa@redhat.com> Reviewed-by: Daniel Henrique Barboza <danielhb413@gmail.com>
2020-03-04 11:19:39 +00:00
"thread-id": 518291
tests: hotplug: Add test infrastructure for testing qemu CPU hotplug code The cpu hotplug operation is rather complex so the testing code needs to provide quite lot of data and monitor conversations to successfully test it. The code mainly tests the selection of cpus according to the target count request.
2016-12-04 18:08:25 +00:00
},
{
qemuhotplugtestcpus: Always use 'query-cpus-fast' Use the new command in the test suite by asserting the capability and adjusting test data to the correct field names as they changed compared to 'query-cpus'. Signed-off-by: Peter Krempa <pkrempa@redhat.com> Reviewed-by: Daniel Henrique Barboza <danielhb413@gmail.com>
2020-03-04 11:19:39 +00:00
"target": "x86",
tests: hotplug: Add test infrastructure for testing qemu CPU hotplug code The cpu hotplug operation is rather complex so the testing code needs to provide quite lot of data and monitor conversations to successfully test it. The code mainly tests the selection of cpus according to the target count request.
2016-12-04 18:08:25 +00:00
"current": false,
qemuhotplugtestcpus: Always use 'query-cpus-fast' Use the new command in the test suite by asserting the capability and adjusting test data to the correct field names as they changed compared to 'query-cpus'. Signed-off-by: Peter Krempa <pkrempa@redhat.com> Reviewed-by: Daniel Henrique Barboza <danielhb413@gmail.com>
2020-03-04 11:19:39 +00:00
"cpu-index": 1,
"qom-path": "/machine/unattached/device[2]",
tests: hotplug: Add test infrastructure for testing qemu CPU hotplug code The cpu hotplug operation is rather complex so the testing code needs to provide quite lot of data and monitor conversations to successfully test it. The code mainly tests the selection of cpus according to the target count request.
2016-12-04 18:08:25 +00:00
"pc": -2130415978,
"halted": true,
qemuhotplugtestcpus: Always use 'query-cpus-fast' Use the new command in the test suite by asserting the capability and adjusting test data to the correct field names as they changed compared to 'query-cpus'. Signed-off-by: Peter Krempa <pkrempa@redhat.com> Reviewed-by: Daniel Henrique Barboza <danielhb413@gmail.com>
2020-03-04 11:19:39 +00:00
"thread-id": 518292
tests: hotplug: Add test infrastructure for testing qemu CPU hotplug code The cpu hotplug operation is rather complex so the testing code needs to provide quite lot of data and monitor conversations to successfully test it. The code mainly tests the selection of cpus according to the target count request.
2016-12-04 18:08:25 +00:00
},
{
qemuhotplugtestcpus: Always use 'query-cpus-fast' Use the new command in the test suite by asserting the capability and adjusting test data to the correct field names as they changed compared to 'query-cpus'. Signed-off-by: Peter Krempa <pkrempa@redhat.com> Reviewed-by: Daniel Henrique Barboza <danielhb413@gmail.com>
2020-03-04 11:19:39 +00:00
"target": "x86",
tests: hotplug: Add test infrastructure for testing qemu CPU hotplug code The cpu hotplug operation is rather complex so the testing code needs to provide quite lot of data and monitor conversations to successfully test it. The code mainly tests the selection of cpus according to the target count request.
2016-12-04 18:08:25 +00:00
"current": false,
qemuhotplugtestcpus: Always use 'query-cpus-fast' Use the new command in the test suite by asserting the capability and adjusting test data to the correct field names as they changed compared to 'query-cpus'. Signed-off-by: Peter Krempa <pkrempa@redhat.com> Reviewed-by: Daniel Henrique Barboza <danielhb413@gmail.com>
2020-03-04 11:19:39 +00:00
"cpu-index": 2,
"qom-path": "/machine/unattached/device[3]",
tests: hotplug: Add test infrastructure for testing qemu CPU hotplug code The cpu hotplug operation is rather complex so the testing code needs to provide quite lot of data and monitor conversations to successfully test it. The code mainly tests the selection of cpus according to the target count request.
2016-12-04 18:08:25 +00:00
"pc": -2130415978,
"halted": true,
qemuhotplugtestcpus: Always use 'query-cpus-fast' Use the new command in the test suite by asserting the capability and adjusting test data to the correct field names as they changed compared to 'query-cpus'. Signed-off-by: Peter Krempa <pkrempa@redhat.com> Reviewed-by: Daniel Henrique Barboza <danielhb413@gmail.com>
2020-03-04 11:19:39 +00:00
"thread-id": 518294
tests: hotplug: Add test infrastructure for testing qemu CPU hotplug code The cpu hotplug operation is rather complex so the testing code needs to provide quite lot of data and monitor conversations to successfully test it. The code mainly tests the selection of cpus according to the target count request.
2016-12-04 18:08:25 +00:00
},
{
qemuhotplugtestcpus: Always use 'query-cpus-fast' Use the new command in the test suite by asserting the capability and adjusting test data to the correct field names as they changed compared to 'query-cpus'. Signed-off-by: Peter Krempa <pkrempa@redhat.com> Reviewed-by: Daniel Henrique Barboza <danielhb413@gmail.com>
2020-03-04 11:19:39 +00:00
"target": "x86",
tests: hotplug: Add test infrastructure for testing qemu CPU hotplug code The cpu hotplug operation is rather complex so the testing code needs to provide quite lot of data and monitor conversations to successfully test it. The code mainly tests the selection of cpus according to the target count request.
2016-12-04 18:08:25 +00:00
"current": false,
qemuhotplugtestcpus: Always use 'query-cpus-fast' Use the new command in the test suite by asserting the capability and adjusting test data to the correct field names as they changed compared to 'query-cpus'. Signed-off-by: Peter Krempa <pkrempa@redhat.com> Reviewed-by: Daniel Henrique Barboza <danielhb413@gmail.com>
2020-03-04 11:19:39 +00:00
"cpu-index": 3,
"qom-path": "/machine/unattached/device[4]",
tests: hotplug: Add test infrastructure for testing qemu CPU hotplug code The cpu hotplug operation is rather complex so the testing code needs to provide quite lot of data and monitor conversations to successfully test it. The code mainly tests the selection of cpus according to the target count request.
2016-12-04 18:08:25 +00:00
"pc": -2130415978,
"halted": true,
qemuhotplugtestcpus: Always use 'query-cpus-fast' Use the new command in the test suite by asserting the capability and adjusting test data to the correct field names as they changed compared to 'query-cpus'. Signed-off-by: Peter Krempa <pkrempa@redhat.com> Reviewed-by: Daniel Henrique Barboza <danielhb413@gmail.com>
2020-03-04 11:19:39 +00:00
"thread-id": 518295
tests: hotplug: Add test infrastructure for testing qemu CPU hotplug code The cpu hotplug operation is rather complex so the testing code needs to provide quite lot of data and monitor conversations to successfully test it. The code mainly tests the selection of cpus according to the target count request.
2016-12-04 18:08:25 +00:00
},
{
qemuhotplugtestcpus: Always use 'query-cpus-fast' Use the new command in the test suite by asserting the capability and adjusting test data to the correct field names as they changed compared to 'query-cpus'. Signed-off-by: Peter Krempa <pkrempa@redhat.com> Reviewed-by: Daniel Henrique Barboza <danielhb413@gmail.com>
2020-03-04 11:19:39 +00:00
"target": "x86",
tests: hotplug: Add test infrastructure for testing qemu CPU hotplug code The cpu hotplug operation is rather complex so the testing code needs to provide quite lot of data and monitor conversations to successfully test it. The code mainly tests the selection of cpus according to the target count request.
2016-12-04 18:08:25 +00:00
"current": false,
qemuhotplugtestcpus: Always use 'query-cpus-fast' Use the new command in the test suite by asserting the capability and adjusting test data to the correct field names as they changed compared to 'query-cpus'. Signed-off-by: Peter Krempa <pkrempa@redhat.com> Reviewed-by: Daniel Henrique Barboza <danielhb413@gmail.com>
2020-03-04 11:19:39 +00:00
"cpu-index": 4,
"qom-path": "/machine/unattached/device[5]",
tests: hotplug: Add test infrastructure for testing qemu CPU hotplug code The cpu hotplug operation is rather complex so the testing code needs to provide quite lot of data and monitor conversations to successfully test it. The code mainly tests the selection of cpus according to the target count request.
2016-12-04 18:08:25 +00:00
"pc": -2130415978,
"halted": true,
qemuhotplugtestcpus: Always use 'query-cpus-fast' Use the new command in the test suite by asserting the capability and adjusting test data to the correct field names as they changed compared to 'query-cpus'. Signed-off-by: Peter Krempa <pkrempa@redhat.com> Reviewed-by: Daniel Henrique Barboza <danielhb413@gmail.com>
2020-03-04 11:19:39 +00:00
"thread-id": 518296
tests: hotplug: Add test infrastructure for testing qemu CPU hotplug code The cpu hotplug operation is rather complex so the testing code needs to provide quite lot of data and monitor conversations to successfully test it. The code mainly tests the selection of cpus according to the target count request.
2016-12-04 18:08:25 +00:00
},
{
qemuhotplugtestcpus: Always use 'query-cpus-fast' Use the new command in the test suite by asserting the capability and adjusting test data to the correct field names as they changed compared to 'query-cpus'. Signed-off-by: Peter Krempa <pkrempa@redhat.com> Reviewed-by: Daniel Henrique Barboza <danielhb413@gmail.com>
2020-03-04 11:19:39 +00:00
"target": "x86",
tests: hotplug: Add test infrastructure for testing qemu CPU hotplug code The cpu hotplug operation is rather complex so the testing code needs to provide quite lot of data and monitor conversations to successfully test it. The code mainly tests the selection of cpus according to the target count request.
2016-12-04 18:08:25 +00:00
"current": false,
qemuhotplugtestcpus: Always use 'query-cpus-fast' Use the new command in the test suite by asserting the capability and adjusting test data to the correct field names as they changed compared to 'query-cpus'. Signed-off-by: Peter Krempa <pkrempa@redhat.com> Reviewed-by: Daniel Henrique Barboza <danielhb413@gmail.com>
2020-03-04 11:19:39 +00:00
"cpu-index": 5,
"qom-path": "/machine/peripheral/vcpu5",
tests: hotplug: Add test infrastructure for testing qemu CPU hotplug code The cpu hotplug operation is rather complex so the testing code needs to provide quite lot of data and monitor conversations to successfully test it. The code mainly tests the selection of cpus according to the target count request.
2016-12-04 18:08:25 +00:00
"pc": -2130415978,
"halted": true,
qemuhotplugtestcpus: Always use 'query-cpus-fast' Use the new command in the test suite by asserting the capability and adjusting test data to the correct field names as they changed compared to 'query-cpus'. Signed-off-by: Peter Krempa <pkrempa@redhat.com> Reviewed-by: Daniel Henrique Barboza <danielhb413@gmail.com>
2020-03-04 11:19:39 +00:00
"thread-id": 518297
tests: hotplug: Add test infrastructure for testing qemu CPU hotplug code The cpu hotplug operation is rather complex so the testing code needs to provide quite lot of data and monitor conversations to successfully test it. The code mainly tests the selection of cpus according to the target count request.
2016-12-04 18:08:25 +00:00
},
{
qemuhotplugtestcpus: Always use 'query-cpus-fast' Use the new command in the test suite by asserting the capability and adjusting test data to the correct field names as they changed compared to 'query-cpus'. Signed-off-by: Peter Krempa <pkrempa@redhat.com> Reviewed-by: Daniel Henrique Barboza <danielhb413@gmail.com>
2020-03-04 11:19:39 +00:00
"target": "x86",
tests: hotplug: Add test infrastructure for testing qemu CPU hotplug code The cpu hotplug operation is rather complex so the testing code needs to provide quite lot of data and monitor conversations to successfully test it. The code mainly tests the selection of cpus according to the target count request.
2016-12-04 18:08:25 +00:00
"current": false,
qemuhotplugtestcpus: Always use 'query-cpus-fast' Use the new command in the test suite by asserting the capability and adjusting test data to the correct field names as they changed compared to 'query-cpus'. Signed-off-by: Peter Krempa <pkrempa@redhat.com> Reviewed-by: Daniel Henrique Barboza <danielhb413@gmail.com>
2020-03-04 11:19:39 +00:00
"cpu-index": 6,
"qom-path": "/machine/peripheral/vcpu6",
tests: hotplug: Add test infrastructure for testing qemu CPU hotplug code The cpu hotplug operation is rather complex so the testing code needs to provide quite lot of data and monitor conversations to successfully test it. The code mainly tests the selection of cpus according to the target count request.
2016-12-04 18:08:25 +00:00
"pc": -2130415978,
"halted": true,
qemuhotplugtestcpus: Always use 'query-cpus-fast' Use the new command in the test suite by asserting the capability and adjusting test data to the correct field names as they changed compared to 'query-cpus'. Signed-off-by: Peter Krempa <pkrempa@redhat.com> Reviewed-by: Daniel Henrique Barboza <danielhb413@gmail.com>
2020-03-04 11:19:39 +00:00
"thread-id": 518298
tests: hotplug: Add test infrastructure for testing qemu CPU hotplug code The cpu hotplug operation is rather complex so the testing code needs to provide quite lot of data and monitor conversations to successfully test it. The code mainly tests the selection of cpus according to the target count request.
2016-12-04 18:08:25 +00:00
}
],
"id": "libvirt-22"
}
Reference in New Issue Copy Permalink