From: Avi Kivity <avi@redhat.com>
To: Bug 899961 <899961@bugs.launchpad.net>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Bug 899961] Re: qemu/kvm locks up when run 32bit userspace with 64bit kernel
Date: Tue, 06 Dec 2011 14:36:55 +0200 [thread overview]
Message-ID: <4EDE0C67.7050003@redhat.com> (raw)
In-Reply-To: <20111204174528.12025.9519.malone@wampee.canonical.com>
On 12/04/2011 07:45 PM, Michael Tokarev wrote:
> Actually after trying to do lots of experiments and finally a git
> bisection, it turned out that the issue only affects qemu-kvm, not
> upstream qemu. Bisection between qemu-kvm 0.15.0 and 1.0 lead to this
> commit:
>
> commit 145e11e840500e04a4d0a624918bb17596be19e9
> Merge: ce967f6 b195043
> Author: Avi Kivity <avi@redhat.com>
> Date: Wed Aug 10 12:06:58 2011 +0300
>
> Merge commit 'b195043003d90ea4027ea01cc7a6c974ac915108' into upstream-merge
>
> * commit 'b195043003d90ea4027ea01cc7a6c974ac915108': (130 commits)
> ...
>
> After which I'm stuck... ;)
>
32-on-64 doesn't build on Fedora due to glib2-devel.i686 conflicting
with its x86_64 cousin, so I can't reproduce this. Can you try
bisecting this further?
$ git tag M b195043003d90ea4027ea01cc7a6c974ac915108
$ git bisect start M M^
...
$ git merge --no-commit M^
[build and test]
$ git merge --abort (or git checkout -f)
$ git bisect [good|bad]
if it happens that M^2 was the bad commit, you'll get a merge conflict.
In that case do
$ git merge --abort
$ git merge M
(you'll just be testing M again, but it's good to verify)
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2011-12-06 12:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-04 16:16 [Qemu-devel] [Bug 899961] [NEW] qemu/kvm locks up when run 32bit userspace with 64bit kernel Michael Tokarev
2011-12-04 17:45 ` [Qemu-devel] [Bug 899961] " Michael Tokarev
2011-12-06 12:36 ` Avi Kivity [this message]
2011-12-04 18:09 ` Michael Tokarev
2011-12-06 11:54 ` Michael Tokarev
2011-12-16 9:08 ` Michael Tokarev
2011-12-18 15:26 ` Bug Watch Updater
2012-03-15 19:29 ` Michael Tokarev
2012-03-16 15:31 ` Michael Tokarev
2012-03-16 15:34 ` Michael Tokarev
2012-06-12 22:40 ` Bug Watch Updater
2016-11-09 10:58 ` Thomas Huth
2017-09-13 7:40 ` Thomas Huth
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=4EDE0C67.7050003@redhat.com \
--to=avi@redhat.com \
--cc=899961@bugs.launchpad.net \
--cc=qemu-devel@nongnu.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).