veyepar: KVM on IBM POWER8 servers

Author(s):	Paul Mackerras
Location	OGGB 260-098
Date	jan Wed 14	Days Raw Files
Start	13:20	First Raw Start	12:21
Duration	0:45:00	Offset	0:58:07
End	14:05	Last Raw End	14:06
Chapters	00:00
Total cuts_time	44 min.

http://lca2015.linux.org.au/schedule/30188/view_talk
raw-playlist raw-mp4-playlist encoded-files-playlist host public tweet mp4 svg png

assets release.pdf KVM_on_IBM_POWER8_servers.json
logs
Admin: episode episode list cut list raw files day marks day marks day image_files

State:
Locked:	clear this to unlock
Locked by:	user/process that locked.
Start:	initially scheduled time from master, adjusted to match reality
Duration:	length in hh:mm:ss
Name:	Video Title (shows in video search results)
Emails:	email(s) of the presenter(s)
Released:	has someone authorised pubication
Normalise:
Channelcopy:	m=mono, 01=copy left to right, 10=right to left, 00=ignore.
Thumbnail:	filename.png
Description:	Last June, IBM released server machines based on its new POWER8 processor chip. Among the many cool new features in these systems, one stands out: you can now order these systems with KVM as the hypervisor, as an alternative to IBM's proprietary PowerVM. Our flavour of KVM (we call it PowerKVM) is based on the Linux kernel, KVM, qemu and libvirt, all of which are open source. We also include the open-source Kimchi web interface for virtualization management, or OpenStack or oVirt can be used for management. The host kernel on these POWER8 machines uses the services of a piece of firmware called OPAL, for Open Power Abstraction Layer. OPAL is open source, and provides services such as console, real-time clock, non-volatile RAM and a boot loader. This presentation examines this software stack and covers the issues in porting KVM to run on the POWER8 CPU, which was designed for PowerVM. Some ingenuity was required to bridge the gap to the KVM model of virtualization. In particular, each POWER8 core has 8 hardware threads, but will only run 4 separate guests simultaneously, which creates interesting problems in scheduling guests. markdown
Comment:	production notes