From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NJwjJ-0002EP-Qm for qemu-devel@nongnu.org; Sun, 13 Dec 2009 17:15:53 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NJwjF-0002A8-AK for qemu-devel@nongnu.org; Sun, 13 Dec 2009 17:15:53 -0500 Received: from [199.232.76.173] (port=45497 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NJwjF-00029v-2T for qemu-devel@nongnu.org; Sun, 13 Dec 2009 17:15:49 -0500 Received: from mx1.redhat.com ([209.132.183.28]:48548) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NJwjE-0004sf-HW for qemu-devel@nongnu.org; Sun, 13 Dec 2009 17:15:48 -0500 Date: Mon, 14 Dec 2009 00:13:02 +0200 From: "Michael S. Tsirkin" Message-ID: <20091213221302.GA26577@redhat.com> References: <20091213145132.GA11258@redhat.com> <20091213190839.GA25519@redhat.com> <20091213195809.GA25615@redhat.com> <20091213201900.GA25658@redhat.com> <8E2A839B-F3EA-46E0-9E11-52117F47C5EA@suse.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <8E2A839B-F3EA-46E0-9E11-52117F47C5EA@suse.de> 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 10:44:04PM +0100, Alexander Graf wrote: > > On 13.12.2009, at 21:19, Michael S. Tsirkin wrote: > > > On Sun, Dec 13, 2009 at 09:15:30PM +0100, Alexander Graf wrote: > >> > >> Am 13.12.2009 um 20:58 schrieb "Michael S. Tsirkin" : > >> > >>> 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? > >> > >> Uh, that's just the normal kernel headers, right? > >> SLE11 definitely does ship them. > > > > kvm has architecture specific defines, does it not? > > In files called the same on x86, just with a different asm link. Exactly. ls -l /usr/src/kernels/2.6.30.8-64.fc11.i586/include/asm lrwxrwxrwx 1 root root 7 2009-10-04 17:53 /usr/src/kernels/2.6.30.8-64.fc11.i586/include/asm -> asm-x86 so it won't find link for s390x. > > > >> Worst case you just install the kernel > >> sources. > >> > >> Alex > >>> > > > > kernel sources is the wrong things to use for qemu. qemu should use > > exported sanitized sources. > > Same thing as on all other archs. What's your point here? > > Alex Hmm. I'm just trying to understand how does build find kvm headers for s390 since they are not linked to from asm. Possibly what happens is we just pick a wrong arch and it kind of works most of the time? anyway, with --enable-kvm I still get: s390-virtio-bus.o: In function `virtio_s390_notify': /scm/qemu/hw/s390-virtio-bus.c:310: undefined reference to `kvm_s390_virtio_irq' collect2: ld returned 1 exit status ??? -- MST