shaba/libvirt
1
0
Fork 0
mirror of https://gitlab.com/libvirt/libvirt.git synced 2025-01-10 05:17:59 +03:00
Code Releases Activity
4ce1106277
libvirt/tests/qemumonitorjsondata/qemumonitorjson-cpuinfo-x86-full.data

110 lines
2.9 KiB
Plaintext
Raw Normal View History

tests: cpu-hotplug: Add data for x86 hotplug with 11+ vcpus During review it was reported that adding at least 11 vcpus creates a collision of prefixes in the monitor matching algorithm. Add a test case to verify that the problem won't happen.
2016-08-24 00:05:52 +03:00
[vcpu libvirt-id='0']
qemu: monitor: Add vcpu state information to monitor data Return whether a vcpu entry is hotpluggable or online so that upper layers don't have to infer the information from other data. Advantage is that this code can be tested by unit tests.
2016-09-13 18:52:38 +03:00
online=yes
hotpluggable=no
tests: cpu-hotplug: Add data for x86 hotplug with 11+ vcpus During review it was reported that adding at least 11 vcpus creates a collision of prefixes in the monitor matching algorithm. Add a test case to verify that the problem won't happen.
2016-08-24 00:05:52 +03:00
thread-id='895040'
tests: qemumonitorjson: Rename 'qemu-id' to 'enable-id' in cpu info test The field is named 'enable_id' in other structures and a patch recently added 'qemu_id' which has different semantics. To avoid confusion in the tests rename the field.
2016-11-22 12:21:46 +03:00
enable-id='1'
qemu: monitor: Properly propagate the 'qemu_id' field through the matcher Commit 3f71c797689a4a70 added 'qemu_id' field to track the id of the cpu as reported by query-cpus. The patch did not include changes necessary to propagate the id through the functions matching the data to the libvirt cpu structures and thus all vcpus had id 0.
2016-11-22 11:32:11 +03:00
query-cpus-id='0'
tests: cpu-hotplug: Add data for x86 hotplug with 11+ vcpus During review it was reported that adding at least 11 vcpus creates a collision of prefixes in the monitor matching algorithm. Add a test case to verify that the problem won't happen.
2016-08-24 00:05:52 +03:00
type='Broadwell-x86_64-cpu'
qom_path='/machine/unattached/device[0]'
topology: socket='0' core='0' thread='0' vcpus='1'
[vcpu libvirt-id='1']
qemu: monitor: Add vcpu state information to monitor data Return whether a vcpu entry is hotpluggable or online so that upper layers don't have to infer the information from other data. Advantage is that this code can be tested by unit tests.
2016-09-13 18:52:38 +03:00
online=yes
hotpluggable=yes
tests: cpu-hotplug: Add data for x86 hotplug with 11+ vcpus During review it was reported that adding at least 11 vcpus creates a collision of prefixes in the monitor matching algorithm. Add a test case to verify that the problem won't happen.
2016-08-24 00:05:52 +03:00
thread-id='895056'
tests: qemumonitorjson: Rename 'qemu-id' to 'enable-id' in cpu info test The field is named 'enable_id' in other structures and a patch recently added 'qemu_id' which has different semantics. To avoid confusion in the tests rename the field.
2016-11-22 12:21:46 +03:00
enable-id='2'
qemu: monitor: Properly propagate the 'qemu_id' field through the matcher Commit 3f71c797689a4a70 added 'qemu_id' field to track the id of the cpu as reported by query-cpus. The patch did not include changes necessary to propagate the id through the functions matching the data to the libvirt cpu structures and thus all vcpus had id 0.
2016-11-22 11:32:11 +03:00
query-cpus-id='1'
tests: cpu-hotplug: Add data for x86 hotplug with 11+ vcpus During review it was reported that adding at least 11 vcpus creates a collision of prefixes in the monitor matching algorithm. Add a test case to verify that the problem won't happen.
2016-08-24 00:05:52 +03:00
type='Broadwell-x86_64-cpu'
alias='vcpu1'
qom_path='/machine/peripheral/vcpu1'
topology: socket='1' core='0' thread='0' vcpus='1'
[vcpu libvirt-id='2']
qemu: monitor: Add vcpu state information to monitor data Return whether a vcpu entry is hotpluggable or online so that upper layers don't have to infer the information from other data. Advantage is that this code can be tested by unit tests.
2016-09-13 18:52:38 +03:00
online=yes
hotpluggable=yes
tests: cpu-hotplug: Add data for x86 hotplug with 11+ vcpus During review it was reported that adding at least 11 vcpus creates a collision of prefixes in the monitor matching algorithm. Add a test case to verify that the problem won't happen.
2016-08-24 00:05:52 +03:00
thread-id='895057'
tests: qemumonitorjson: Rename 'qemu-id' to 'enable-id' in cpu info test The field is named 'enable_id' in other structures and a patch recently added 'qemu_id' which has different semantics. To avoid confusion in the tests rename the field.
2016-11-22 12:21:46 +03:00
enable-id='3'
qemu: monitor: Properly propagate the 'qemu_id' field through the matcher Commit 3f71c797689a4a70 added 'qemu_id' field to track the id of the cpu as reported by query-cpus. The patch did not include changes necessary to propagate the id through the functions matching the data to the libvirt cpu structures and thus all vcpus had id 0.
2016-11-22 11:32:11 +03:00
query-cpus-id='2'
tests: cpu-hotplug: Add data for x86 hotplug with 11+ vcpus During review it was reported that adding at least 11 vcpus creates a collision of prefixes in the monitor matching algorithm. Add a test case to verify that the problem won't happen.
2016-08-24 00:05:52 +03:00
type='Broadwell-x86_64-cpu'
alias='vcpu2'
qom_path='/machine/peripheral/vcpu2'
topology: socket='2' core='0' thread='0' vcpus='1'
[vcpu libvirt-id='3']
qemu: monitor: Add vcpu state information to monitor data Return whether a vcpu entry is hotpluggable or online so that upper layers don't have to infer the information from other data. Advantage is that this code can be tested by unit tests.
2016-09-13 18:52:38 +03:00
online=yes
hotpluggable=yes
tests: cpu-hotplug: Add data for x86 hotplug with 11+ vcpus During review it was reported that adding at least 11 vcpus creates a collision of prefixes in the monitor matching algorithm. Add a test case to verify that the problem won't happen.
2016-08-24 00:05:52 +03:00
thread-id='895058'
tests: qemumonitorjson: Rename 'qemu-id' to 'enable-id' in cpu info test The field is named 'enable_id' in other structures and a patch recently added 'qemu_id' which has different semantics. To avoid confusion in the tests rename the field.
2016-11-22 12:21:46 +03:00
enable-id='4'
qemu: monitor: Properly propagate the 'qemu_id' field through the matcher Commit 3f71c797689a4a70 added 'qemu_id' field to track the id of the cpu as reported by query-cpus. The patch did not include changes necessary to propagate the id through the functions matching the data to the libvirt cpu structures and thus all vcpus had id 0.
2016-11-22 11:32:11 +03:00
query-cpus-id='3'
tests: cpu-hotplug: Add data for x86 hotplug with 11+ vcpus During review it was reported that adding at least 11 vcpus creates a collision of prefixes in the monitor matching algorithm. Add a test case to verify that the problem won't happen.
2016-08-24 00:05:52 +03:00
type='Broadwell-x86_64-cpu'
alias='vcpu3'
qom_path='/machine/peripheral/vcpu3'
topology: socket='3' core='0' thread='0' vcpus='1'
[vcpu libvirt-id='4']
qemu: monitor: Add vcpu state information to monitor data Return whether a vcpu entry is hotpluggable or online so that upper layers don't have to infer the information from other data. Advantage is that this code can be tested by unit tests.
2016-09-13 18:52:38 +03:00
online=yes
hotpluggable=yes
tests: cpu-hotplug: Add data for x86 hotplug with 11+ vcpus During review it was reported that adding at least 11 vcpus creates a collision of prefixes in the monitor matching algorithm. Add a test case to verify that the problem won't happen.
2016-08-24 00:05:52 +03:00
thread-id='895059'
tests: qemumonitorjson: Rename 'qemu-id' to 'enable-id' in cpu info test The field is named 'enable_id' in other structures and a patch recently added 'qemu_id' which has different semantics. To avoid confusion in the tests rename the field.
2016-11-22 12:21:46 +03:00
enable-id='5'
qemu: monitor: Properly propagate the 'qemu_id' field through the matcher Commit 3f71c797689a4a70 added 'qemu_id' field to track the id of the cpu as reported by query-cpus. The patch did not include changes necessary to propagate the id through the functions matching the data to the libvirt cpu structures and thus all vcpus had id 0.
2016-11-22 11:32:11 +03:00
query-cpus-id='4'
tests: cpu-hotplug: Add data for x86 hotplug with 11+ vcpus During review it was reported that adding at least 11 vcpus creates a collision of prefixes in the monitor matching algorithm. Add a test case to verify that the problem won't happen.
2016-08-24 00:05:52 +03:00
type='Broadwell-x86_64-cpu'
alias='vcpu4'
qom_path='/machine/peripheral/vcpu4'
topology: socket='4' core='0' thread='0' vcpus='1'
[vcpu libvirt-id='5']
qemu: monitor: Add vcpu state information to monitor data Return whether a vcpu entry is hotpluggable or online so that upper layers don't have to infer the information from other data. Advantage is that this code can be tested by unit tests.
2016-09-13 18:52:38 +03:00
online=yes
hotpluggable=yes
tests: cpu-hotplug: Add data for x86 hotplug with 11+ vcpus During review it was reported that adding at least 11 vcpus creates a collision of prefixes in the monitor matching algorithm. Add a test case to verify that the problem won't happen.
2016-08-24 00:05:52 +03:00
thread-id='895060'
tests: qemumonitorjson: Rename 'qemu-id' to 'enable-id' in cpu info test The field is named 'enable_id' in other structures and a patch recently added 'qemu_id' which has different semantics. To avoid confusion in the tests rename the field.
2016-11-22 12:21:46 +03:00
enable-id='6'
qemu: monitor: Properly propagate the 'qemu_id' field through the matcher Commit 3f71c797689a4a70 added 'qemu_id' field to track the id of the cpu as reported by query-cpus. The patch did not include changes necessary to propagate the id through the functions matching the data to the libvirt cpu structures and thus all vcpus had id 0.
2016-11-22 11:32:11 +03:00
query-cpus-id='5'
tests: cpu-hotplug: Add data for x86 hotplug with 11+ vcpus During review it was reported that adding at least 11 vcpus creates a collision of prefixes in the monitor matching algorithm. Add a test case to verify that the problem won't happen.
2016-08-24 00:05:52 +03:00
type='Broadwell-x86_64-cpu'
alias='vcpu5'
qom_path='/machine/peripheral/vcpu5'
topology: socket='5' core='0' thread='0' vcpus='1'
[vcpu libvirt-id='6']
qemu: monitor: Add vcpu state information to monitor data Return whether a vcpu entry is hotpluggable or online so that upper layers don't have to infer the information from other data. Advantage is that this code can be tested by unit tests.
2016-09-13 18:52:38 +03:00
online=yes
hotpluggable=yes
tests: cpu-hotplug: Add data for x86 hotplug with 11+ vcpus During review it was reported that adding at least 11 vcpus creates a collision of prefixes in the monitor matching algorithm. Add a test case to verify that the problem won't happen.
2016-08-24 00:05:52 +03:00
thread-id='895061'
tests: qemumonitorjson: Rename 'qemu-id' to 'enable-id' in cpu info test The field is named 'enable_id' in other structures and a patch recently added 'qemu_id' which has different semantics. To avoid confusion in the tests rename the field.
2016-11-22 12:21:46 +03:00
enable-id='7'
qemu: monitor: Properly propagate the 'qemu_id' field through the matcher Commit 3f71c797689a4a70 added 'qemu_id' field to track the id of the cpu as reported by query-cpus. The patch did not include changes necessary to propagate the id through the functions matching the data to the libvirt cpu structures and thus all vcpus had id 0.
2016-11-22 11:32:11 +03:00
query-cpus-id='6'
tests: cpu-hotplug: Add data for x86 hotplug with 11+ vcpus During review it was reported that adding at least 11 vcpus creates a collision of prefixes in the monitor matching algorithm. Add a test case to verify that the problem won't happen.
2016-08-24 00:05:52 +03:00
type='Broadwell-x86_64-cpu'
alias='vcpu6'
qom_path='/machine/peripheral/vcpu6'
topology: socket='6' core='0' thread='0' vcpus='1'
[vcpu libvirt-id='7']
qemu: monitor: Add vcpu state information to monitor data Return whether a vcpu entry is hotpluggable or online so that upper layers don't have to infer the information from other data. Advantage is that this code can be tested by unit tests.
2016-09-13 18:52:38 +03:00
online=yes
hotpluggable=yes
tests: cpu-hotplug: Add data for x86 hotplug with 11+ vcpus During review it was reported that adding at least 11 vcpus creates a collision of prefixes in the monitor matching algorithm. Add a test case to verify that the problem won't happen.
2016-08-24 00:05:52 +03:00
thread-id='895062'
tests: qemumonitorjson: Rename 'qemu-id' to 'enable-id' in cpu info test The field is named 'enable_id' in other structures and a patch recently added 'qemu_id' which has different semantics. To avoid confusion in the tests rename the field.
2016-11-22 12:21:46 +03:00
enable-id='8'
qemu: monitor: Properly propagate the 'qemu_id' field through the matcher Commit 3f71c797689a4a70 added 'qemu_id' field to track the id of the cpu as reported by query-cpus. The patch did not include changes necessary to propagate the id through the functions matching the data to the libvirt cpu structures and thus all vcpus had id 0.
2016-11-22 11:32:11 +03:00
query-cpus-id='7'
tests: cpu-hotplug: Add data for x86 hotplug with 11+ vcpus During review it was reported that adding at least 11 vcpus creates a collision of prefixes in the monitor matching algorithm. Add a test case to verify that the problem won't happen.
2016-08-24 00:05:52 +03:00
type='Broadwell-x86_64-cpu'
alias='vcpu7'
qom_path='/machine/peripheral/vcpu7'
topology: socket='7' core='0' thread='0' vcpus='1'
[vcpu libvirt-id='8']
qemu: monitor: Add vcpu state information to monitor data Return whether a vcpu entry is hotpluggable or online so that upper layers don't have to infer the information from other data. Advantage is that this code can be tested by unit tests.
2016-09-13 18:52:38 +03:00
online=yes
hotpluggable=yes
tests: cpu-hotplug: Add data for x86 hotplug with 11+ vcpus During review it was reported that adding at least 11 vcpus creates a collision of prefixes in the monitor matching algorithm. Add a test case to verify that the problem won't happen.
2016-08-24 00:05:52 +03:00
thread-id='895063'
tests: qemumonitorjson: Rename 'qemu-id' to 'enable-id' in cpu info test The field is named 'enable_id' in other structures and a patch recently added 'qemu_id' which has different semantics. To avoid confusion in the tests rename the field.
2016-11-22 12:21:46 +03:00
enable-id='9'
qemu: monitor: Properly propagate the 'qemu_id' field through the matcher Commit 3f71c797689a4a70 added 'qemu_id' field to track the id of the cpu as reported by query-cpus. The patch did not include changes necessary to propagate the id through the functions matching the data to the libvirt cpu structures and thus all vcpus had id 0.
2016-11-22 11:32:11 +03:00
query-cpus-id='8'
tests: cpu-hotplug: Add data for x86 hotplug with 11+ vcpus During review it was reported that adding at least 11 vcpus creates a collision of prefixes in the monitor matching algorithm. Add a test case to verify that the problem won't happen.
2016-08-24 00:05:52 +03:00
type='Broadwell-x86_64-cpu'
alias='vcpu8'
qom_path='/machine/peripheral/vcpu8'
topology: socket='8' core='0' thread='0' vcpus='1'
[vcpu libvirt-id='9']
qemu: monitor: Add vcpu state information to monitor data Return whether a vcpu entry is hotpluggable or online so that upper layers don't have to infer the information from other data. Advantage is that this code can be tested by unit tests.
2016-09-13 18:52:38 +03:00
online=yes
hotpluggable=yes
tests: cpu-hotplug: Add data for x86 hotplug with 11+ vcpus During review it was reported that adding at least 11 vcpus creates a collision of prefixes in the monitor matching algorithm. Add a test case to verify that the problem won't happen.
2016-08-24 00:05:52 +03:00
thread-id='895064'
tests: qemumonitorjson: Rename 'qemu-id' to 'enable-id' in cpu info test The field is named 'enable_id' in other structures and a patch recently added 'qemu_id' which has different semantics. To avoid confusion in the tests rename the field.
2016-11-22 12:21:46 +03:00
enable-id='10'
qemu: monitor: Properly propagate the 'qemu_id' field through the matcher Commit 3f71c797689a4a70 added 'qemu_id' field to track the id of the cpu as reported by query-cpus. The patch did not include changes necessary to propagate the id through the functions matching the data to the libvirt cpu structures and thus all vcpus had id 0.
2016-11-22 11:32:11 +03:00
query-cpus-id='9'
tests: cpu-hotplug: Add data for x86 hotplug with 11+ vcpus During review it was reported that adding at least 11 vcpus creates a collision of prefixes in the monitor matching algorithm. Add a test case to verify that the problem won't happen.
2016-08-24 00:05:52 +03:00
type='Broadwell-x86_64-cpu'
alias='vcpu9'
qom_path='/machine/peripheral/vcpu9'
topology: socket='9' core='0' thread='0' vcpus='1'
[vcpu libvirt-id='10']
qemu: monitor: Add vcpu state information to monitor data Return whether a vcpu entry is hotpluggable or online so that upper layers don't have to infer the information from other data. Advantage is that this code can be tested by unit tests.
2016-09-13 18:52:38 +03:00
online=yes
hotpluggable=yes
tests: cpu-hotplug: Add data for x86 hotplug with 11+ vcpus During review it was reported that adding at least 11 vcpus creates a collision of prefixes in the monitor matching algorithm. Add a test case to verify that the problem won't happen.
2016-08-24 00:05:52 +03:00
thread-id='895065'
tests: qemumonitorjson: Rename 'qemu-id' to 'enable-id' in cpu info test The field is named 'enable_id' in other structures and a patch recently added 'qemu_id' which has different semantics. To avoid confusion in the tests rename the field.
2016-11-22 12:21:46 +03:00
enable-id='11'
qemu: monitor: Properly propagate the 'qemu_id' field through the matcher Commit 3f71c797689a4a70 added 'qemu_id' field to track the id of the cpu as reported by query-cpus. The patch did not include changes necessary to propagate the id through the functions matching the data to the libvirt cpu structures and thus all vcpus had id 0.
2016-11-22 11:32:11 +03:00
query-cpus-id='10'
tests: cpu-hotplug: Add data for x86 hotplug with 11+ vcpus During review it was reported that adding at least 11 vcpus creates a collision of prefixes in the monitor matching algorithm. Add a test case to verify that the problem won't happen.
2016-08-24 00:05:52 +03:00
type='Broadwell-x86_64-cpu'
alias='vcpu10'
qom_path='/machine/peripheral/vcpu10'
topology: socket='10' core='0' thread='0' vcpus='1'
Copy Permalink