On 08/15/2010 02:32 AM, Teck Choon Giam wrote:
Can you try to bisect between qemu-kvm-0.12.3 and 0.12.4 to see which commit
introduced the regression?
Actually I am not so sure about how to do the bisecting as the below
steps always produce different configure for me. Any pointers?
# cd /usr/src
# git clone git://git.kernel.org/pub/scm/virt/kvm/qemu-kvm.git
# cd qemu-kvm
# ./configure --help|grep cpu-emulation
--disable-cpu-emulation disables use of qemu cpu emulation code
# git bisect reset master
We are not bisecting.
# git bisect good qemu-kvm-0.12.1.2
You need to start by "git bisect start"
Do you want me to do it for you [Y/n]? y
# git bisect bad qemu-kvm-0.12.2
Bisecting: 14 revisions left to test after this (roughly 4 steps)
[66dbb62824845e91808171a675998706ce359c71] Handle TFTP ERROR from client
# ./configure --help|grep cpu-emulation
show nothing when bisecting... ... configure script is different :(
That's fine - you'll be running upstream qemu instead of qemu-kvm. Just
remember to add -enable-kvm to the command line. Use ./configure
--target-list=x86_64-softtmmu to cut down on compile time.
I'm betting 73b48d914f9 is the cause, but let's see the full bisect.
--
error compiling committee.c: too many arguments to function
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
