From: Avi Kivity <avi@redhat.com>
To: Alexander Graf <agraf@suse.de>
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>,
Marcelo Tosatti <mtosatti@redhat.com>,
Joerg Roedel <joerg.roedel@amd.com>,
Sheng Yang <sheng@linux.intel.com>
Subject: Re: KVM guest crashes
Date: Wed, 21 Jan 2009 11:05:16 +0200 [thread overview]
Message-ID: <4976E54C.4080407@redhat.com> (raw)
In-Reply-To: <4976D954.9070901@suse.de>
Alexander Graf wrote:
> Avi Kivity wrote:
>
>> Alexander Graf wrote:
>>
>>> The guest kernels included here are openSUSE 11.0 (2.6.25) and 11.1
>>> (2.6.27) kernels.
>>>
>>> Find the tests here: http://alex.csgraf.de/kvm-tests.tar.bz2
>>> And some logs here (NPT enabled): http://alex.csgraf.de/kvm-logs.tar.bz2
>>>
>>> I'm somewhat lost on the reason for these failures, so if you do have
>>> some time on your hands, please give me a hand debugging this! If I'd
>>> had to guess, I'd say it's either an APIC issue and/or guest memory
>>> corruption.
>>>
>>>
>> I'd guess memory corruption.
>>
>> Does running a uniprocessor guest help? What about a uniprocessor
>> guest pinned to one host core?
>>
>
> So last night I started several guests with -smp 8 but without network
> to see if IO load is causing the problems. All VMs are down, but one
> panic log is rather new:
>
> Stuck ??
> Stuck ??
> Stuck ??
> Stuck ??
> Stuck ??
> Stuck ??
> BUG: unable to handle kernel NULL pointer dereference at 0000000000000000
> IP: [<ffffffff80237454>] cpu_attach_domain+0x84/0x207
>
This is right on startup, if I read things right.
I suggest checking if you have the latest BIOS update applied. I've had
bad experiences with un-updated processors.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-01-21 9:05 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-20 15:49 KVM guest crashes Alexander Graf
2009-01-20 20:07 ` Avi Kivity
2009-01-20 20:20 ` Alexander Graf
2009-01-21 8:14 ` Alexander Graf
2009-01-21 9:05 ` Avi Kivity [this message]
2009-01-21 9:36 ` Avi Kivity
2009-01-21 10:44 ` Alexander Graf
2009-01-22 20:29 ` Alexander Graf
2009-01-22 20:36 ` Alexander Graf
2009-01-22 20:55 ` Alexander Graf
2009-01-23 16:36 ` Alexander Graf
2009-01-23 22:36 ` Marcelo Tosatti
2009-01-24 7:42 ` Alexander Graf
2009-01-24 13:06 ` Marcelo Tosatti
2009-01-24 14:30 ` Alexander Graf
2009-01-26 15:53 ` Alexander Graf
2009-01-26 16:21 ` Marcelo Tosatti
2009-01-26 16:33 ` Alexander Graf
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=4976E54C.4080407@redhat.com \
--to=avi@redhat.com \
--cc=agraf@suse.de \
--cc=joerg.roedel@amd.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=sheng@linux.intel.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 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.