From: Bernd Schubert <bernd-schubert@gmx.de>
To: Marcelo Tosatti <mtosatti@redhat.com>
Cc: kvm@vger.kernel.org, Avi Kivity <avi@qumranet.com>,
Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [GIT PULL] KVM fixes for 2.6.26-rc7
Date: Wed, 25 Jun 2008 21:26:19 +0200 [thread overview]
Message-ID: <200806252126.19701.bernd-schubert@gmx.de> (raw)
In-Reply-To: <20080625191723.GA20531@dmt.cnet>
On Wednesday 25 June 2008, Marcelo Tosatti wrote:
> On Wed, Jun 25, 2008 at 08:54:44PM +0200, Bernd Schubert wrote:
> > On Wednesday 25 June 2008, Marcelo Tosatti wrote:
> > > On Wed, Jun 25, 2008 at 06:13:05PM +0200, Bernd Schubert wrote:
> > > > Avi Kivity wrote:
> > > > > Linus, please pull from the repo and branch at:
> > > > >
> > > > > git://git.kernel.org/pub/scm/linux/kernel/git/avi/kvm.git
> > > > > kvm-updates-2.6.26
> > > >
> > > > I just pulled from Linus and now it stalls to boot at
> > > >
> > > > [ 0.616031] pnp: PnP ACPI init
> > > > [ 0.628031] ACPI: bus type pnp registered
> > > > [ 0.640031] pnp: PnP ACPI: found 7 devices
> > > > [ 0.652031] ACPI: ACPI bus type pnp unregistered
> > > > [ 0.660031] SCSI subsystem initialized
> > > > [ 0.664031] PCI: Using ACPI for IRQ routing
> > > > [ 0.692031] PCI-GART: No AMD northbridge found.
> > > >
> > > > The kvm process is at 100% time. Taking the many problems I already
> > > > reported about, 2.6.26 probably will be entirely broken regarding kvm
> > > > :(
> > >
> > > Do you have CONFIG_KVM_CLOCK or CONFIG_KVM_GUEST enabled ?
> > >
> > > There is a known problem with CONFIG_KVM_GUEST being worked on.
> > >
> > > Can you provide this details, and pinpoint which option is the culprit?
> >
> > Just found out, it is CONFIG_KVM_CLOCK. With CONFIG_KVM_CLOCK=y it does
> > boot fine.
>
> You mean with CONFIG_KVM_CLOCK=n it boots fine, I suppose.
Oh sorry, this was supposed to be "With CONFIG_KVM_GUEST=y it boots fine". So
yes, CONFIG_KVM_CLOCK is the culprit.
>
> You should upgrade the guest kernel to the git tree, kvm clock changes
> break compatibility with older kernels.
This __is__ the after updating to recent git (before that my problem was
different). Latest commit is
commit 543cf4cb3fe6f6cae3651ba918b9c56200b257d0
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date: Tue Jun 24 18:58:20 2008 -0700
Linux 2.6.26-rc8
Thanks,
Bernd
next prev parent reply other threads:[~2008-06-25 19:26 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-24 21:05 [GIT PULL] KVM fixes for 2.6.26-rc7 Avi Kivity
2008-06-25 1:12 ` Linus Torvalds
2008-06-25 7:08 ` Avi Kivity
2008-06-25 16:13 ` Bernd Schubert
2008-06-25 17:19 ` Marcelo Tosatti
2008-06-25 18:54 ` Bernd Schubert
2008-06-25 19:17 ` Marcelo Tosatti
2008-06-25 19:26 ` Bernd Schubert [this message]
2008-06-25 19:33 ` Marcelo Tosatti
2008-06-25 19:44 ` Bernd Schubert
2008-06-26 6:20 ` Gerd Hoffmann
2008-06-26 8:45 ` Bernd Schubert
2008-06-26 9:07 ` Gerd Hoffmann
2008-06-26 12:48 ` Anthony Liguori
2008-06-26 12:52 ` Avi Kivity
2008-06-26 13:12 ` Soren Hansen
2008-06-29 10:03 ` Avi Kivity
2008-06-26 13:43 ` Soren Hansen
2008-06-26 14:00 ` Gerd Hoffmann
2008-06-26 14:25 ` Soren Hansen
2008-06-29 8:59 ` Avi Kivity
2008-06-30 13:21 ` Soren Hansen
2008-06-30 13:39 ` Avi Kivity
2008-06-30 14:21 ` Soren Hansen
2008-06-30 14:35 ` Avi Kivity
2008-06-27 5:18 ` Jeremy Fitzhardinge
2008-06-28 4:02 ` Avi Kivity
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=200806252126.19701.bernd-schubert@gmx.de \
--to=bernd-schubert@gmx.de \
--cc=avi@qumranet.com \
--cc=kraxel@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
/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