From: "Michael S. Tsirkin" <mst@redhat.com>
To: Alexander Graf <agraf@suse.de>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: link failure with s390
Date: Sun, 13 Dec 2009 21:58:09 +0200 [thread overview]
Message-ID: <20091213195809.GA25615@redhat.com> (raw)
In-Reply-To: <C8DBF98B-A337-4ED2-A24A-464FBFA31BA9@suse.de>
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
next prev parent reply other threads:[~2009-12-13 20:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-13 14:51 [Qemu-devel] link failure with s390 Michael S. Tsirkin
2009-12-13 17:30 ` [Qemu-devel] " Alexander Graf
2009-12-13 19:08 ` Michael S. Tsirkin
2009-12-13 19:21 ` Alexander Graf
2009-12-13 19:58 ` Michael S. Tsirkin [this message]
2009-12-13 20:15 ` Alexander Graf
2009-12-13 20:19 ` Michael S. Tsirkin
2009-12-13 21:44 ` Alexander Graf
2009-12-13 22:13 ` Michael S. Tsirkin
2009-12-13 22:19 ` Alexander Graf
2009-12-13 22:27 ` Michael S. Tsirkin
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=20091213195809.GA25615@redhat.com \
--to=mst@redhat.com \
--cc=agraf@suse.de \
--cc=qemu-devel@nongnu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).