Ppc64le: Difference between revisions

From Alpine Linux
(→‎Booting Alpine from CDROM using qemu: Don't recommend "enable-kvm" by default. It makes no sense unless the host is the same architecture as the guest.)
(15 intermediate revisions by 5 users not shown)
Line 1: Line 1:
This page is used to describe the ppc64le port.
This page is used to describe the [https://en.wikipedia.org/wiki/Ppc64 ppc64le] port.


== Testing (for developers) ==
= Testing (for developers) =


The hosting sponsor for the ppc64le port operate a miniCloud service which will provide Alpine ppc64le images for testing.
The hosting sponsor for the '''ppc64le''' port operates a miniCloud service, which provides ppc64le images to Alpine for testing.


View their website at http://openpower.ic.unicamp.br/minicloud/ for more info.
View [http://openpower.ic.unicamp.br/minicloud/ their] website for more info.


== Hardware ==
= Hardware =
   
   
You can buy POWER8 hardware from IBM or other vendors, for example the IBM S812LC server is reasonably price competitive to similar x86 servers and fully supported by the ppc64le port.
You can buy [https://en.wikipedia.org/wiki/POWER8 POWER8] or [https://en.wikipedia.org/wiki/POWER9 POWER9] hardware from IBM or from other vendors. For example, the '''Raptor Computing System Blackbird''' workstation is reasonably priced, competitive when compared to similar x86 servers, and is fully supported by the ppc64le port.
 
These are the IBM machines model that would support Alpine Linux:
 
The following are the '''IBM''' machine models that would support Alpine Linux:
* IBM Power System S821LC  [http://www-03.ibm.com/systems/power/hardware/s821lc/index.html]
* IBM Power System S821LC  [http://www-03.ibm.com/systems/power/hardware/s821lc/index.html]{{dead link}}
* IBM Power System S822LC for Big Data [http://www-03.ibm.com/systems/power/hardware/s822lc-big-data/index.html]
* IBM Power System S822LC for Big Data [http://www-03.ibm.com/systems/power/hardware/s822lc-big-data/index.html]{{dead link}}
* IBM Power System S822LC for Commercial Computing [http://www-03.ibm.com/systems/power/hardware/s822lc-commercial/index.html]
* IBM Power System S822LC for Commercial Computing [http://www-03.ibm.com/systems/power/hardware/s822lc-commercial/index.html]{{dead link}}
* IBM Power System S822LC for High Performance Computing [IBM Power System S822LC for High Performance Computing]
* IBM Power System S822LC for High Performance Computing [IBM Power System S822LC for High Performance Computing]
* IBM Power System S812L and S822L [http://www-03.ibm.com/systems/power/hardware/s812l-s822l/index.html]
* IBM Power System S812L and S822L [http://www-03.ibm.com/systems/power/hardware/s812l-s822l/index.html]{{dead link}}
* IBM Power System S824L [http://www-03.ibm.com/systems/power/hardware/s824l/index.html]
* IBM Power System S824L [http://www-03.ibm.com/systems/power/hardware/s824l/index.html]{{dead link}}
* IBM Power System S812 [http://www-03.ibm.com/systems/power/hardware/s812/index.html]
* IBM Power System S812 [http://www-03.ibm.com/systems/power/hardware/s812/index.html]{{dead link}}
* IBM Power System S822 [http://www-03.ibm.com/systems/power/hardware/s822/index.html]
* IBM Power System S822 [http://www-03.ibm.com/systems/power/hardware/s822/index.html]{{dead link}}
* IBM Power System S814 [http://www-03.ibm.com/systems/power/hardware/s814/index.html]
* IBM Power System S814 [http://www-03.ibm.com/systems/power/hardware/s814/index.html]{{dead link}}
* IBM Power System S824 [http://www-03.ibm.com/systems/power/hardware/s824/index.html]
* IBM Power System S824 [http://www-03.ibm.com/systems/power/hardware/s824/index.html]{{dead link}}
* IBM Power Enterprise Systems for the cloud [http://www-03.ibm.com/systems/power/hardware/enterprise-cloud/index.html]
* IBM Power Enterprise Systems for the cloud [http://www-03.ibm.com/systems/power/hardware/enterprise-cloud/index.html]{{dead link}}
* IBM Power System E850C [http://www-03.ibm.com/systems/power/hardware/e850c/index.html]
* IBM Power System E850C [http://www-03.ibm.com/systems/power/hardware/e850c/index.html]{{dead link}}
* IBM Power System E850 [http://www-03.ibm.com/systems/power/hardware/e850/index.html]
* IBM Power System E850 [http://www-03.ibm.com/systems/power/hardware/e850/index.html]{{dead link}}
* IBM Power System E870 [http://www-03.ibm.com/systems/power/hardware/e870/index.html]
* IBM Power System E870 [http://www-03.ibm.com/systems/power/hardware/e870/index.html]{{dead link}}
* IBM Power System E880 [http://www-03.ibm.com/systems/power/hardware/e880/index.html]
* IBM Power System E880 [http://www-03.ibm.com/systems/power/hardware/e880/index.html]{{dead link}}
 
 
'''Raptor Computing System''' also has machines:
* Talos II [https://www.raptorcs.com/content/base/products.html]
* Blackbird [https://www.raptorcs.com/content/base/products.html]


Tyan also has machines:


'''Tyan''' also has machines:
* Tyan TN76-BP016  
* Tyan TN76-BP016  
* Tyan GT75-BP012
* Tyan GT75-BP012
Line 36: Line 41:




Open Power machines:
'''Open Power''' machines:
 
* Rackspace Barreleye [https://www.nextplatform.com/2015/10/19/rackspace-forges-first-barreleye-openpower-servers/]
* Rackspace Barreleye [https://www.nextplatform.com/2015/10/19/rackspace-forges-first-barreleye-openpower-servers/]
* Google Zaius [https://cloudplatform.googleblog.com/2016/10/introducing-Zaius-Google-and-Rackspaces-open-server-running-IBM-POWER9.html]
* Google Zaius [https://cloudplatform.googleblog.com/2016/10/introducing-Zaius-Google-and-Rackspaces-open-server-running-IBM-POWER9.html]


== Installation ==
= Installation =


The Alpine 3.6 ppc64le ISO is available at: http://rsync.alpinelinux.org/alpine/v3.6/releases/ppc64le/alpine-vanilla-3.6.0-ppc64le.iso. <br>
The Alpine 3.11.5 ppc64le ISO is available [http://dl-cdn.alpinelinux.org/alpine/v3.11/releases/ppc64le/alpine-standard-3.11.5-ppc64le.iso here].
The user login is "root" with no password.
<br><br>


* Booting Alpine using qemu
The user login is '''root''' with no password.


To start qemu using the Alpine ISO as cdrom, you can use a command similar to:<br>
== Booting Alpine from CDROM using qemu ==
$ sudo qemu-system-ppc64 -device spapr-vlan,netdev=net0,mac=4C:45:42:45:79:F7 -netdev bridge,br=br0,id=net0 -enable-kvm -m 8G -smp 16,sockets=16,cores=1,threads=1 -nodefaults -nographic -serial stdio -cdrom alpine-vanilla-3.6.0.ppc64le.iso
<br><br>


* Installing Alpine to hard-disk
To start qemu using the Alpine ISO as cdrom, you can use a command similar to:
$ sudo qemu-system-ppc64 -device spapr-vlan,netdev=net0,mac=4C:45:42:45:79:F7 -netdev bridge,br=br0,id=net0 -m 8G -smp 16,sockets=16,cores=1,threads=1 -nodefaults -nographic -serial stdio -cdrom alpine-standard-3.11.5-ppc64le.iso


This feature is not currently supported.
If running on a ppc64le host, you can append '''-enable-kvm''' to the above command.
<br><br>


* Booting Alpine using qemu and saving modifications between reboots
== Installing Alpine to hard-disk using qemu ==


When using Alpine in this mode, you need to use Alpine Local Backup (lbu) to save your modifications between reboots and that requires some writable medium, usually removable. <br><br>
Create a disk to install Alpine on it:
$ qemu-img create alpine_disk.img 16G


Create a disk to save Alpine modifications <br>
Start qemu attaching the created disk and using Alpine ISO as cdrom. Here is an example of the qemu command:
$ qemu-img create alpine_disk.img 8G <br>
$ sudo qemu-system-ppc64 -hda alpine_disk.img -device spapr-vlan,netdev=net0,mac=4C:45:42:45:79:F7 -netdev bridge,br=br0,id=net0 -enable-kvm -m 8G -smp 16,sockets=16,cores=1,threads=1 -nodefaults -nographic -serial stdio -cdrom alpine-standard-3.11.5-ppc64le.iso
<br>


Start qemu attaching the created disk and using Alpine ISO as cdrom. An example of a qemu command <br>
Run the <code>setup-alpine</code> script:
$ sudo qemu-system-ppc64 -hda alpine_disk.img -device spapr-vlan,netdev=net0,mac=4C:45:42:45:79:F7 -netdev bridge,br=br0,id=net0 -enable-kvm -m 8G -smp 16,sockets=16,cores=1,threads=1 -nodefaults -nographic -serial stdio -cdrom alpine-vanilla-3.6.0-ppc64le.iso  <br>
$ setup-alpine
<br>


Format the attached disk and add it to /etc/fstab file: <br>
After running the <code>setup-alpine</code> script, select the disk (in this example, '''sda''') when the following configuration appears:
$ apk add e2fsprogs  <br>
<pre>
Available disks are:
sda  (17.2 GB QEMU    QEMU HARDDISK)
Which disk(s) would you like to use? (or '?' for help or 'none') [none] : sda
</pre>
 
When asked how you would like to use the disk, select '''sys''', and select '''yes''' when asked whether to erase the disk.
 
NOTE: [https://gitlab.alpinelinux.org/alpine/aports/issues/11384 The grub-ieee1275 and sfdisk are not included in ISO]. Internet connection is required to complete the setup.
The installation will format the disk properly.  After this finishes, type <code>reboot</code>.
 
== Booting Alpine from CDROM using qemu and saving modifications between reboots ==
 
When using Alpine in this mode, you need to use Alpine Local Backup (<code>lbu</code>) to save your modifications between reboots.  This requires some writable medium, usually removable.
 
Create a disk to save Alpine modifications:
$ qemu-img create alpine_disk.img 8G
 
Start qemu attaching the created disk and using Alpine ISO as cdrom. Here is the example of the qemu command:
$ sudo qemu-system-ppc64 -hda alpine_disk.img -device spapr-vlan,netdev=net0,mac=4C:45:42:45:79:F7 -netdev bridge,br=br0,id=net0 -enable-kvm -m 8G -smp 16,sockets=16,cores=1,threads=1 -nodefaults -nographic -serial stdio -cdrom alpine-standard-3.11.5-ppc64le.iso
 
Format the attached disk and add it to the {{path|/etc/fstab}} file:
<pre>
$ apk add e2fsprogs   
$ mkfs.ext4 /dev/sda  <br>
$ mkfs.ext4 /dev/sda  <br>
$ echo "/dev/sda        /media/sda      ext4    noauto,rw 0 0" >> /etc/fstab  <br>
$ echo "/dev/sda        /media/sda      ext4    noauto,rw 0 0" >> /etc/fstab  <br>
$ mkdir /media/sda  <br>
$ mkdir /media/sda  <br>
$ mkdir /media/sda/cache <br>
$ mkdir /media/sda/cache <br>
<br>
</pre>
 
Set <code>lbu</code> to write to the attached disk, setting <code>LBU_MEDIA=sda</code> in the {{path|/etc/lbu/lbu.conf}} file.
 
Run the <code>setup-alpine</code> command, and select the following configurations when asked:
* Enter where to store configs: <code>('floppy', 'sda', 'usb' or 'none') [none]: sda </code>
* Enter apk cache directory <code>(or '?' or 'none') [/media/sda/cache]: /media/sda/cache</code>
 
The last step is to commit the changes:
$ lbu commit
 
After performing these configurations, you can reboot Alpine and the modifications will be saved. The next time a change happens, you just need to run the <code>lbu commit</code> command, as the configurations are already done.


Set lbu to write in the attached disk, setting LBU_MEDIA=sda in /etc/lbu/lbu.conf file  <br>
It is important to know that, by default, <code>lbu</code> only cares about modifications in {{path|/etc}} and its subfolders, with the exception of {{path|/etc/init.d}}!
<br>


Run "setup-alpine" command and select the following configurations when asked: <br>
= See also =
- Enter where to store configs ('floppy', 'sda', 'usb' or 'none') [none]: sda <br>
* [[Alpine_local_backup|Alpine local backup]] - For more information about how to use <code>lbu</code> and how to include a new folder to backup.
- Enter apk cache directory (or '?' or 'none') [/media/sda/cache]: /media/sda/cache <br>
<br>


Last step is to commit the changes <br>
= Reference =
$ lbu commit <br>
* ABI - https://openpowerfoundation.org/?resource_lib=64-bit-elf-v2-abi-specification-power-architecture
<br>


After doing this configurations, you can reboot your alpine and modifications will be saved. The next time a change happens, you just need to run "lbu commit" command, as the configurations are already done.<br>
[[Category:Hardware]]
It is import to know that by default lbu only cares about modifications in /etc and its subfolders, with the exception of /etc/init.d!. For more information about how to use lbu and include new folder to backup: https://wiki.alpinelinux.org/wiki/Alpine_local_backup

Revision as of 20:28, 6 September 2022

This page is used to describe the ppc64le port.

Testing (for developers)

The hosting sponsor for the ppc64le port operates a miniCloud service, which provides ppc64le images to Alpine for testing.

View their website for more info.

Hardware

You can buy POWER8 or POWER9 hardware from IBM or from other vendors. For example, the Raptor Computing System Blackbird workstation is reasonably priced, competitive when compared to similar x86 servers, and is fully supported by the ppc64le port.


The following are the IBM machine models that would support Alpine Linux:


Raptor Computing System also has machines:


Tyan also has machines:

  • Tyan TN76-BP016
  • Tyan GT75-BP012
  • Tyan TN71-BP012


Open Power machines:

  • Rackspace Barreleye [17]
  • Google Zaius [18]

Installation

The Alpine 3.11.5 ppc64le ISO is available here.

The user login is root with no password.

Booting Alpine from CDROM using qemu

To start qemu using the Alpine ISO as cdrom, you can use a command similar to:

$ sudo qemu-system-ppc64 -device spapr-vlan,netdev=net0,mac=4C:45:42:45:79:F7 -netdev bridge,br=br0,id=net0 -m 8G -smp 16,sockets=16,cores=1,threads=1 -nodefaults -nographic -serial stdio -cdrom alpine-standard-3.11.5-ppc64le.iso

If running on a ppc64le host, you can append -enable-kvm to the above command.

Installing Alpine to hard-disk using qemu

Create a disk to install Alpine on it:

$ qemu-img create alpine_disk.img 16G

Start qemu attaching the created disk and using Alpine ISO as cdrom. Here is an example of the qemu command:

$ sudo qemu-system-ppc64 -hda alpine_disk.img -device spapr-vlan,netdev=net0,mac=4C:45:42:45:79:F7 -netdev bridge,br=br0,id=net0 -enable-kvm -m 8G -smp 16,sockets=16,cores=1,threads=1 -nodefaults -nographic -serial stdio -cdrom alpine-standard-3.11.5-ppc64le.iso

Run the setup-alpine script:

$ setup-alpine

After running the setup-alpine script, select the disk (in this example, sda) when the following configuration appears:

Available disks are:
sda   (17.2 GB QEMU     QEMU HARDDISK)
Which disk(s) would you like to use? (or '?' for help or 'none') [none] : sda

When asked how you would like to use the disk, select sys, and select yes when asked whether to erase the disk.

NOTE: The grub-ieee1275 and sfdisk are not included in ISO. Internet connection is required to complete the setup.

The installation will format the disk properly. After this finishes, type reboot.

Booting Alpine from CDROM using qemu and saving modifications between reboots

When using Alpine in this mode, you need to use Alpine Local Backup (lbu) to save your modifications between reboots. This requires some writable medium, usually removable.

Create a disk to save Alpine modifications:

$ qemu-img create alpine_disk.img 8G 

Start qemu attaching the created disk and using Alpine ISO as cdrom. Here is the example of the qemu command:

$ sudo qemu-system-ppc64 -hda alpine_disk.img -device spapr-vlan,netdev=net0,mac=4C:45:42:45:79:F7 -netdev bridge,br=br0,id=net0 -enable-kvm -m 8G -smp 16,sockets=16,cores=1,threads=1 -nodefaults -nographic -serial stdio -cdrom alpine-standard-3.11.5-ppc64le.iso 

Format the attached disk and add it to the /etc/fstab file:

$ apk add e2fsprogs  
$ mkfs.ext4 /dev/sda  <br>
$ echo "/dev/sda        /media/sda      ext4    noauto,rw 0 0" >> /etc/fstab  <br>
$ mkdir /media/sda  <br>
$ mkdir /media/sda/cache <br>

Set lbu to write to the attached disk, setting LBU_MEDIA=sda in the /etc/lbu/lbu.conf file.

Run the setup-alpine command, and select the following configurations when asked:

  • Enter where to store configs: ('floppy', 'sda', 'usb' or 'none') [none]: sda
  • Enter apk cache directory (or '?' or 'none') [/media/sda/cache]: /media/sda/cache

The last step is to commit the changes:

$ lbu commit 

After performing these configurations, you can reboot Alpine and the modifications will be saved. The next time a change happens, you just need to run the lbu commit command, as the configurations are already done.

It is important to know that, by default, lbu only cares about modifications in /etc and its subfolders, with the exception of /etc/init.d!

See also

  • Alpine local backup - For more information about how to use lbu and how to include a new folder to backup.

Reference

* ABI - https://openpowerfoundation.org/?resource_lib=64-bit-elf-v2-abi-specification-power-architecture