Kernel KVM-PPC virtualization development
 help / color / mirror / Atom feed
From: Corey Minyard <minyard@acm.org>
To: kvm-ppc@vger.kernel.org
Subject: Re: KVM on 440GP
Date: Fri, 22 Jan 2010 17:23:40 +0000	[thread overview]
Message-ID: <4B59DF1C.9070409@acm.org> (raw)
In-Reply-To: <4B59BFE4.5040107@acm.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

  parent reply	other threads:[~2010-01-22 17:23 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-22 15:10 KVM on 440GP Corey Minyard
2010-01-22 15:27 ` Corey Minyard
2010-01-22 16:52 ` Hollis Blanchard
2010-01-22 17:23 ` Corey Minyard [this message]
2010-01-22 17:27 ` Alexander Graf
2010-01-22 18:14 ` Hollis Blanchard
2010-01-22 18:29 ` Corey Minyard
2010-01-22 18:48 ` Alexander Graf
2010-01-22 19:13 ` Corey Minyard
2010-01-22 19:28 ` Hollis Blanchard
2010-01-22 20:04 ` Corey Minyard
2010-03-09  5:38 ` Hollis Blanchard
2010-03-09 13:46 ` Corey Minyard

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=4B59DF1C.9070409@acm.org \
    --to=minyard@acm.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox