public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Christian Borntraeger <borntraeger@de.ibm.com>
To: Robin Atwood <robin@binro.org>
Cc: kvm@vger.kernel.org
Subject: Re: KVM compile fails on s390x
Date: Fri, 1 Aug 2008 14:09:02 +0200	[thread overview]
Message-ID: <200808011409.02379.borntraeger@de.ibm.com> (raw)
In-Reply-To: <200807312107.39200.robin@binro.org>

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.
You might need "tunctl" and "screen" for better results. If you want to stay 
at 2.6.26 there are some kernel patches in the kuli package. They add virtio 
console support as well as a fix for the z900. 2.6.27-rc1 should work out of 
the box.

Christian

  reply	other threads:[~2008-08-01 12:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-31 14:07 KVM compile fails on s390x Robin Atwood
2008-08-01 12:09 ` Christian Borntraeger [this message]
2008-08-01 12:20   ` Daniel P. Berrange
2008-08-01 12:32     ` Christian Borntraeger
2008-08-01 13:19       ` Robin Atwood
2008-08-02 12:00   ` Robin Atwood
2008-08-04 11:02     ` Christian Borntraeger

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=200808011409.02379.borntraeger@de.ibm.com \
    --to=borntraeger@de.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=robin@binro.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