Michal Privoznik d954fbc74e sysinfotest: Move from custom dmidecode scripts to virCommandSetDryRun() ...

Problem with custom dmidecode scripts is that they are hard to
modify, especially if we will want them to act differently based
on passed arguments. So far, we have two scripts which do no more
than 'cat $sysinfo' where $sysinfo is saved dmidecode output.

The virCommandSetDryRun() can be used to trick
virSysinfoReadDMI() thinking it executed real dmidecode.

Signed-off-by: Michal Privoznik <mprivozn@redhat.com>
Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>

2020-06-10 14:00:38 +02:00

..

aarch64-gigabytecpuinfo.data

…

aarch64-gigabytesysinfo.data

…

aarch64-gigabytesysinfo.expect

virSysinfoReadARM: Try reading DMI table

2019-06-03 17:59:38 +02:00

aarch64-moonshotcpuinfo.data

…

aarch64-moonshotsysinfo.expect

…

aarch64cpuinfo.data

…

aarch64sysinfo.expect

…

arm-rpi2cpuinfo.data

…

arm-rpi2sysinfo.expect

…

armcpuinfo.data

…

armsysinfo.expect

…

ppccpuinfo.data

…

ppcsysinfo.expect

…

s390-freqcpuinfo.data

…

s390-freqsysinfo.data

…

s390-freqsysinfo.expect

…

s390cpuinfo.data

…

s390sysinfo.data

…

s390sysinfo.expect

…

x86sysinfo.data

…

x86sysinfo.expect

…