public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Fix <pr0gress0r-ZoOhUfop2Wg@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Oops at boot - kernel 2.6.22.1
Date: Tue, 24 Jul 2007 08:12:55 +0300	[thread overview]
Message-ID: <46A58A57.5080900@qumranet.com> (raw)
In-Reply-To: <200707240320.16070.pr0gress0r-ZoOhUfop2Wg@public.gmane.org>

Fix wrote:
>>> Host system: Linux
>>> Processor: Athlon64 X2 3600+
>>> Kernel: 2.6.22.1
>>> KVM version: 31
>>>
>>> Guest system: Linux
>>> Kernel: 2.6.22.1
>>>
>>> $ kvm -hda linux.img -boot c -m 256
>>>
>>> Host system freeze immediately after pressing <Enter> in
>>> LILO
>>>
>>> /var/log/messages:
>>>
>>> Jul 23 11:57:10 linux kernel: Unable to handle kernel NULL
>>> pointer dereference
>>> at 0000000000000000 RIP:
>>> Jul 23 11:57:13 linux kernel:
>>> [_end+136405197/2130576028]
>>>
>>> :kvm:x86_emulate_memop+0x16c1/0x3cb0
>>>       
>> Oh, if you have CONFIG_SLUB enabled, then you need to use kvm-32.
>>     
>
> No, I don't.
> The same situation with kvm-33.
> Here is .tar.bz2 with my bzImage, System.map and .config: 
> http://depositfiles.com/en/files/1296145
> The following command causes hangup of my host system:
> $ kvm -hda [any image] -kernel bzImage-2.6.22.1-3 -boot c -m 256
>
> P.S.: with -no-kvm kernel boots fine
>
> P.P.S.: host and guest are 64-bit
>
>   

Can you post the guest image (if it is free and has no private data)?

-- 
Do not meddle in the internals of kernels, for they are subtle and quick to panic.


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/

  parent reply	other threads:[~2007-07-24  5:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-23  4:33 Oops at boot - kernel 2.6.22.1 Fix
     [not found] ` <web-2185108-sNPQ4meFfIFEiSddOK6LoQ@public.gmane.org>
2007-07-23  8:14   ` Avi Kivity
2007-07-23 11:40   ` Avi Kivity
     [not found]     ` <46A493A8.6020204-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-07-23 19:20       ` Fix
     [not found]         ` <200707240320.16070.pr0gress0r-ZoOhUfop2Wg@public.gmane.org>
2007-07-24  5:12           ` Avi Kivity [this message]
     [not found]             ` <46A58A57.5080900-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-07-24 20:17               ` Fix
     [not found]                 ` <200707250417.20572.pr0gress0r-ZoOhUfop2Wg@public.gmane.org>
2007-07-25  3:28                   ` Avi Kivity
     [not found]                     ` <46A6C36D.2010707-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-07-25  5:47                       ` Mark Janssen
     [not found]                         ` <531e3e4c0707242247s1cb8ea80j4c62701761736716-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-07-26 12:13                           ` 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=46A58A57.5080900@qumranet.com \
    --to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
    --cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=pr0gress0r-ZoOhUfop2Wg@public.gmane.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