From: Joerg Roedel <joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
To: Walter Lundby <lundby-yWtbtysYrB+LZ21kGMrzwg@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: attached is kvm crash log with a kernel BUG at /usr/src/modules/kvm/mmu.c:307!
Date: Sat, 26 Jan 2008 09:07:15 +0100 [thread overview]
Message-ID: <20080126080715.GC21476@8bytes.org> (raw)
In-Reply-To: <479A9778.2030203-yWtbtysYrB+LZ21kGMrzwg@public.gmane.org>
On Fri, Jan 25, 2008 at 08:14:16PM -0600, Walter Lundby wrote:
> KVM version:/sbin/modinfo kvm
> filename: /lib/modules/2.6.24-rc5/misc/kvm.ko
> license: GPL
> author: Qumranet
> version: kvm-48
> srcversion: 63B0F92A3F1152C05FE5A8F
> depends:
> vermagic: 2.6.24-rc5 SMP mod_unload
>
> /sbin/modinfo kvm_amd
> filename: /lib/modules/2.6.24-rc5/misc/kvm-amd.ko
> license: GPL
> author: Qumranet
> version: kvm-48
> srcversion: 22F744921D178E88E9B84A7
> depends: kvm
> vermagic: 2.6.24-rc5 SMP mod_unload
>
> host arch: x86_64
> guest that crashed: win2k srv pack 4
> start cmd line: kvm -hda /home/watermod/KVM/win2k_srvpk4_.img -m 512
> -no-acpi
>
> no-kvm - works fine.
KVM-48 is really old. A lot of bugs were fixed since this time. Can you
try kvm-60 and tell us if the bug is still there? In our tests kvm-60
worked fairly well on AMD.
Joerg
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
next prev parent reply other threads:[~2008-01-26 8:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-26 2:14 attached is kvm crash log with a kernel BUG at /usr/src/modules/kvm/mmu.c:307! Walter Lundby
[not found] ` <479A9778.2030203-yWtbtysYrB+LZ21kGMrzwg@public.gmane.org>
2008-01-26 8:07 ` Joerg Roedel [this message]
2008-01-26 18:26 ` 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=20080126080715.GC21476@8bytes.org \
--to=joro-zlv9swrftaidnm+yrofe0a@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=lundby-yWtbtysYrB+LZ21kGMrzwg@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