From: Avi Kivity <avi@redhat.com>
To: Eino Malinen <eino.malinen@utu.fi>
Cc: kvm@vger.kernel.org
Subject: Re: Unable to boot guest on kernel 2.6.29.1 with kvm-84 or kvm-85
Date: Mon, 27 Apr 2009 11:57:52 +0300 [thread overview]
Message-ID: <49F57390.6090600@redhat.com> (raw)
In-Reply-To: <20090426221158.GA25016@pancreas.elisa-laajakaista.fi>
Eino Malinen wrote:
>> Can you try a bisect?
>>
>
> I confirm having the same trouble with kvm. Bisect with the vanilla kernel
> gave the following result:
>
> (f438349...|BISECTING)$ git bisect log
> # bad: [8d7bff2d72660d9d60aa371ae3d1356bbf329a09] Linux 2.6.29.1
> # good: [8e0ee43bc2c3e19db56a4adaa9a9b04ce885cd84] Linux 2.6.29
> git bisect start 'v2.6.29.1' 'v2.6.29' '--' 'arch/x86/kvm/' 'virt/kvm/'
> # bad: [f438349efb8247cd0c1d453a4131b1f801bf5691] KVM: VMX: Don't allow
> uninhibited access to EFER on i386
> git bisect bad f438349efb8247cd0c1d453a4131b1f801bf5691
>
> Are the commits splitted more precisely in kvm.git?
>
No (and this is pretty fine granularity -- that commit is a one liner).
So 2.6.29 worked and 2.6.29.1 did not? What is your host cpu type? Are
you running an i386 or x86_64 host?
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-04-27 8:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-26 22:11 Unable to boot guest on kernel 2.6.29.1 with kvm-84 or kvm-85 Eino Malinen
2009-04-27 8:57 ` Avi Kivity [this message]
2009-04-27 17:42 ` Eino Malinen
-- strict thread matches above, loose matches on Subject: below --
2009-05-03 11:49 Kenni Lund
2009-05-03 12:07 ` Avi Kivity
2009-05-01 22:52 Kenni Lund
2009-05-02 7:51 ` Avi Kivity
2009-05-03 10:14 ` Avi Kivity
2009-04-24 14:29 Kenni Lund
2009-04-26 10:43 ` Avi Kivity
2009-04-23 17:21 Kenni Lund
2009-04-23 20:57 ` Bernhard Held
2009-04-25 1:04 ` Marcelo Tosatti
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=49F57390.6090600@redhat.com \
--to=avi@redhat.com \
--cc=eino.malinen@utu.fi \
--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