On Fri, Aug 01, 2008 at 02:09:02PM +0200, Christian Borntraeger wrote: > Am Donnerstag, 31. Juli 2008 schrieb Robin Atwood: > > I guess I am doing something very dumb, but when I try to compile kvm-72 on > > z900 architecture (actually Hercules) I immediately get a compile error: > > > > zgentoo kvm-72 # ./configure --disable-gfx-check --disable-sdl > > Your userspace headers dont have all the necessary pieces... > You want to add --with-patched-kernel, that should trigger an headers_sync to > get the header files from the kernel. > > Anyway, that wont give you anything useful by now, as we only have kvmlib > done > in the userspace. Until we ported the rest of our userspace part over to > kvm-userspace, you can use our prototype code found on > > http://www-128.ibm.com/developerworks/linux/linux390/kuli.html > > It supports a subset of the qemu syntax, e.g. somethin like > kuli -drive file=disks/root -megs 128 -n tap,ifname=tap0 -smp=2 > works.
What are your intentions for this part longer term. Are you planning to create a QEMU target for s390 so we can use real QEMU binaries instead of emulating a subset of its features. If s390 userspace were QEMU based them you'd be able to use libvirt as a management API in same way as the other architectures. Experiance with the 'xenner' work has shown that trying to write a tool that behaves like qemu is a non-trivial, never ending task. As soon as libvirt makes use of some new feature of QEMU's CLI or monitor console, we find Xenner doesn't cope and have to duplicate yet more code. Hence xenner is slowly switching over to use QEMU fully, rather than emulating its CLI syntax Regards, Daniel -- |: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :| -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
