Bring Up PowerKVM

So you got S822L or S824 machine which is shipped from factory.  Here we go to set up Powerkvm.  This blog talks about “How to bring up your Power8 box with PowerKVM”  and Manage/Monitor/….etc

1) Configure FSP IP

2) Configure IPMI

3) Access IMPI console to start install

4) You can install PowerKVM using DVD or over network

5) Choose which management layer to use based on your requirement

Kimchi or PowerVC  or IBM Cloud Manager (ICM) or just devstack

Kimchi  :



xcat: ( To deploy PowerKVM)

Create Power Images for Openstack

6) if you have simple use case to use create VM with libvirt/virt-install and play with VM


Clone VM:

pci passthrough to VM

Memory Balloon


Enable/Disable SMT on VM

VM Migration


7) If you want to Monitor your PowerKVM using various tools




8) Devops tools on PowerKVM


9) Upgrade

Upgrade PowerKVM

Upgrade OPAL

Upgrade Disk Adapter Microcode

10)  Tools

PowerLinux Tools

Profiler Utility tool

11) Docker on Power8

Running Docker on Power Servers:

Running Docker on Ubuntu for Power Servers

Create Dockerised applications for  Ubuntu on PPC64 servers:

How to create a Dockerized Application for Ubuntu on Power (ppc64) Servers

Running Docker on Power8

By Jean-tiare from OVH

How to create repeatable development environments on PowerKVM using Vagrant and Docker

How to create repeatable development environments on PowerKVM using Vagrant and Docker

How to use Vagrant Docker provisioner with PowerKVM

How to use Vagrant Docker provisioner with PowerKVM

How to use Vagrant with PowerKVM

How to use Vagrant with PowerKVM

Hadoop on PowerKVM

RHEVM Managing PowerKVM

Setup Chef on standalone PowerKVM Environment

1) What it is?

Chef simplifies the way you perform infrastructure automation and configuration management tasks. The standalone installation of the Chef  creates a working installation on a single server.   This setup is on  standalone environment on PowerKVM node. (No separate chef server is configured.)

2) How to install on powerkvm node.

yum search chef
============================================================================== N/S matched: chef ===============================================================================
chef.ppc64 : The full stack of chef

yum install chef.ppc64

3) Configuration files:

web.json:   This is a pointer to recipe, which user would like to run.

solo.rb: only sets two paths for Chef Solo.

default.rb: sample recipe which user would like to run. User need to keep adding recipes  as per his/her requirements

3.1) Example Cookbook  to start kimchid service on powerkvm.

cat /root/chef-repo/cookbooks/demo/recipes/default.rb

# Cookbook Name:: demo
# Recipe:: default
# Copyright 2014, YOUR_COMPANY_NAME
# All rights reserved – Do Not Redistribute

package ‘kimchi’ do
action :install

service ‘kimchid’ do
action [  :enable, :start ]

3.2) chef.solo

cat chef-repo/solo.rb
file_cache_path “/root/chef-solo”
cookbook_path “/root/chef-repo/cookbooks”

3.3) web.json

cat web.json
“run_list”: [ “recipe[demo]” ]

4) How to run

chef-solo  -c chef-repo/solo.rb -j web.json
[2014-09-16T13:42:49+01:00] WARN:
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
SSL validation of HTTPS requests is disabled. HTTPS connections are still
encrypted, but chef is not able to detect forged replies or man in the middle

To fix this issue add an entry like this to your configuration file:

# Verify all HTTPS connections (recommended)
ssl_verify_mode :verify_peer

# OR, Verify only connections to chef-server
verify_api_cert true

To check your SSL configuration, or troubleshoot errors, you can use the
`knife ssl check` command like so:

knife ssl check -c chef-repo/solo.rb

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

Starting Chef Client, version 11.12.8
Compiling Cookbooks…
Converging 2 resources
Recipe: demo::default
* package[kimchi] action install (up to date)
* service[kimchid] action enable
   – enable service service[kimchid]

* service[kimchid] action start (up to date)

Running handlers:
Running handlers complete

Chef Client finished, 1/3 resources updated in 4.874421085 seconds