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: Mon, 4 Aug 2008 13:02:38 +0200	[thread overview]
Message-ID: <200808041302.38847.borntraeger@de.ibm.com> (raw)
In-Reply-To: <200808021900.23830.robin@binro.org>

Am Samstag, 2. August 2008 schrieb Robin Atwood:
> On Friday 01 Aug 2008, 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.
> 
> The correct headers are now found but later into the compile I get:
> 
> In file included 
> from /var/tmp/portage/app-emulation/kvm-72/work/kvm-72/qemu/exec.c:41:
> /var/tmp/portage/app-emulation/kvm-72/work/kvm-72/qemu/tcg/tcg.h:24:24: 
error: 
> tcg-target.h: No such file or directory
> /var/tmp/portage/app-emulation/kvm-72/work/kvm-72/qemu/tcg/tcg.h:37:2: 
error: 
> #error unsupported
> <snip>
> make[2]: *** [exec.o] Error 1
> make[2]: Leaving directory 
> `/var/tmp/portage/app-emulation/kvm-72/work/kvm-72/qemu/i386-softmmu'
> make[1]: *** [subdir-i386-softmmu] Error 2
> make[1]: Leaving directory 
> `/var/tmp/portage/app-emulation/kvm-72/work/kvm-72/qemu'
> make: *** [qemu] Error 2
> 
> There is no tcg-target.h for the s390 arch but why is i386-softmmu being 
> compiled?

Yes. Expect further breakage in kvm-userspace on s390. At the moment libkvm is 
the only part of kvm-userspace that is finished. Anything else is not yet 
done.

At the moment you have to use kuli to start a guest.

If you start kuli with:
# kuli -k <yourguestkernel> -a "noinitrd"
you will get a booting kernel until the no device found panic message

you can use a file, disk or partition as a root device. If you have a copy of 
your distribution on lets say /dev/dasdb1 you can boot with:

# kuli -k /boot/image-<xxx> -a "initrd root=/dev/vda" \
-d file=/dev/dasdb1 -i /boot/initrd-<xxx>

Make sure to adopt the guest fstab to /dev/vda and so on.

Christian

      reply	other threads:[~2008-08-04 11:02 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
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 [this message]

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=200808041302.38847.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