From: Avi Kivity <avi@redhat.com>
To: Gene Horodecki <geneh@shaw.ca>
Cc: KVM list <kvm@vger.kernel.org>
Subject: Re: segfault with windows XP guest
Date: Mon, 10 Aug 2009 15:27:27 +0300 [thread overview]
Message-ID: <4A80122F.8070602@redhat.com> (raw)
In-Reply-To: <4A800EEE.1070209@shaw.ca>
On 08/10/2009 03:13 PM, Gene Horodecki wrote:
> Avi Kivity wrote:
>> On 08/08/2009 03:56 AM, Gene Horodecki wrote:
>>> Hi there, I currently have about five guests set up with KVM, one of
>>> them being windows XP. I am having trouble with the windows XP
>>> one. It will works for a bit and then the process dies with the
>>> following in the kern.log:
>>>
>>> kvm[5593]: segfault at 29c ip 00000000004316d8 sp 00007fff0766bed0
>>> error 4 in kvm[400000+1e0000]
>>>
>>> Once the process dies once, then it keeps happening. The virtual
>>> machine will hardly boot now and it just crashes with this error.
>>>
>>> No major load on the windows VM, acpi enabled, a single 20Gb raw disk.
>>>
>>> Really hoping to get this working, thanks!
>>>
>>
>> Please generate a core dump and a stack trace. You may need to
>> ./configure --disable-strip so that debug symbols are retained.
>>
> Can someone please link me to instructions on how to do this? Thanks.
>
On the command line, do
$ ulimit -c unlimited
then run your guest (from the command line). When it segfaults it will
say "core dumped". Look for a file named core (or core.$PID), and run
$ gdb /path/to/qemu-system-x86_64 /path/to/core/file
(gdb) bt full
and post the results.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2009-08-10 12:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-08 0:56 segfault with windows XP guest Gene Horodecki
2009-08-09 9:50 ` Avi Kivity
[not found] ` <4A800EEE.1070209@shaw.ca>
2009-08-10 12:27 ` Avi Kivity [this message]
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=4A80122F.8070602@redhat.com \
--to=avi@redhat.com \
--cc=geneh@shaw.ca \
--cc=kvm@vger.kernel.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.