Re: [kvm-ppc-devel] Current e500 kvm guest kernel booting log

[Hollis Blanchard <hollisb@us.ibm.com>]

Congratulations! :) Will you send patches? What are your thoughts on the
commonality between 440 and e500 code?

We haven't touched the "hack" code recently, since we've been
refactoring the upstream tree. That's pretty much done though, and right
now I'm just starting to integrate the old 440 support with the new
upstream code. That's not in a good state right now, but I could clean
it up and send it out if you're interested.

Also, I'm messing around with Makefiles now, and have been thinking
about how to connect the modules... For example, should there be a
kvm-powerpc-guest-440.ko that could link with kvm-powerpc-host-e500.ko?
For now, a single kvm-powerpc-e500.ko (e500 guests on e500 host) is
probably easiest, but we should think about the long-term goal too.

By the way, we booted with an initrd so we wouldn't need the network,
and hacked the device tree not to use interrupts for the UART. If you
take shortcuts like that you can really minimize your dependency on qemu
for now.

-- 
Hollis Blanchard
IBM Linux Technology Center

On Tue, 2007-12-11 at 13:01 +0800, Zhang Wei wrote:
> Hi,
> 
> Thanks Hollis' 'hack' codes!
> I've ported them to e500 core and booted something from e500 core kvm of
> PowerPC. Because of no qemu to emulate IO, the guest kernel halts before
> CPU's peripheral equipment (such as mpic) operations. The log is output
> from the serial port.
> 
> Log:
> Memory <- <0x0 0x8000000> (-1408896MB)
> CPU clock-frequency <- 0x4ead9a00 (1320MHz)
> CPU timebase-frequency <- 0x3ef1480 (66MHz)
> CPU bus-frequency <- 0x1f78a400 (528MHz)
> 
> zImage starting: loaded at 0x00400000 (sp: 0x00fffeb8)
> Allocating 0x2ca080 bytes for kernel ...
> gunzipping (0x00000000 <- 0x0040d000:0x006d0314)...done 0x2b0124 bytes
> 
> Linux/PowerPC load: root=/dev/nfs rw
> nfsroot\x192.168.1.10:/tftpboot/192.168.1.16
> ip\x192.168.1.16:192.168.1.10:192.168.1.1:255.255.255.0:unknown:eth0:off
> console=ttyS1,115200
> Finalizing device tree... flat tree at 0x40a8d0
> Using MPC85xx MDS machine description
> Memory CAM mapping: CAM0dMb, CAM1dMb, CAM2=0Mb residual: 0Mb
> Linux version 2.6.24-rc1-ga3c0a29d-dirty (zhangwei@bus) (gcc version
> 4.1.2) #336 Mon Dec 10 13:21:15 CST 2007
>  -> find_legacy_serial_port()
> stdout is /soc8568@e0000000/serial@4600
> legacy_serial_console = 1
> default console speed = 115200
>  <- find_legacy_serial_port()
> console [udbg0] enabled
> setup_arch: bootmem
> mpc85xx_mds_setup_arch()
> arch: exit
> Zone PFN ranges:
>   DMA             0 ->    32768
>   Normal      32768 ->    32768
> Movable zone start PFN for each node
> early_node_map[1] active PFN ranges
>     0:        0 ->    32768
> Built 1 zonelists in Zone order, mobility grouping on.  Total pages:
> 32512
> Kernel command line: root=/dev/nfs rw
> nfsroot\x192.168.1.10:/tftpboot/192.168.1.16
> ip\x192.168.1.16:192.168.1.10:192.168.1.1:255.255.255.0:unknown:eth0:off
> console=ttyS1,115200
> 
> The memory initialization is finished.
> 
> Cheers!
> Wei
> 
> -------------------------------------------------------------------------
> SF.Net email is sponsored by:
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://sourceforge.net/services/buy/index.php
> _______________________________________________
> kvm-ppc-devel mailing list
> kvm-ppc-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/kvm-ppc-devel


-------------------------------------------------------------------------
SF.Net email is sponsored by:
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
kvm-ppc-devel mailing list
kvm-ppc-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-ppc-devel