From: Giuseppe Falsetti <giuseppe@czero.it>
To: kvm-ppc@vger.kernel.org
Subject: Re: Compiling error : ppc440_bamboo.o fails
Date: Mon, 01 Dec 2008 18:30:21 +0000 [thread overview]
Message-ID: <49342D3D.9050808@czero.it> (raw)
In-Reply-To: <49341A65.2080601@czero.it>
Hi Hollis,
no I don't have a 440, I have only many 970 :-|
So I can't hope that KVM will support 970 cpus? Qemu already support
this, why for KVM is so difficoult?
Noone is interested? Or the problem is the HW to develop/test on?
I can participate only as tester, I'm not a developer, but I can provide
the HW for the cause.
Thanks.
Giuseppe.
Hollis Blanchard ha scritto:
> Hi Giuseppe, thanks for your mail. Feel free to CC
> kvm-ppc@vger.kernel.org in the future, too... :)
>
> On Mon, 2008-12-01 at 15:08 +0100, Giuseppe Falsetti wrote:
>
> Sorry about that... I'm currently in the process of merging PowerPC KVM
> support into upstream qemu, and due to this the kvm qemu fork has
> broken.
>
> These are annoying, but just warnings so we can ignore them for now.
>
> I can provide you a patch to get you going again right now, but just to
> clarify: do you have a 440 system you're going to be running KVM on, and
> the G5 is just your build how? There currently is no KVM support for
> 970...
>
next prev parent reply other threads:[~2008-12-01 18:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-01 17:09 Compiling error : ppc440_bamboo.o fails Giuseppe Falsetti
2008-12-01 18:30 ` Giuseppe Falsetti [this message]
2008-12-01 19:08 ` Hollis Blanchard
2008-12-03 18:34 ` Giuseppe Falsetti
2008-12-03 19:12 ` Hollis Blanchard
-- strict thread matches above, loose matches on Subject: below --
2008-12-01 14:08 Giuseppe Falsetti
[not found] ` <4933EFDD.8000709-qgsxNw1iPWg@public.gmane.org>
2008-12-01 17:34 ` Hollis Blanchard
2008-12-01 17:34 ` Hollis Blanchard
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=49342D3D.9050808@czero.it \
--to=giuseppe@czero.it \
--cc=kvm-ppc@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.