Michal Privoznik b44898dd31 virsysinfo: Parse OEM strings ... Setting OEM strings for a domain was introduced in v4.1.0-rc1~315. However, any application that wanted to use them (e.g. to point to an URL where a config file is stored) had to 'dmidecode -u --oem-string N' (where N is index of the string). Well, we can expose them under our <sysinfo/> XML and if the domain is running Libvirt inside it can be obtained using virConnectGetSysinfo() API. 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	virsysinfo: Parse OEM strings	2020-06-10 14:00:38 +02:00
x86sysinfo.expect	virsysinfo: Parse OEM strings	2020-06-10 14:00:38 +02:00