From: "David S. Ahern" <daahern@cisco.com>
To: Jan Kiszka <jan.kiszka@web.de>
Cc: kvm-devel <kvm@vger.kernel.org>
Subject: Re: segfault at start with latest qemu-kvm.git
Date: Wed, 03 Mar 2010 16:11:49 -0700 [thread overview]
Message-ID: <4B8EECB5.7030609@cisco.com> (raw)
In-Reply-To: <4B8EEC07.2040803@web.de>
On 03/03/2010 04:08 PM, Jan Kiszka wrote:
> David S. Ahern wrote:
>> With latest qemu-kvm.git I am getting a segfault at start:
>>
>> /tmp/qemu-kvm-test/bin/qemu-system-x86_64 -m 1024 -smp 2 \
>> -drive file=/images/f12-x86_64.img,if=virtio,cache=none,boot=on
>>
>> kvm_create_vcpu: Invalid argument
>> Segmentation fault (core dumped)
>>
>>
>> git bisect points to:
>>
>> Bisecting: 0 revisions left to test after this (roughly 0 steps)
>> [52b03dd70261934688cb00768c4b1e404716a337] qemu-kvm: Move
>> kvm_set_boot_cpu_id
>>
>>
>> $ git show
>> commit 7811d4e8ec057d25db68f900be1f09a142faca49
>> Author: Marcelo Tosatti <mtosatti@redhat.com>
>> Date: Mon Mar 1 21:36:31 2010 -0300
>>
>>
>> If I manually back out the patch it will boot fine.
>>
>
> Problem persists after removing the build directory and doing a fresh
> configure && make? I'm asking before taking the bug (which would be
> mine, likely) as I recently spent some hours "debugging" a volatile
> build system issue.
>
> Jan
>
Before sending the email I pulled a fresh clone in a completely
different directory (/tmp) to determine if it was something I
introduced. I then went back to my usual location, unapplied the patch
and it worked fine.
David
next prev parent reply other threads:[~2010-03-03 23:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-03 20:54 segfault at start with latest qemu-kvm.git David S. Ahern
2010-03-03 23:08 ` Jan Kiszka
2010-03-03 23:11 ` David S. Ahern [this message]
2010-03-03 23:20 ` Jan Kiszka
2010-03-03 23:23 ` David S. Ahern
2010-03-03 23:55 ` Jan Kiszka
2010-03-04 8:28 ` Jan Kiszka
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=4B8EECB5.7030609@cisco.com \
--to=daahern@cisco.com \
--cc=jan.kiszka@web.de \
--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.