From: Hollis Blanchard <hollisb@us.ibm.com>
To: Avi Kivity <avi@qumranet.com>
Cc: kvm-ppc-devel <kvm-ppc-devel@lists.sourceforge.net>,
kvm-devel <kvm-devel@lists.sourceforge.net>
Subject: Re: [kvm-ppc-devel] upstream PowerPC qemu breakage
Date: Mon, 18 Feb 2008 15:03:27 -0600 [thread overview]
Message-ID: <1203368607.3428.66.camel@basalt> (raw)
In-Reply-To: <47B9E914.1030603@qumranet.com>
On Mon, 2008-02-18 at 22:22 +0200, Avi Kivity wrote:
> Hollis Blanchard wrote:
> >> Unfortunately I wasn't able to get an F8 ppc rescue cd ISO to boot with
> >> qemu 0.9.0. Can you point me to a working combination?
> >>
> >
> > It's difficult to get anything booting with upstream PowerPC qemu,
> > mostly because of the unmaintained firmware they use (called Open
> > Hackware).
> >
> > That said, upstream qemu does not support 440 cores, which is what our
> > KVM work is targeting. Also, Fedora 8 doesn't either, though it may be
> > possible to get F8 working by providing your own kernel and some small
> > configuration tweaks (inittab, securetty).
> >
> > There are other distributions that will work with little to no tweaking
> > for 440, but until we can get IO (other than console) working we have
> > been using very simple root filesystems.
> >
> > However, none of these will be useful to you in KVM unless you have a
> > 440 host to run them on.
> >
> > Originally you said you just need a kernel tree to build against. Can
> > you elaborate on what you're trying to do now?
> >
>
> I'd like to have a full setup so I can do run testing as well.
I'd love to help make this happen.
> I was thinking of running a ppc distro on qemu, and building and running
> kvm-ppc on that to test.
This isn't going to work in the near future, because KVM today requires
a 440 host, and qemu today doesn't emulate 440 instructions.
> Even if I don't run it, it's a much better
> build-time environment. Of course running the unit tests and an image
> or two will be even better.
>
> So, at best, I'd like an emulation environment that allows me to build
> and run; at worst, build only.
Building would be better done with a cross-compiler than inside qemu.
--
Hollis Blanchard
IBM Linux Technology Center
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
prev parent reply other threads:[~2008-02-18 21:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-11 21:55 upstream PowerPC qemu breakage Hollis Blanchard
2008-02-11 22:55 ` Anthony Liguori
2008-02-13 7:03 ` Avi Kivity
2008-02-12 10:45 ` Avi Kivity
2008-02-12 18:56 ` Hollis Blanchard
2008-02-13 6:58 ` Avi Kivity
2008-02-16 0:26 ` [kvm-ppc-devel] " Hollis Blanchard
2008-02-16 8:47 ` Avi Kivity
2008-02-18 19:38 ` Hollis Blanchard
2008-02-18 20:22 ` Avi Kivity
2008-02-18 21:03 ` Hollis Blanchard [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=1203368607.3428.66.camel@basalt \
--to=hollisb@us.ibm.com \
--cc=avi@qumranet.com \
--cc=kvm-devel@lists.sourceforge.net \
--cc=kvm-ppc-devel@lists.sourceforge.net \
/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