Implement getHost() of cpuDriverX86 for non-x86_64 hosts
Recent commit bbbf774f changed the 'graphics-spice-timeout' test to not do a CPU check (check='none') with this following CPU, running with KVM accel:
<cpu match='exact' check='none'>
<model>core2duo</model>
<vendor>Intel</vendor>
<topology sockets='1' dies='1' cores='2' threads='1'/>
<feature policy='require' name='ds'/>
<feature policy='require' name='acpi'/>
<feature policy='require' name='ss'/>
<feature policy='require' name='ht'/>
<feature policy='require' name='tm'/>
<feature policy='require' name='pbe'/>
<feature policy='require' name='ds_cpl'/>
<feature policy='require' name='vmx'/>
<feature policy='require' name='est'/>
<feature policy='require' name='tm2'/>
<feature policy='require' name='cx16'/>
<feature policy='require' name='xtpr'/>
<feature policy='require' name='lahf_lm'/>
</cpu>
For non-86 hosts, the getHost() interface from the x86 CPU driver isn't implemented. This means that under certain conditions, e.g. running the test in a ppc64 or s390x host, with 'latest' caps, KVM accel, with a lot of features marked as 'require' and with a specific vendor, the test will eventually break in qemuProcessUpdateGuestCPU(). See the commit message of bbbf774f for more information about how these conditions were triggering a test error in 'graphics-spice-timeout'.
A more permanent solution would be to implement a mock for the getHost() interface of the cpuDriverX86 that is arch-agnostic, avoiding future KVM tests to break if more unusual conditions are met at the same time.
This is a low priority feature since 'graphics-spice-timeout' is a rather special test that checks a lot of boxes at the same time and it was already amended, but nevertheless a good enhancement to have.