Hi all,

I updated the CoreOS@ppc64le status in here and anyone can help to
verify/build packages for ppc64le ?

This modified CoreOS SDK which is working on x86 will not make any impact
on existing amd64/arm64 platform.
So If we have verified, build, solved the packages for ppc64le, I think we
can emerge this developing ppc64le branch.
We will not merge previously CoreOS SDK working on ppc64le since it's
broken amd64/arm64 platform.



*1. We've made CoreOS SDK on x86  to support cross building packages for
ppc64le platform,*
*    please download this modified CoreOS SDK as below steps if you want to
join/verify our work.*

    a) download coreos sdk
    #repo init -u https://github.com/houstar/manifest.git -b ppc64le
    #repo sync

    b) chroot coreos sdk
    #./chromite/sdk/cros_sdk

    Once chrooted in CoreOS SDK environment,

    c) set password for board
    #./set_shared_user_password.sh

    d) setup ppc64le-usr board
    #./setup_board --board=ppc64le-usr

    e) cross building packages for ppc64le-usr board
    #./build_packages --board=ppc64le-usr


*2. But We've faced cross building issues in following packages. I want to
someone point out *

*    Which packages is MUST needed and which is optional that we can skip
it for CoreOS.*

dev-libs/pth-2.0.7-r3
dev-lang/perl-5.20.2
sys-apps/texinfo-5.1
app-crypt/gnupg-2.0.28
sys-apps/kexec-tools-2.0.4-r1
dev-util/boost-build-1.55.0
dev-libs/boost-1.55.0-r2
sys-block/thin-provisioning-tools-0.4.1
app-emulation/rkt-9999
net-dns/bind-tools-9.10.2_p4
dev-libs/gobject-introspection-1.38.0
dev-db/etcd-9999
sys-fs/xfsprogs-3.2.2-r1
dev-libs/dbus-glib-0.102
sys-kernel/coreos-kernel-4.8.4
coreos-base/update_engine-9999
app-emulation/docker-9999
dev-lang/go-1.7.1
dev-lang/go-1.6.3-r1


      Current we known that some packages has no cross build support for
ppc64le as same as arm64. e.g.
          So we can skip it.
          dev-lang/perl-5.20.2
          app-crypt/gnupg-2.0.28
          sys-apps/kexec-tools-2.0.4-r1
          dev-util/boost-build-1.55.0
          net-dns/bind-tools-9.10.2_p4
          Or ???


*3. If we have build all packages that needed for CoreOS. Could we*

*      Using grub running on x86 to install ieee1275 to our ppc64le qcow2
images ?*





*      #grub-install --no-bootsect --no-nvram --target=powerpc-ieee1274
./qemu-boot-partition *

*Thanks! *

*Leno Hou*
E-mail :  leno...@gmail.com


On Thu, Sep 8, 2016 at 12:36 AM, Leno Hou <leno...@gmail.com> wrote:

