From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NJucm-0005yw-5A for qemu-devel@nongnu.org; Sun, 13 Dec 2009 15:01:00 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NJuch-0005uv-Fu for qemu-devel@nongnu.org; Sun, 13 Dec 2009 15:00:59 -0500 Received: from [199.232.76.173] (port=34767 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NJuch-0005up-CW for qemu-devel@nongnu.org; Sun, 13 Dec 2009 15:00:55 -0500 Received: from mx1.redhat.com ([209.132.183.28]:56668) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NJucg-0003ZO-PI for qemu-devel@nongnu.org; Sun, 13 Dec 2009 15:00:55 -0500 Date: Sun, 13 Dec 2009 21:58:09 +0200 From: "Michael S. Tsirkin" Message-ID: <20091213195809.GA25615@redhat.com> References: <20091213145132.GA11258@redhat.com> <20091213190839.GA25519@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Subject: [Qemu-devel] Re: link failure with s390 List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Alexander Graf Cc: qemu-devel@nongnu.org On Sun, Dec 13, 2009 at 08:21:57PM +0100, Alexander Graf wrote: > > On 13.12.2009, at 20:08, Michael S. Tsirkin wrote: > > > On Sun, Dec 13, 2009 at 06:30:56PM +0100, Alexander Graf wrote: > >> > >> On 13.12.2009, at 15:51, Michael S. Tsirkin wrote: > >> > >>> s390-virtio-bus.o: In function `virtio_s390_notify': > >>> /scm/qemu/hw/s390-virtio-bus.c:310: undefined reference to > >>> `kvm_s390_virtio_irq' > >>> > >> > >> Are you sure you're building with --enable-kvm? > > > > No, I did ./configure --taget-list=s390x-softmmu > > > >> Currently there's no emulation target for S390. > > > > So either configure should fail without --enable-kvm, > > or better enable kvm by default. > > Well, that's why you have to explicitly do --target-list=s390-softmmu. I'd love to see S390 bumped to a normal qemu arch with both TCG and KVM backends. But for now we don't have that. > > But yeah, we should probably add some sort of detection to configure, so it fails when you're building S390 on non-S390 and w/o KVM :-). > > > Alex By the way, where do you get kernel headers for s390 which are required to build with --enable-kvm? Which distro ships them? -- MST