Jerone Young wrote:
> 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.
>   

In theory, it would still work with QEMU though right?  It just requires 
a custom guest kernel.

Regards,

Anthony Liguori

> 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 <[EMAIL PROTECTED]>
>>>
>>> -------------------------------------------------------------------------
>>> 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-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel

Reply via email to