External/libvirt
1
0
Fork 0
mirror of https://gitlab.com/libvirt/libvirt.git synced 2025-01-03 11:35:19 +00:00
Code Issues Packages Projects Releases Wiki Activity
886fd169c5
libvirt/tests/sysinfodata/aarch64-hpe-apollosysinfo.expect

89 lines
3.6 KiB
Plaintext
Raw Normal View History

tests: Add HPE Apollo test case to sysinfotest Introduce a test case for sysinfotest. The data was obtained by running dmidecode as libvirt would run it: dmidecode -q -t 0,1,2,3,4,11,17 Now, the expected output fits almost perfectly, except for OEM strings where the third string looks nothing like in the dmidecode output. This is because of testDMIDecodeDryRun() which overwrites the third OEM string (see v6.5.0-rc1~214 for more info). But that's okay for now. Speaking of OEM strings, it's worth noticing two 'OEM Strings' sections in the dmidecode output. This is causing some troubles and will be fixed in next commit. Signed-off-by: Michal Privoznik <mprivozn@redhat.com> Reviewed-by: Jiri Denemark <jdenemar@redhat.com>
2024-07-18 06:22:27 +00:00
<sysinfo type='smbios'>
<bios>
<entry name='vendor'>EDK II</entry>
<entry name='version'>L50_5.13_1.11</entry>
<entry name='date'>06/18/2019</entry>
<entry name='release'>7.2</entry>
</bios>
<system>
<entry name='manufacturer'>HPE</entry>
<entry name='product'>Apollo 70</entry>
<entry name='version'>X1</entry>
<entry name='serial'>0000000000</entry>
<entry name='uuid'>69d9c240-bfde-1000-03ca-ea3db8730904</entry>
<entry name='sku'>P00367-B21</entry>
<entry name='family'>CN99XX</entry>
</system>
<baseBoard>
<entry name='manufacturer'>HPE</entry>
<entry name='product'>C01_APACHE_MB</entry>
<entry name='version'>876453-001</entry>
<entry name='serial'>PWJBD0AR9BI016</entry>
<entry name='asset'>PWJBD0AR9BI016</entry>
<entry name='location'>Default string</entry>
</baseBoard>
<chassis>
<entry name='manufacturer'>HPE</entry>
<entry name='version'>P00367-B21</entry>
<entry name='serial'>0000000000</entry>
<entry name='asset'>0000000000</entry>
<entry name='sku'>Default string</entry>
</chassis>
<processor>
<entry name='socket_destination'>Socket 0</entry>
<entry name='type'>Central Processor</entry>
<entry name='family'>ARM</entry>
<entry name='manufacturer'>Cavium Inc.</entry>
<entry name='signature'>Implementor 0x43, Variant 0x1, Architecture 15, Part 0x0af, Revision 1</entry>
<entry name='version'>Cavium ThunderX2(R) CPU CN9975 v2.1 @ 2.0GHz</entry>
<entry name='external_clock'>33 MHz</entry>
<entry name='max_speed'>2500 MHz</entry>
<entry name='status'>Populated, Enabled</entry>
<entry name='serial_number'>0000115D-1AEA3248</entry>
<entry name='part_number'>CN9975-2000LG4077-Y21-G</entry>
</processor>
<processor>
<entry name='socket_destination'>Socket 1</entry>
<entry name='type'>Central Processor</entry>
<entry name='family'>ARM</entry>
<entry name='manufacturer'>Cavium Inc.</entry>
<entry name='signature'>Implementor 0x43, Variant 0x1, Architecture 15, Part 0x0af, Revision 1</entry>
<entry name='version'>Cavium ThunderX2(R) CPU CN9975 v2.1 @ 2.0GHz</entry>
<entry name='external_clock'>33 MHz</entry>
<entry name='max_speed'>2500 MHz</entry>
<entry name='status'>Populated, Enabled</entry>
<entry name='serial_number'>0000115D-2AEA322B</entry>
<entry name='part_number'>CN9975-2000LG4077-Y21-G</entry>
</processor>
<memory_device>
<entry name='size'>16 GB</entry>
<entry name='form_factor'>DIMM</entry>
<entry name='locator'>DIMM_A0</entry>
<entry name='bank_locator'>N0</entry>
<entry name='type'>DDR4</entry>
<entry name='type_detail'>Registered (Buffered)</entry>
<entry name='speed'>2666 MT/s</entry>
<entry name='manufacturer'>Hyundai Electronics</entry>
<entry name='serial_number'>1112731123</entry>
<entry name='part_number'>HMA82GR7CJR8N-VK</entry>
</memory_device>
<memory_device>
<entry name='size'>16 GB</entry>
<entry name='form_factor'>DIMM</entry>
<entry name='locator'>DIMM_I0</entry>
<entry name='bank_locator'>N1</entry>
<entry name='type'>DDR4</entry>
<entry name='type_detail'>Registered (Buffered)</entry>
<entry name='speed'>2666 MT/s</entry>
<entry name='manufacturer'>Hyundai Electronics</entry>
<entry name='serial_number'>1112731032</entry>
<entry name='part_number'>HMA82GR7CJR8N-VK</entry>
</memory_device>
<oemStrings>
<entry>Default string</entry>
<entry>ThunderX2 System</entry>
virsysinfo: Calculate OEM string index better As can be seen in earlier commits, there can be two OEM strings with the same index. But since our parser (virSysinfoParseOEMStrings()) doesn't expect that, it increments index in each run and thus skips over these strings. Fortunately, we have the right index at hand - we're just skipping over it in a loop. Just reconstruct the index back inside the loop. Signed-off-by: Michal Privoznik <mprivozn@redhat.com> Reviewed-by: Jiri Denemark <jdenemar@redhat.com>
2024-07-18 13:09:22 +00:00
<entry>Some valid OEM string</entry>
tests: Add HPE Apollo test case to sysinfotest Introduce a test case for sysinfotest. The data was obtained by running dmidecode as libvirt would run it: dmidecode -q -t 0,1,2,3,4,11,17 Now, the expected output fits almost perfectly, except for OEM strings where the third string looks nothing like in the dmidecode output. This is because of testDMIDecodeDryRun() which overwrites the third OEM string (see v6.5.0-rc1~214 for more info). But that's okay for now. Speaking of OEM strings, it's worth noticing two 'OEM Strings' sections in the dmidecode output. This is causing some troubles and will be fixed in next commit. Signed-off-by: Michal Privoznik <mprivozn@redhat.com> Reviewed-by: Jiri Denemark <jdenemar@redhat.com>
2024-07-18 06:22:27 +00:00
<entry>Comanche</entry>
</oemStrings>
</sysinfo>
Reference in New Issue Copy Permalink