From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jan Kiszka Subject: Re: segfault at start with latest qemu-kvm.git Date: Thu, 04 Mar 2010 00:20:08 +0100 Message-ID: <4B8EEEA8.8070902@web.de> References: <4B8ECC79.8040205@cisco.com> <4B8EEC07.2040803@web.de> <4B8EECB5.7030609@cisco.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig55FE1E56E704CE34F2877BEE" Cc: kvm-devel To: "David S. Ahern" Return-path: Received: from fmmailgate02.web.de ([217.72.192.227]:43535 "EHLO fmmailgate02.web.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751787Ab0CCXUT (ORCPT ); Wed, 3 Mar 2010 18:20:19 -0500 In-Reply-To: <4B8EECB5.7030609@cisco.com> Sender: kvm-owner@vger.kernel.org List-ID: This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig55FE1E56E704CE34F2877BEE Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable David S. Ahern wrote: >=20 >=20 >=20 > 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=3D/images/f12-x86_64.img,if=3Dvirtio,cache=3Dnone,boot=3D= 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 >>> 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 >> >=20 > 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. OK, that reason can be excluded. What's your host kernel kvm version? (Of course, the issue does not show up here. But virtio currently does not boot for me - independent of my patch.) Jan --------------enig55FE1E56E704CE34F2877BEE Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iEYEARECAAYFAkuO7qgACgkQitSsb3rl5xT2JQCfXTX/NvtPI5u27r79sfjbis46 5mkAoKYD2s1ne7CO/rpkh8LN1Iefig2H =nn/V -----END PGP SIGNATURE----- --------------enig55FE1E56E704CE34F2877BEE--