All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Clayton <chris2553-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>
To: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Fwd: Re:  kvm-31 seg fault
Date: Tue, 24 Jul 2007 22:02:05 +0000	[thread overview]
Message-ID: <200707242202.05192.chris2553@googlemail.com> (raw)

Forgot to cc this to the list, sorry
----------  Forwarded Message  ----------

Subject: Re: [kvm-devel] kvm-31 seg fault
Date: Tuesday 24 July 2007
From: Chris Clayton <chris2553-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>
To: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>

Hi again Avi,

On Sunday 22 July 2007, you wrote:
> Chris Clayton wrote:
> > On Sunday 22 July 2007, you wrote:
> >> Chris Clayton wrote:
> >>> Hi,
> >>>
> >>> I'm getting a seg fault running kvm-31 on linux-2.6.22.1-cfs-v19 and
> >>> linux-2.6.22-git17.
> >>>
> >>> If I use the kvm-31 kernel modules with qemu from kvm-29, all is OK
> >>> Also, running "non-kvm" guests, such as Windows ME, works fine with
> >>> kvm-31.
> >>>
> >>> I have an strace log but its over 99 Kilobytes, so I haven't attached
> >>> it to this mail. More than happy to compress it and send it by private
> >>> mail, if required.
> >>>
> >>> I'm not subscribed, so please cc me.
> >>
> >> Please send it to me.  What guest are you running?  Is the host 32-bit
> >> or 64-bit?
> >
> > Attached is the log from 2.6.22-git17
> >
> > The host is 32bit and the guest is freebsd-6.2 although I get the same
> > seg fault with slackware 10.2 and damn small linux 3.1 (all 32 bit).
>
> Unfortunately that doesn't help.  Can you generate a core ('ulimit -c
> unlimited' may help) and get a stacktrace from gdb?

I've been doing some more digging around here and thought I'd report my 
findings. I've found that under kvm 31 and 33, qemu-system-x86_64 always 
fails with a seg fault when the (__thread) variable vcpu_env (declared at 
line 33 of qemu-kvm.c) is accessed in kvm_update_interrupt_request(). I've 
inserted useless statements (printf()s and assignments) at the head of the 
function, and always get the seg fault at the first access to the variable.

I'm building qemu with gcc-3.4.6, but to eliminate a fault in that compiler, 
I've also built the application on my laptop with gcc-3.3.6 and copied the 
binary over to my desktop machine. I still get the seg fault.

Sorry if this is just noise on your line, but I thought I'd send it just in 
case it's useful.

Chris

-------------------------------------------------------

-------------------------------------------------------------------------
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/

             reply	other threads:[~2007-07-24 22:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-24 22:02 Chris Clayton [this message]
     [not found] ` <200707242202.05192.chris2553-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>
2007-07-25  3:22   ` Fwd: Re: kvm-31 seg fault Avi Kivity
     [not found]     ` <46A6C1EB.4040104-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-07-28  5:28       ` Chris Clayton
  -- strict thread matches above, loose matches on Subject: below --
2007-07-24 22:30 Gregory Haskins

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=200707242202.05192.chris2553@googlemail.com \
    --to=chris2553-gm/ye1e23mwn+bqq9rbeug@public.gmane.org \
    --cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@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 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.