Re: [libvirt] libvirt 0.8.7 tests failure on arm and ppc

2011/2/15 Daniel Veillard <veillard(a)redhat.com&gt;: >  I reproduced this on a ppc64 box (RHEL-6) and get: > > 122) QEMU XML-2-ARGV cpu-topology2                                     ... libvir: QEMU error : unsupported configuration: CPU specification not supported by hypervisor > FAILED > 123) QEMU XML-2-ARGV cpu-topology3                                     ... OK > 124) QEMU XML-2-ARGV cpu-minimum1                                      ... libvir: QEMU error : unsupported configuration: CPU specification not supported by hypervisor > FAILED > 125) QEMU XML-2-ARGV cpu-minimum2                                      ... libvir: QEMU error : unsupported configuration: CPU specification not supported by hypervisor > FAILED > 126) QEMU XML-2-ARGV cpu-exact1                                        ... libvir: QEMU error : unsupported configuration: CPU specification not supported by hypervisor > FAILED > 127) QEMU XML-2-ARGV cpu-exact2                                        ... libvir: QEMU error : unsupported configuration: CPU specification not supported by hypervisor > FAILED > 128) QEMU XML-2-ARGV cpu-strict1                                       ... libvir: QEMU error : unsupported configuration: CPU specification not supported by hypervisor > FAILED > >  I would guess it's related to tests/qemuxml2argvdata/qemu.sh > not "providing" the CPU wanted by the tests in the faked_cpu() > > Daniel > Daniel, that's a different problem. Serge said that 6 out of the last 7 tests in 0.8.7 fail for him. These are hostdev-pci-address, restore-v1, restore-v2, restore-v2, migrate and qemu-ns-no-env. The tests that are failing for you were added after 0.8.7.

So we have two ARM/PPC related problems here. Daniel. qemuxml2argvtest outputs the capabilities, does it contain a host/cpu element? Maybe the problem it that the CPU data decoding in libvirt is x86 specific as it relies on the CPUID command.