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
