From: Stephane Eranian <eranian-sDzT885Ts8HQT0dZR+AlfA@public.gmane.org>
To: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
Magicboiz <magicboiz-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Subject: Re: kvm-intel kernel panicing 2.6.22 on T7200
Date: Wed, 20 Jun 2007 15:02:14 -0700 [thread overview]
Message-ID: <20070620220214.GF26200@frankl.hpl.hp.com> (raw)
In-Reply-To: <46726EA2.4040904-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
Avi,
On Fri, Jun 15, 2007 at 01:49:06PM +0300, Avi Kivity wrote:
> Magicboiz wrote:
> > a little bit better. It Opps'ed again, but this time, my laptop is still
> > usable:
> >
> > sudo /usr/local/kvm/bin/qemu -hda /tmp/disco-qemu -m 128 -boot d
> > -cdrom /tmp/debian-40r0-i386-businesscard.iso -vnc :3
> >
> >
> >
> > Jun 15 12:39:35 linux kernel: [16051.152000] BUG: unable to handle
> > kernel paging request at virtual address 0100000f
> > Jun 15 12:39:35 linux kernel: [16051.152000] EIP is at kvm_vcpu_ioctl
> > +0x90b/0xe10 [kvm]
> >
>
> Please post your kvm.ko for analysis.
>
Did this issue ever get resolved?
I am running into it on my Core 2 Duo laptop (x86-64 host, i386 guest).
I am trying with kvm-28 + your use-zero-consistently-for-missing-shadow-pdpts.patch
on a 2.6.22-rc4 host.
thanks.
--
-Stephane
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
next prev parent reply other threads:[~2007-06-20 22:02 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-14 14:10 kvm-intel kernel panicing 2.6.22 on T7200 Magicboiz
2007-06-14 14:25 ` Gregory Haskins
[not found] ` <1181831139.13335.14.camel-5CR4LY5GPkvLDviKLk5550HKjMygAv58XqFh9Ls21Oc@public.gmane.org>
2007-06-14 15:06 ` Magicboiz
2007-06-14 15:17 ` Gregory Haskins
[not found] ` <1181834264.13335.18.camel-5CR4LY5GPkvLDviKLk5550HKjMygAv58XqFh9Ls21Oc@public.gmane.org>
2007-06-14 15:46 ` Magicboiz
2007-06-15 10:02 ` Avi Kivity
[not found] ` <467263CA.1070507-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-06-15 10:42 ` Magicboiz
2007-06-15 10:49 ` Avi Kivity
[not found] ` <46726EA2.4040904-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-06-15 10:57 ` Magicboiz
2007-06-20 22:02 ` Stephane Eranian [this message]
[not found] ` <20070620220214.GF26200-HU54gidqsKnWxDs0y9d3MAC/G2K4zDHf@public.gmane.org>
2007-06-21 9:10 ` Avi Kivity
2007-06-16 7:51 ` Avi Kivity
[not found] ` <46739666.1000102-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-06-16 9:52 ` Magicboiz
2007-07-10 6:26 ` Jindrich Makovicka
2007-07-10 11:10 ` Avi Kivity
2007-07-14 17:48 ` Jindrich Makovicka
2007-06-14 15:43 ` Luca
2007-08-01 19:03 ` Magic Boiz
-- strict thread matches above, loose matches on Subject: below --
2007-06-13 10:06 Alan Pope
[not found] ` <20070613100624.GA26122-ARoKIbVt0xkAvxtiuMwx3w@public.gmane.org>
2007-06-13 11:01 ` 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=20070620220214.GF26200@frankl.hpl.hp.com \
--to=eranian-sdzt885ts8hqt0dzr+alfa@public.gmane.org \
--cc=avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=magicboiz-Re5JQEeQqe8AvxtiuMwx3w@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