> Hi all,
>
> Today I've successfully built  CoreOS@ppc64le and booted this CoreOS from
> KVM.
>
>
> Hi @Brandon Philips @Michael Marineau el at,
>
> Could you help me to review the patches/PRs sent by Leno Hou ?
>
> PRs
> [1] https://github.com/coreos/scripts/pull/584
> [2] https://github.com/coreos/chromite/pull/22
> [3] https://github.com/coreos/coreos-overlay/pull/2174
>
>
> *Leno Hou*
> E-mail :  leno...@gmail.com
>
>
>
>
>>>
>>>
>>> ----- Original message -----
>>> From: Michael Marineau <michael.marin...@coreos.com>
>>> To: coreos-dev <coreos-dev@googlegroups.com>
>>> Cc: Brandon Philips <brandon.phil...@coreos.com>, Qing Yuan QQ
>>> Hou/China/IBM@IBMCN, Qu KK Jiang/China/IBM@IBMCN, Liang NS
>>> Zhuang/China/IBM@IBMCN
>>> Subject: Re: ppc64le port of CoreOS
>>> Date: Tue, Jul 19, 2016 2:50 AM
>>>
>>> The file src/scripts/build_library/disk_layout.json will need new
>>> entries. For dev images copy the the "devel" layout, adding an entry to
>>> override partition 2 (BIOS BOOT), changing its type to the PReP GUID (the
>>> partitioning tool, cgpt, doesn't have a built in name for that type right
>>> now but the raw guid should work, I hope). You may need to adjust the size
>>> too. For prod images add an entry that only contains your new partition 2.
>>> Anything not defined is inherited from the "base" layout. Then
>>> pass --disk_layout= to build_image and image_to_vm. Actually setting up the
>>> bootloader should go in src/scripts/build_library/grub_install.sh
>>>
>>> I don't know anything about booting PPC but I'd recommend keeping the
>>> PReP partition as simple/small as possible with most things in the larger
>>> ESP partition for consistency with other platforms.
>>>
>>> On Mon, Jul 18, 2016 at 4:36 AM, Leno Hou <leno...@gmail.com> wrote:
>>>
>>> Hi all,
>>>
>>> This is the updated CoreOS@ppc64le status for you and I need your help
>>> about bootloader partition.
>>>
>>> 1. Gentoo hosted ppc64le patches on Gentoo ppc64le overlay
>>> <https://cgit.gentoo.org/repo/proj/ppc64le.git/>
>>> 2. The coreos@ppc64le repo manifest
>>> <https://github.com/houstar/manifest> was pushed in github
>>> 3. All CoreOS production packages was built successfully.
>>>
>>>
>>> coreos-build@gentoo /mnt/host/source/src/build/images/ppc64l
>>> e-usr/developer-1032.0.0+2016-07-18-0550-a1 $ ls
>>>
>>> configroot  coreos_developer_image.bin  coreos_developer_qemu.README
>>> coreos_developer_qemu.sh  coreos_developer_qemu_image.img
>>> developer_data  rootfs
>>>
>>> 4. This coreos_developer_qemu_image.img can't boot. This problem was
>>> due to ppc64le doesn't support UEFI and must have PReP partition for boot.
>>>
>>> For example, manually configure boot loader
>>>
>>> 1) Disk Partition
>>>        device            size              Id Type
>>>       /dev/vda1       8M               PPC PReP Boot
>>>       /dev/vda2       10G             Linux
>>>       /dev/vda3       2G               Linux Swap / Solaris
>>>
>>>  2) using genkernel-next build kernel and initrd
>>>     #genkernel --all
>>>
>>>  3) installing bootloader
>>>     #grub2-install /dev/vda1
>>>
>>>  4) generating grub.cfg
>>>    #grub2-mkconfig /boot/grub/grub.cfg
>>>
>>> grub2 platform on ppc64le is powerpc-ieee1275
>>>
>>>
>>> How to automatically range this disk partition use CoreOS SDK to support
>>> boot from qcow2 disk image ? Thanks.
>>>
>>>
>>> *Leno Hou*
>>> E-mail :  leno...@gmail.com
>>>
>>>
>>> On Sun, Jun 5, 2016 at 9:44 PM, Liang NS Zhuang <liang.zhu...@cn.ibm.com
>>> > wrote:
>>>
>>> Brandon, it was a nice talk, thanks for the time!
>>>
>>> Hello team, if necessary, we could later help to apply resource on
>>> SuperVessel (which is a Power/OpenPOWER cloud) for test..
>>> http://www-03.ibm.com/press/us/en/pressrelease/47082.wss
>>>
>>>
>>> Regards,
>>> Liang ZHUANG (庄亮, Leon), PMP, CSM
>>> Manager, Linux Dev, LTC/IBM System, CSTL/SH
>>> Ext. 86-21-609-28548
>>>
>>>
>>> [image: Inactive hide details for Brandon Philips ---06/03/2016
>>> 11:46:28---Hello Everyone- I wanted to introduce Leno and team who 
>>> are]Brandon
>>> Philips ---06/03/2016 11:46:28---Hello Everyone- I wanted to introduce Leno
>>> and team who are working on a ppc64le port of
>>>
>>> From: Brandon Philips <brandon.phil...@coreos.com>
>>> To: coreos-dev <coreos-dev@googlegroups.com>, Leno Hou <
>>> leno...@gmail.com>, Qing Yuan QQ Hou/China/IBM@IBMCN, Liang NS
>>> Zhuang/China/IBM@IBMCN, Qu KK Jiang/China/IBM@IBMCN
>>> Date: 06/03/2016 11:46
>>> Subject: ppc64le port of CoreOS
>>> ------------------------------
>>>
>>>
>>>
>>> Hello Everyone-
>>>
>>> I wanted to introduce Leno and team who are working on a ppc64le port of
>>> many of the ebuilds required by CoreOS over here:
>>> *https://github.com/linux-on-power/gentoo*
>>> <https://github.com/linux-on-power/gentoo>
>>>
>>> I talked to them on a hangout for a bit and the overall plan for this
>>> port, which they want to do the maintenance of, includes:
>>>
>>> - Waiting for all of the "second architecture" stuff to finish for ARM
>>> - Test out rkt/update_engine and some other pieces that are becoming
>>> easier to cross compile from the above work
>>> - Continue to work upstream to merge the 12 or so patches required for
>>> Gentoo
>>> - Generate and distribute an unofficial PPC64LE CoreOS SDK
>>> - Help get the SDK and build into the CoreOS build system over the next
>>> 6 months or so
>>>
>>> If anyone can help out on this stuff it would be great but it sounds
>>> like Leno and team are making great progress so far.
>>>
>>> Cheers,
>>>
>>> Brandon
>>>
>>>
>>>
>>>
>>>
>>> [image: Image.1__=C7BBF55ADFD8D09E8f9e8a93df938690918cC7B@.gif]
>>> [image: Image.1__=C7BBF55ADFD8D09E8f9e8a93df938690918cC7B@.gif][image:
>>> Image.1__=C7BBF55ADFD8D09E8f9e8a93df938690918cC7B@.gif]
>>>
>>>
>>
>

Reply via email to