(Difference between revisions)
Jump to: navigation, search

Features/Vdsm for PPC64

(Approach)
(User Interface)
 
Line 66: Line 66:
  
 
No new user interfaces are required to be added. However few of the existing
 
No new user interfaces are required to be added. However few of the existing
interfaces needs to be updated to reflect KVM on IBM POWER related specifics
+
interfaces needs to be updated to reflect KVM on IBM POWER related specifics.
  
 
At the minimum following user interfaces will be affected
 
At the minimum following user interfaces will be affected

Latest revision as of 20:52, 17 September 2012

Contents

[edit] Summary

This feature provides support for managing KVM on IBM POWER processors via oVirt.

Qemu and Libvirt support for KVM on IBM POWER processors is already available and is part of the respective upstream versions of the packages

All POWER Linux distributions (RHEL 6.x, SLES 11.x, Debian 6.x, Fedora 16+) that support Power7 native mode are supported as KVM guests. This limits older distributions, such as SUSE 10 and RHEL 5.x


[edit] Owner

  • Feature owner: Pradipta Kr. Banerjee <bpradip@in.ibm.com>
    • REST Component owner: Ricardo Marin Matinata <rmm@br.ibm.com>
    • Engine Component owner: Ricardo Marin Matinata <rmm@br.ibm.com>
    • VDSM Component owner: Pradipta Kr. Banerjee <bpradip@in.ibm.com>
    • QA Owner: Li AG Zhang <zhlbj@cn.ibm.com>

[edit] Current Status

  • Status: Design Stage


[edit] Detailed Description

This feature will introduce the capability of managing KVM on IBM POWER processors via oVirt. Administrators will be able to perform management fuctionalities like:

  • Add/Activate KVM on IBM POWER host
  • Create cluster of KVM on IBM POWER hosts
  • Perform VM lifecycle management on any IBM POWER host
    • create
    • start
    • stop
    • edit
    • remove
    • pause
    • migrate

Migrate is still work in progress for KVM on IBM POWER processor

[edit] Approach

Managing KVM on IBM POWER processors requires changes to both vdsm and ovirt-engine. However the intent is to keep ovirt-engine changes to the minimum

Following are the key changes that will be required

  • Enhancing the bootstrapping mechanism in VDSM to handle IBM POWER processor and ppc64 specifics (like cpuid, cpu speed, cpu flags)
  • Adding a new CPU type (IBM POWER) to ovirt-engine
  • Enhancing the VM templates based on guest device models (disk, network, video) supported by KVM on IBM POWER

KVM on IBM POWER supports the following device models for guest

  • virt-io, spapr-vscsi for disk
  • virt-io, e1000, rtl and spapr-vlan for network
  • vga device is supported for guest video
  • Only VNC backend is supported for guest console access.

There is currently no support for SPICE protocol and USB support in guests.

Both NFS and SAN storage is supported for the hosts. iSCSI support is currently work in progress

[edit] User Interface

No new user interfaces are required to be added. However few of the existing interfaces needs to be updated to reflect KVM on IBM POWER related specifics.

At the minimum following user interfaces will be affected

  • New Server/New Desktop Virtual Machine in userportal
  • New Server/New Desktop Virtual Machine in webadmin
  • Make Template in userportal and webadmin
  • Editing Virtual Disks and Editing Network Interfaces in webadmin
  • New Cluster in webadmin

[edit] Benefits to oVirt

oVirt would be able to support KVM running on IBM POWER processor based systems

[edit] Dependencies / Related Features and Projects

Affected oVirt projects:

  • Engine-core
  • VDSM

[edit] Documentation / External references

KVM on IBM POWER : http://www.linux-kvm.org/wiki/images/5/5d/2011-forum-KVM_on_the_IBM_POWER7_Processor.pdf

[edit] Comments and Discussion

[edit] Future Work

[edit] Open Issues