All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: kelu@kelu.dk
Cc: kvm@vger.kernel.org
Subject: Re: Unable to boot guest on kernel 2.6.29.1 with kvm-84 or kvm-85
Date: Sun, 26 Apr 2009 13:43:11 +0300	[thread overview]
Message-ID: <49F43ABF.6070407@redhat.com> (raw)
In-Reply-To: <52934.1240583359@kelu.dk>

Kenni Lund wrote:
> Ok, but as I write in my message, I'm using the KVM modules from the latest
> upstream kernel, not the kvm-85 modules.
>
> According to the KVM download page, http://www.linux-kvm.org/page/Downloads,
> any kernel above 2.6.25 should work with the latest KVM userspace. This has
> been true until now in my case, but it breaks with 2.6.29.1 and that's the reason
> why I'm posting this bug report.
>
>   

Can you try a bisect?

If you bisect only kvm patches it should be pretty fast.  The following 
commands should do it:

  git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-2.6-stable.git

(if you already have a linux git tree somewhere, do 'git remote add -f 
stable 
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-2.6-stable.git' 
instead)

  git bisect start v2.6.29.1 v2.6.28 -- arch/x86/kvm virt/kvm

git will check out a test version, build it and test, and respond with 
'git bisect bad' or 'git bisect good'.  Rinse and repeat.

-- 
error compiling committee.c: too many arguments to function


  reply	other threads:[~2009-04-26 10:43 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-24 14:29 Unable to boot guest on kernel 2.6.29.1 with kvm-84 or kvm-85 Kenni Lund
2009-04-26 10:43 ` Avi Kivity [this message]
  -- 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-26 22:11 Eino Malinen
2009-04-27  8:57 ` Avi Kivity
2009-04-27 17:42   ` Eino Malinen
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=49F43ABF.6070407@redhat.com \
    --to=avi@redhat.com \
    --cc=kelu@kelu.dk \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.