Kernel KVM-PPC virtualization development
 help / color / mirror / Atom feed
From: Jerone Young <jyoung5@us.ibm.com>
To: Anthony Liguori <anthony-rdkfGonbjUSkNkDKm+mE6A@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
	kvm-ppc-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: [kvm-ppc-devel] [kvm-devel] [PATCH 0 of 7] PowerPC Embedded KVM
Date: Mon, 28 Jan 2008 16:01:47 +0000	[thread overview]
Message-ID: <1201536108.1666.1.camel@thinkpad> (raw)
In-Reply-To: <479D5032.6050807-rdkfGonbjUSkNkDKm+mE6A@public.gmane.org>

The issue here is that qemu does not support u-boot firmware. What we
are doing is actually loading a u-boot image and booting Linux directly
with a pre made device tree (which is something normally u-boot firmware
would provide Linux). So this code wouldn't fit into plain qemu just
yet.

On Sun, 2008-01-27 at 21:46 -0600, Anthony Liguori wrote:
> Jerone Young wrote:
> > This set of patches is to enable PowerPC embedded KVM capablities to be taken advantage of by qemu.
> >
> > The code currently boots a ungziped uImage of the Linux kernel complied for PowerPC 440 AMCC Bamboo evalution board.  We have not fully tested userspace, but fixes will follow as we do. We are also missing networking support, though this will come shortly. Also our current bamboo board model is h
> > ardcoded to have 144MB or RAM (which will get changed shortly also).
> >
> > What you need:
> >         - A PowerPC 440 based SOC (System-on-Chip)
> >              (we have been testing with a AMCC bamboo & AMCC sequoia boards)
> >         - PowerPC KVM Patches (these have been sent by Hollis Blanchard to the list)
> >         - KVM Kernel source with PowerPC KVM Patches applied
> >         - cross tools with powerpc 440 compiler (this is assuming your not using a power machine)
> >         - version of zlib-1.2.3 or higher compiled for powerpc
> >
> > Then you compile with userspace. Here is an example of what I use to configure kvm-userspace:
> >
> > ./configure --arch=powerpc --cross-prefix=powerpc-440-linux-gnu- --with-patched-kernel --kerneldir=/home/jerone/work/kvmppc.hg/ --disable-sdl --disable-vnc-tls --disable-gfx-check --disable-gcc-check --qemu-cflags="-I/home/jerone/work/zlib-1.2.3 -I/home/jerone/work/kvmppc.hg/include/" --qemu-ldflags="-L/home/jerone/work/zlib-1.2.3/" 
> >
> > Then you run "make". After which you will have an excutable:
> > kvm-userspace/qemu/ppcemb-softmmu/qemu-system-ppcemb
> >
> > To run, boot your compiled KVM PPC enabled kernel and also compile your special none gzipped cuImag
> > e of Linux for the Bamboo board. Then run:
> >
> > ./qemu-system-ppcemb -nographic -M bamboo -kernel cuImage.bambo
> >   
> 
> Since you're just adding a new machine type to the existing ppcemb, it 
> may be worth while to split out the KVM logic and submit the machine 
> type directly to qemu-devel.
> 
> Does the code work with -no-kvm?
> 
> Regards,
> 
> Anthony Liguori
> 
> > Signed-off-by: Jerone Young <jyoung5@us.ibm.com>
> >
> > -------------------------------------------------------------------------
> > 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/
> > _______________________________________________
> > kvm-devel mailing list
> > kvm-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/kvm-devel
> >   
> 


-------------------------------------------------------------------------
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/
_______________________________________________
kvm-ppc-devel mailing list
kvm-ppc-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-ppc-devel

  parent reply	other threads:[~2008-01-28 16:01 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-28  3:16 [kvm-ppc-devel] [PATCH 0 of 7] PowerPC Embedded KVM qemu enablement Jerone Young
2008-01-28  3:16 ` [kvm-ppc-devel] [PATCH 1 of 7] Enhnace kvm-userspace configure Jerone Young
2008-01-28  3:16 ` [kvm-ppc-devel] [PATCH 2 of 7] Ensure 4kB page alignment for Jerone Young
2008-01-28  3:16 ` [kvm-ppc-devel] [PATCH 3 of 7] Chnage so that Powerpc & IA64 do not Jerone Young
2008-01-28  3:16 ` [kvm-ppc-devel] [PATCH 4 of 7] Add vcpu to arguments of powerpc Jerone Young
2008-01-28  3:16 ` [kvm-ppc-devel] [PATCH 5 of 7] Add qemu powerpc build support Jerone Young
2008-01-28  3:16 ` [kvm-ppc-devel] [PATCH 6 of 7] Add powerpc KVM support to qemu Jerone Young
2008-01-28  3:16 ` [kvm-ppc-devel] [PATCH 7 of 7] Add Powerpc 440 board model "bamboo" Jerone Young
2008-01-28  3:46 ` [kvm-ppc-devel] [kvm-devel] [PATCH 0 of 7] PowerPC Embedded KVM Anthony Liguori
     [not found]   ` <479D5032.6050807-rdkfGonbjUSkNkDKm+mE6A@public.gmane.org>
2008-01-28 16:01     ` Jerone Young [this message]
2008-01-28 16:17       ` Anthony Liguori
     [not found]         ` <479E0029.3090906-rdkfGonbjUSkNkDKm+mE6A@public.gmane.org>
2008-01-28 16:20           ` Jerone Young
2008-01-28 16:48           ` Hollis Blanchard
2008-01-28 11:03 ` Avi Kivity

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=1201536108.1666.1.camel@thinkpad \
    --to=jyoung5@us.ibm.com \
    --cc=anthony-rdkfGonbjUSkNkDKm+mE6A@public.gmane.org \
    --cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=kvm-ppc-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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