public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Carlo Marcelo Arenas Belon <carenas@sajinet.com.pe>
To: Antoine Martin <antoine@nagafix.co.uk>
Cc: Avi Kivity <avi@qumranet.com>,
	kvm-devel@lists.sourceforge.net,
	Linux Kernel Development <linux-kernel@vger.kernel.org>
Subject: Re: [kvm-devel] boot stops after console handover?
Date: Sat, 12 Jan 2008 21:10:33 -0600	[thread overview]
Message-ID: <20080113031033.GA21813@tapir> (raw)
In-Reply-To: <47896711.4050909@nagafix.co.uk>

On Sun, Jan 13, 2008 at 01:19:13AM +0000, Antoine Martin wrote:
> Carlo Marcelo Arenas Belon wrote:
> > On Sat, Jan 12, 2008 at 11:01:28PM +0200, Avi Kivity wrote:
> >> Antoine Martin wrote:
> >>
> >>> FYI, just tried building 2.6.24-rc7-git4 and got this warning:
> >>> (...)
> >> Probably harmless, but worth reporting to lkml.
> > 
> > couldn't replicate it here, but I'd seen usually those kind of errors
> > when building a kernel that hasn't been "mrproper" between re-configurations
> > 
> cp .config ../config-2.6.24-rc7-git4
> make mrproper
> cp ../config-2.6.24-rc7-git4 .config

make oldconfig  # presumed

> make -j 4

replicated with your configuration, but can't still reproduce it with mine
even when forcing as you do

  CONFIG_KVM=y
  CONFIG_KVM_INTEL=y

available from :

  http://tapir.sajinet.com.pe/kvm/config-2.6.24-rc7-git4

> (...)
>   MODPOST vmlinux.o
> WARNING: vmlinux.o(.text+0x2cb657): Section mismatch: reference to
> .init.text:register_cpu_notifier (between 'kvm_init_x86' and 'kvm_sched_in')
> WARNING: vmlinux.o(.text.head+0xe4): Section mismatch: reference to
> .init.data.2:trampoline_level4_pgt (between 'ident_complete' and
> 'secondary_startup_64')
> WARNING: vmlinux.o(.text.head+0xeb): Section mismatch: reference to
> .init.data.2:trampoline_level4_pgt (between 'ident_complete' and
> 'secondary_startup_64')
>   LD      vmlinux
>   SYSMAP  System.map
>   SYSMAP  .tmp_System.map
> 
> You can grab the .config here:
> http://194.145.196.85/kvm/config-2.6.24-rc7-git4

is this the configuration for the host kernel?

if you want to use the last code for kvm you should have CONFIG_KVM disabled
and instead use the external module as instructed in (HINT: you don't have a
patched kernel) :

  http://kvm.qumranet.com/kvmwiki/HOWTO1

not sure which version will be part of 2.6.24 but I suspect it might not be
kvm 59.

Carlo

      reply	other threads:[~2008-01-13  3:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <47812BC3.6060503@nagafix.co.uk>
     [not found] ` <4781EDE3.2000008@qumranet.com>
     [not found]   ` <47827DE4.2020306@nagafix.co.uk>
     [not found]     ` <47833572.7090902@qumranet.com>
     [not found]       ` <4783C6CC.1050404@nagafix.co.uk>
     [not found]         ` <478901D7.1060404@nagafix.co.uk>
     [not found]           ` <47892AA8.6090406@qumranet.com>
     [not found]             ` <20080112222501.GA17084@tapir>
2008-01-13  1:19               ` [kvm-devel] boot stops after console handover? Antoine Martin
2008-01-13  3:10                 ` Carlo Marcelo Arenas Belon [this message]

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=20080113031033.GA21813@tapir \
    --to=carenas@sajinet.com.pe \
    --cc=antoine@nagafix.co.uk \
    --cc=avi@qumranet.com \
    --cc=kvm-devel@lists.sourceforge.net \
    --cc=linux-kernel@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