From: Avi Kivity <avi@redhat.com>
To: Teck Choon Giam <giamteckchoon@gmail.com>
Cc: kvm@vger.kernel.org
Subject: Re: system_powerdown not working for qemu-kvm 0.12.4?
Date: Sun, 15 Aug 2010 14:00:34 +0300 [thread overview]
Message-ID: <4C67C8D2.5000400@redhat.com> (raw)
In-Reply-To: <AANLkTik2TjWx8YbseR+gnSyU6JkBm7X5uabiymBaXUyh@mail.gmail.com>
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
next prev parent reply other threads:[~2010-08-15 16:08 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-15 1:19 system_powerdown not working for qemu-kvm 0.12.4? Teck Choon Giam
2010-05-15 9:36 ` Michael Tokarev
2010-05-16 11:52 ` Avi Kivity
2010-05-19 9:23 ` Teck Choon Giam
2010-05-19 16:22 ` Avi Kivity
2010-08-14 23:32 ` Teck Choon Giam
2010-08-15 11:00 ` Avi Kivity [this message]
2010-08-15 16:15 ` Teck Choon Giam
2010-08-15 16:19 ` Avi Kivity
2010-08-15 17:53 ` Teck Choon Giam
2010-10-07 12:30 ` Teck Choon Giam
2010-10-11 16:29 ` Ruben Kerkhof
2010-10-11 16:57 ` Avi Kivity
2010-10-11 17:53 ` Ruben Kerkhof
2010-10-12 6:49 ` Avi Kivity
2010-10-12 7:11 ` Kevin O'Connor
2010-10-12 7:14 ` Gleb Natapov
2010-10-12 7:25 ` Avi Kivity
2010-10-12 7:33 ` Avi Kivity
2010-10-12 7:39 ` Avi Kivity
2010-10-12 7:40 ` Gleb Natapov
2010-10-12 7:44 ` Avi Kivity
2010-10-15 1:45 ` Ruben Kerkhof
2010-10-15 7:01 ` Gleb Natapov
2010-10-15 14:26 ` Ruben Kerkhof
2010-10-15 15:53 ` Teck Choon Giam
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4C67C8D2.5000400@redhat.com \
--to=avi@redhat.com \
--cc=giamteckchoon@gmail.com \
--cc=kvm@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).