6:59 p.m.
Hi, as per the message after the tests fail, I'm reporting this on
the list. Hopefully someone has seen this before. I've not yet
tried this with the latest git snapshot. With 0.8.7, I get:
TEST: qemuxml2argvtest
........................................ 40
........................................ 80
.............................!.!!!!! 116 FAIL
-serge
3:09 a.m.
2011/2/15 Serge E. Hallyn <serge.hallyn(a)canonical.com>:
Hi, as per the message after the tests fail, I'm reporting this
on
the list. Hopefully someone has seen this before. I've not yet
tried this with the latest git snapshot. With 0.8.7, I get:
TEST: qemuxml2argvtest
........................................ 40
........................................ 80
.............................!.!!!!! 116 FAIL
-serge
I don't have ARM or PPC at hand to test, so I can't really tell why
these tests fail.
Could you rerun this test with more verbose output like this
cd /path/to/libvirt
cd tests
LIBVIRT_LOG_OUTPUTS=3:stderr VIR_TEST_DEBUG=2 \
./qemuxml2argvtest > qemuxml2argvtest.log 2>&1
and attach the qemuxml2argvtest.log.
Matthias
3:41 a.m.
On Tue, Feb 15, 2011 at 10:09:14AM +0100, Matthias Bolte wrote:
2011/2/15 Serge E. Hallyn <serge.hallyn(a)canonical.com>:
> Hi, as per the message after the tests fail, I'm reporting this on
> the list. Hopefully someone has seen this before. I've not yet
> tried this with the latest git snapshot. With 0.8.7, I get:
>
> TEST: qemuxml2argvtest
> ........................................ 40
> ........................................ 80
> .............................!.!!!!! 116 FAIL
>
> -serge
>
I don't have ARM or PPC at hand to test, so I can't really tell why
these tests fail.
Could you rerun this test with more verbose output like this
cd /path/to/libvirt
cd tests
LIBVIRT_LOG_OUTPUTS=3:stderr VIR_TEST_DEBUG=2 \
./qemuxml2argvtest > qemuxml2argvtest.log 2>&1
and attach the qemuxml2argvtest.log.
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 Veillard | libxml Gnome XML XSLT toolkit http://xmlsoft.org/
daniel(a)veillard.com | Rpmfind RPM search engine http://rpmfind.net/
http://veillard.com/ | virtualization library http://libvirt.org/
4 a.m.
2011/2/15 Daniel Veillard <veillard(a)redhat.com>:
On Tue, Feb 15, 2011 at 10:09:14AM +0100, Matthias Bolte wrote:
> 2011/2/15 Serge E. Hallyn <serge.hallyn(a)canonical.com>:
> > Hi, as per the message after the tests fail, I'm reporting this on
> > the list. Hopefully someone has seen this before. I've not yet
> > tried this with the latest git snapshot. With 0.8.7, I get:
> >
> > TEST: qemuxml2argvtest
> > ........................................ 40
> > ........................................ 80
> > .............................!.!!!!! 116 FAIL
> >
> > -serge
> >
>
> I don't have ARM or PPC at hand to test, so I can't really tell why
> these tests fail.
>
> Could you rerun this test with more verbose output like this
>
> cd /path/to/libvirt
> cd tests
> LIBVIRT_LOG_OUTPUTS=3:stderr VIR_TEST_DEBUG=2 \
> ./qemuxml2argvtest > qemuxml2argvtest.log 2>&1
>
> and attach the qemuxml2argvtest.log.
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.
Matthias
4:12 a.m.
On Tue, Feb 15, 2011 at 11:00:06 +0100, Matthias Bolte wrote:
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.
I'm looking into this issue right now.
Jirka
4:23 a.m.
On Tue, Feb 15, 2011 at 11:00:06AM +0100, Matthias Bolte wrote:
2011/2/15 Daniel Veillard <veillard(a)redhat.com>:
> 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.
ah right I tested the rc3 tarball !
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.
The tests which fails are the ones where there is a <cpu match>
and a model is specified. Maybe something changed there, because
tests/qemuxml2argvdata/qemu.sh used emulate the faked cpu on boxes
where qemu isn't available but it seems to not be called any more
with "-cpu ?" and hence can't fake the supported CPU on those boxes.
Daniel
--
Daniel Veillard | libxml Gnome XML XSLT toolkit http://xmlsoft.org/
daniel(a)veillard.com | Rpmfind RPM search engine http://rpmfind.net/
http://veillard.com/ | virtualization library http://libvirt.org/
4:55 a.m.
On Tue, Feb 15, 2011 at 06:23:56PM +0800, Daniel Veillard wrote:
On Tue, Feb 15, 2011 at 11:00:06AM +0100, Matthias Bolte wrote:
> 2011/2/15 Daniel Veillard <veillard(a)redhat.com>:
> > 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.
ah right I tested the rc3 tarball !
Actually I get the exact same errors with libvirt-0.8.7 on that
machine:
110) QEMU XML-2-ARGV cpu-topology2 ... libvir: QEMU
error : unsupported configuration: CPU specification not supported by hypervisor
FAILED
111) QEMU XML-2-ARGV cpu-topology3 ... OK
112) QEMU XML-2-ARGV cpu-minimum1 ... libvir: QEMU
error : unsupported configuration: CPU specification not supported by hypervisor
FAILED
113) QEMU XML-2-ARGV cpu-minimum2 ... libvir: QEMU
error : unsupported configuration: CPU specification not supported by hypervisor
FAILED
114) QEMU XML-2-ARGV cpu-exact1 ... libvir: QEMU
error : unsupported configuration: CPU specification not supported by hypervisor
FAILED
115) QEMU XML-2-ARGV cpu-exact2 ... libvir: QEMU
error : unsupported configuration: CPU specification not supported by hypervisor
FAILED
116) QEMU XML-2-ARGV cpu-strict1 ... libvir: QEMU
error : unsupported configuration: CPU specification not supported by hypervisor
FAILED
[root@ibm-js22-vios-02-lp2 tests]# pwd
note it's a ppc64, not ppc
Daniel
--
Daniel Veillard | libxml Gnome XML XSLT toolkit http://xmlsoft.org/
daniel(a)veillard.com | Rpmfind RPM search engine http://rpmfind.net/
http://veillard.com/ | virtualization library http://libvirt.org/
7:37 a.m.
Quoting Matthias Bolte (matthias.bolte(a)googlemail.com):
2011/2/15 Serge E. Hallyn <serge.hallyn(a)canonical.com>:
> Hi, as per the message after the tests fail, I'm reporting this on
> the list. Hopefully someone has seen this before. I've not yet
> tried this with the latest git snapshot. With 0.8.7, I get:
>
> TEST: qemuxml2argvtest
> ........................................ 40
> ........................................ 80
> .............................!.!!!!! 116 FAIL
>
> -serge
>
I don't have ARM or PPC at hand to test, so I can't really tell why
these tests fail.
Could you rerun this test with more verbose output like this
cd /path/to/libvirt
cd tests
LIBVIRT_LOG_OUTPUTS=3:stderr VIR_TEST_DEBUG=2 \
./qemuxml2argvtest > qemuxml2argvtest.log 2>&1
and attach the qemuxml2argvtest.log.
Matthias
Thanks, Matthias. Here is the output (with 'OK' lines trimmed):
TEST: qemuxml2argvtest
QEMU driver capabilities:
<capabilities>
<host>
<cpu>
<arch>armv7l</arch>
<model>core2duo</model>
<vendor>Intel</vendor>
<topology sockets='1' cores='2' threads='1'/>
<feature name='lahf_lm'/>
<feature name='xtpr'/>
<feature name='cx16'/>
<feature name='tm2'/>
<feature name='est'/>
<feature name='vmx'/>
<feature name='ds_cpl'/>
<feature name='pbe'/>
<feature name='tm'/>
<feature name='ht'/>
<feature name='ss'/>
<feature name='acpi'/>
<feature name='ds'/>
</cpu>
</host>
<guest>
<os_type>hvm</os_type>
<arch name='i686'>
<wordsize>32</wordsize>
<emulator>/usr/bin/qemu</emulator>
<machine>pc</machine>
<machine>isapc</machine>
<domain type='qemu'>
</domain>
</arch>
</guest>
<guest>
<os_type>hvm</os_type>
<arch name='x86_64'>
<wordsize>64</wordsize>
<emulator>/usr/bin/qemu-system-x86_64</emulator>
<machine>pc-0.11</machine>
<machine canonical='pc-0.11'>pc</machine>
<machine>pc-0.10</machine>
<machine>isapc</machine>
<domain type='qemu'>
</domain>
<domain type='kvm'>
<emulator>/usr/bin/kvm</emulator>
<machine>pc</machine>
<machine>isapc</machine>
</domain>
</arch>
</guest>
<guest>
<os_type>xen</os_type>
<arch name='x86_64'>
<wordsize>64</wordsize>
<emulator>/usr/bin/xenner</emulator>
<machine>xenner</machine>
<domain type='kvm'>
<emulator>/usr/bin/kvm</emulator>
</domain>
</arch>
</guest>
</capabilities>
3) QEMU XML-2-ARGV machine-aliases2 ... 13:35:12.002:
8839: error : qemuBuildCommandLine:2550 : unsupported configuration: the QEMU binary
/usr/bin/kvm does not support kvm
OK
9) QEMU XML-2-ARGV bootloader ... 13:35:12.065:
8839: error : qemuBuildCommandLine:2550 : unsupported configuration: the QEMU binary
/usr/bin/xenner does not support kvm
OK
52) QEMU XML-2-ARGV input-xen ... 13:35:12.304:
8839: error : qemuBuildCommandLine:2550 : unsupported configuration: the QEMU binary
/usr/bin/xenner does not support kvm
OK
110) QEMU XML-2-ARGV cpu-topology2 ... 13:35:12.620:
8839: error : qemuBuildCpuArgStr:2300 : unsupported configuration: CPU specification not
supported by hypervisor
libvir: QEMU error : unsupported configuration: CPU specification not supported by
hypervisor
FAILED
111) QEMU XML-2-ARGV cpu-topology3 ... OK
112) QEMU XML-2-ARGV cpu-minimum1 ... 13:35:12.642:
8839: error : qemuBuildCpuArgStr:2300 : unsupported configuration: CPU specification not
supported by hypervisor
libvir: QEMU error : unsupported configuration: CPU specification not supported by
hypervisor
FAILED
113) QEMU XML-2-ARGV cpu-minimum2 ... 13:35:12.653:
8839: error : qemuBuildCpuArgStr:2300 : unsupported configuration: CPU specification not
supported by hypervisor
libvir: QEMU error : unsupported configuration: CPU specification not supported by
hypervisor
FAILED
114) QEMU XML-2-ARGV cpu-exact1 ... 13:35:12.665:
8839: error : qemuBuildCpuArgStr:2300 : unsupported configuration: CPU specification not
supported by hypervisor
libvir: QEMU error : unsupported configuration: CPU specification not supported by
hypervisor
FAILED
115) QEMU XML-2-ARGV cpu-exact2 ... 13:35:12.677:
8839: error : qemuBuildCpuArgStr:2300 : unsupported configuration: CPU specification not
supported by hypervisor
libvir: QEMU error : unsupported configuration: CPU specification not supported by
hypervisor
FAILED
before cpu-strict1
116) QEMU XML-2-ARGV cpu-strict1 ... 13:35:12.689:
8839: error : qemuBuildCpuArgStr:2300 : unsupported configuration: CPU specification not
supported by hypervisor
libvir: QEMU error : unsupported configuration: CPU specification not supported by
hypervisor
FAILED
after cpu-strict1
7:59 a.m.
On Tue, Feb 15, 2011 at 07:37:37 -0600, Serge E. Hallyn wrote:
TEST: qemuxml2argvtest
QEMU driver capabilities:
<capabilities>
<host>
<cpu>
<arch>armv7l</arch>
This is the problem. The code does not properly dealing with the case where
host CPU architecture as described by host capabilities does not match the
architecture of the real host CPU. This case can only happen in tests where we
fake host CPU.
I have a fix for that already. I'll make a proper patch from it and send soon.
Jirka
9:44 a.m.
Quoting Jiri Denemark (jdenemar(a)redhat.com):
On Tue, Feb 15, 2011 at 07:37:37 -0600, Serge E. Hallyn wrote:
> TEST: qemuxml2argvtest
> QEMU driver capabilities:
> <capabilities>
>
> <host>
> <cpu>
> <arch>armv7l</arch>
This is the problem. The code does not properly dealing with the case where
host CPU architecture as described by host capabilities does not match the
architecture of the real host CPU. This case can only happen in tests where we
fake host CPU.
I have a fix for that already. I'll make a proper patch from it and send soon.
Jirka
Thanks!
I'll wait for that and slurp it in. (Presumably the same thing is going
on with my ppc failure.)
thanks,
-serge
5029
days inactive
5029
days old
9 comments
4 participants
participants (4)
-
Daniel Veillard -
Jiri Denemark -
Matthias Bolte -
Serge E. Hallyn