From mboxrd@z Thu Jan  1 00:00:00 1970
From: Corey Minyard <minyard@acm.org>
Date: Fri, 22 Jan 2010 17:23:40 +0000
Subject: Re: KVM on 440GP
Message-Id: <4B59DF1C.9070409@acm.org>
List-Id: <kvm-ppc.vger.kernel.org>
References: <4B59BFE4.5040107@acm.org>
In-Reply-To: <4B59BFE4.5040107@acm.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: kvm-ppc@vger.kernel.org

Hollis Blanchard wrote:
>
>
> Thanks! The patch looks good to me. It's unfortunate that 440GP is
> reported is "ppc440gp", while every other 440 variant is reported is
> "ppc440", but that's just how it goes I guess. It shouldn't be too
> difficult to get things working, since the cores are more or less the
> same. There has been a little accidental build breakage introduced in
> the 440 code recently (work to support the "Book S" KVM port), but
> it's all been simple stuff.
>   
There's more basic build problems with the kernel at the head of 
development, but that doesn't seem related to kvm.

> As for console, you probably want to use qemu's "-nographic" or at
> least "-serial stdio" options.
>   
Thanks for the info.  However, "-serial stdio" doesn't seem to work.  I get:


root@ebony:~# ./qemu-system-ppcemb --enable-kvm -nographic -m 128 -M 
bamboo -kernel uImage.bamboo -L . -append "" -m 64 -serial stdio
chardev: opening backend "stdio" failed
qemu: could not open serial device 'stdio': Success


I'm using the qemu at git://git.savannah.nongnu.org/qemu.git, not the 
one at git://git.kernel.org/pub/scm/virt/kvm/qemu-kvm.git, because the 
latter wouldn't build.  I suppose those are the build problems you speak 
of.  I'll see if I can get the latter working.

Thanks a bunch!

-corey