Download - Migrating P2V: SUSE Linux Enterprise Server with Xen

Migrating P2V into Xenon SUSE® Linux Enterprise Server

Jason DeaProduct Marketing [email protected]

Jeff LindhomTechnical Sales [email protected]

© Novell, Inc. All rights reserved.2

What You Will Learn

PlateSpin® Technology Introduction

PlateSpin Migrate

Xen on SUSE® Linux Enterprise Server 11

Product Demo

– Xen physical to virtual migration with PS Migrate

PlateSpin® Technology Overview


Workload

Application

Middleware

Operating System

Workload: The (New) IT Paradigm

A workload is an integrated stack of application, middleware, and operating system that accomplishes a computing task

A workload is portable and platform agnostic–it can run in physical, virtual or cloud computing environments

A workload or a collection of workloads makes up a business service, which is what the end user consumes


PlateSpin® Technology

Workload Profiling• Agent-less data collection• Resource sizing and analysis

Workload Portability• Move, copy and replicate workloads• Cross infrastructure boundaries

Workload Orchestration• Policy based• Proactive automation


Workload Portability

Virtual Hosts Image Archives

Physical Servers

V2II2V

P2VV2P

P2II2P

PlateSpin® Migrate


PlateSpin® Migrate

Decouple workloadfrom host

infrastructure

Live peer-to-peerworkload migration Migration testing Sync-up prior

to cut-over

PhysicalServers

BladeServers

VirtualHosts

ImageArchives

Workload Decoupledfrom Hardware

With PlateSpin Migrate, you can automatically migrate server workloads over the network.


Server Consolidation – Why ?

Server consolidation is the process of migrating physical server workloads into a virtual environment.

Challenges – Before•Too many physical servers•Underutilized servers•Limited floor space•High power/cooling consumption•Low ROI and high TCO

Solution – After•Consolidated servers•Available floor space•Optimized resource utilization•Reclaim unused resources•Green IT/reduced carbon footprint•High ROI and low TCO


PlateSpin® Migrate and Workload Portability• Enables hardware independent migrations of server workloads

(operating system, applications and data) across x86 server infrastructure

• Automates reconfiguration of resources assigned to workloads

• Supports virtual hosts and bare metal physical machines as target platforms

• Reads data from various volume data sources to deploy or recover machines

• Provides incremental P2V, V2V, P2I, and V2I migrations for disaster recovery

• Ally Server Sync™ one time and perpetual incremental migrations


Supported Workloads

Server Operating Systems

Desktop Operating Systems

Hypervisors Hardware Support

Windows NT4, 2000, 2003,

2008

SLES 8, 9, 10, 11

RHEL 3, 4, 5

Solaris 10(SPARC)

Windows

XP, Vista

XEN on SLES

VMware ESX, ESXi

Microsoft Hyper-V

Citrix XenServer

Solaris

Dell

HO

IBM

Unisys

Fujitsu

Sun

Others


Architecture

OFXIIS/ASP.NET/C#/C++

Generic job management engine that remotely executes and monitors jobs through controllers. Applications can

be created around OFX functions.

Web Services Interface

Web Services Interface

Portability Suite Server Portability Suite

Client

Administrator

Controller Controller

WS/HTPP

Dynamic agents that reside on servers that allow PlateSpin®

To run and monitor jobs on those systems remotely.

SQLServer

OFX

Stores information on what toRun, where to run it, and whatTo do when jobs finish.

Interface for conductingserver conversions

WS/HTPP WS/HTPP

WS/HTPP


Architecture

Portability SuiteServer

Portability SuiteClient

SSH: 22 TCP

HTTP: Port80 TCP(could be HTTPS)

SMB: 139 and 445 TCP137 and 138 UDP(Take Control Only)



WMI: 135/445 TCP(plus randomly assignedPorts – see KB)

File transfer: 3725 TCPCan be encrypted with 128-bit AES

Linux VirtualMachine Server


Novell® Identity Manager

Novell® Access Manager

Novell® Roles Based Provisioning Module

Novell® Access Governance Suite

Novell Privileged User Manager

Novell® SecureLogin®

Novell® Cloud Security Service

How Novell® Delivers Intelligent Workload Management

Build Secure Manage MeasureSUSE® Linux Enterprise Server

SUSE® Studio

SUSE® Linux Enterprise JeOS

ZENworks® Configuration Management

SUSE® Appliance Toolkit

Novell® Workshop

Novell® Business Service Manager

Novell® Business Service Level Manager™

Novell® Business Experience Manager™

Novell® myCMDB™

Novell® Sentinel™

Novell® Sentinel™ Log Manager

Novell Compliance Automation

* Available by end of 2010

PlateSpin® Migrate

PlateSpin® Orchestrate

ZENworks® Configuration Management

PlateSpin® Recon

PlateSpin® Protect

PlateSpin® “Atlantic”

PlateSpin® “BlueStar”

ZENworks® “Workbench”

Xen Virtualization on SUSE® Linux Enterprise Server 11


SUSE® Linux Enterprise ServerVirtualization at Novell®

“Novell is a Virtualization Solution Provider”

“Novell is an Operating System Vendor”

SUSE Linux Enterprise Server

Guest OS

“The Perfect Guest”

Xen, KVM(SLES)

Management Tools

Host andManagement


SUSE® Linux Enterprise Server 11 Xen Virtualization

• Integrated Xen hypervisor provides reliable, high performance virtualization

• Xen 3.3.1 delivers advanced virtualization capabilities• Lowest cost solution – Host is included with OS,

and you get unlimited VMs per system• Additional management solutions are available• Supports latest Intel processor and chipset-level

virtualization advances– Intel VT FlexPriority– Intel VT FlexMigration– Intel VT for Direct I/O


SUSE® Linux Enterprise Server 11Virtualization Host

• Upgrade to Xen 3.3.1 delivers

– Architectural improvements: better scalability, performance and security

– Enhanced power management

– Improved graphical capabilities

• Open source management tools (virt-manager)

• KVM technical preview

• New paravirtualized drivers for Windows Vista and Windows Server 2008

Xen Terminology


Xen Community Terminology

• Domain: A container for a running virtual machine. Colloquially, the VM itself

• Domain 0: The first domain container created. Privileged to affect (manage) other domains. a.k.a. “dom0”

• Unprivileged Domain: Any domain other than domain 0. Cannot affect other domains. a.k.a. “domU”

• Driver Domain: Any domain that provides back end services to virtual drivers. Typically this is dom0.

• Physical Driver: A device driver that talks directly to the hardware

• Virtual Driver: A device driver in a domU that fulfills requests by going to the physical driver in the driver domain


Novell®/Industry Terminology

• Hypervisor: The entity that enables virtualization• Full-virtual: A VM mode that can run a native, unmodified

operating system by emulating all hardware devices• Paravirtual: A VM mode that can run a modified operating system,

which cooperates with the Hypervisor• VT Computer: A computer that contains processor(s) that support

virtualization technology, such as Intel VT or AMD-V. Required for fully virtual mode

• Standard Computer: A computer that does not contain processor(s) that support virtualization technology and therefore can run VMs only in paravirtual mode

• Native Operation System: A typical operating system that is not optimized for the paravirtual VM environment and must run in fully virtual mode or on “bare metal”


Novell® Terminology

• VM Server: A server running Xen, or some other hypervisor, capable of hosting VMs (i.e., xen + dom0)

> Example: SUSE® Linux Enterprise Server 10 with the Xen packages installed, booted with Xen

• VM: Virtual machines (domUs)

• Problematic terms– “Host”, “Guest”, “Domain”

– “Host” and “Guest” suggest VMware's architecture

– “Domain” can be used synonymous with “virtual machine” in the Xen community

Virtualization Modes and Xen Architecture


Virtualization Modes

Full-Virtual

– VMs can run native (unmodified) OS– Requires the need to trap and emulate

all privileged instructions*, or emulate everything

– Performance is negatively impacted– Also know as “HVM” virtual machines– Requires VT enabled CPU

*Some processors are difficult to fully virtualize such as traditional x86

Virtualization Layer

HW Platform

Apps

Operating System

Apps

Operating System

Virtual Machine (full-virtual)




Paravirtual

– Higher performance than full-virtualization

– Hypervisor is supplemented with an API that provides an assist for certain situations

– Requires hardware dependent portions of the VM OS to be modified to become aware of the virtualization layer

– Allows VMs to avoid hard to virtualize instructions by replacing them with a procedure call that provides the same functionality


HW Platform

Apps

Operating System

Apps

Operating System



Man

agem

ent A

PI

API



Enlightened Virtualization

– Hybrid of full and paravirtualization– OS is “enlightened” to know about

paravirtual hypercalls– Some parts of the OS can use

paravirtual hypercalls other parts must use trap and emulation

– Performance is improved– Requires VT enabled CPU

*For Windows Server 2008, enlightenment requires a 64 bit Xen Hypervisor


HW Platform


HW Platform

Apps

Operating System

Apps

Operating System



Man

agem

ent A

PI

Nat

ive

API

Nat

ive

API

Adapter


Xen Virtual Machine Architecture

CPU CPU

00:0

1.0

00:0

2.0

00:0

3.0

00:0

4.0

00:0

5.0

00:0

6.0

00:0

7.0

00:0

8.0

PCI Bus

Har

dwar

e

IO & Platform Devices(Disk, LAN, USB, BMC, IPMI, ACPI, etc.)

Memory & CPU(x86, x86-64, EM64T,VT)


Xen Virtual Machine ArchitectureXE

N H

yper

viso

r

CPU CPU

00:0

1.0

00:0

2.0

00:0

3.0

00:0

4.0

00:0

5.0

00:0

6.0

00:0

7.0

00:0

8.0

PCI Bus

Xen Bus

00:0

1.0

00:0

2.0

00:0

3.0

00:0

4.0

00:0

5.0

00:0

6.0

00:0

7.0

00:0

8.0

Abstracted PCI Bus

Har

dwar

e

VCPU VCPU VCPU

VCPUVCPUVCPU

VCPU

VCPU



Emulated Hardware InterfaceEnabled by X86/X86_64 VT

and Qemu



N H

yper

viso

r

CPU CPU

00:0

1.0

00:0

2.0

00:0

3.0

00:0

4.0

00:0

5.0

00:0

6.0

00:0

7.0

00:0

8.0

PCI Bus

Xen Bus

00:0

1.0

00:0

2.0

00:0

3.0

00:0

4.0

00:0

5.0

00:0

6.0

00:0

7.0

00:0

8.0

Abstracted PCI Bus

Physical Drivers

Domain 0Management OS

ParavirtualDriver

Backend

VM Management Applications

xend

xenstore

00:0

1.0

00:0

2.0

00:0

3.0

00:0

4.0

00:0

5.0

00:0

6.0

00:0

7.0

PCI Bus

Linux Kernel

CIMOMAgent

Mgmt.Path

Har

dwar

e

Xen Bus

Blo

ck

LAN

FB

VCPU VCPU

VCPU VCPU VCPU

VCPUVCPUVCPU

VCPU

VCPU




and Qemu

00:0

8.0



N H

yper

viso

r

CPU CPU

00:0

1.0

00:0

2.0

00:0

3.0

00:0

4.0

00:0

5.0

00:0

6.0

00:0

7.0

00:0

8.0

PCI Bus

Xen Bus

00:0

1.0

00:0

2.0

00:0

3.0

00:0

4.0

00:0

5.0

00:0

6.0

00:0

7.0

00:0

8.0

Abstracted PCI Bus

Physical Drivers


ParavirtualDriver

Backend


xend

xenstore

00:0

1.0

00:0

2.0

00:0

3.0

00:0

4.0

00:0

5.0

00:0

6.0

00:0

7.0

PCI Bus

Linux Kernel

Paravirtual Machine

ParavirtualDriver

Frontend

PCI Bus

VCPU VCPU VCPU

VCPUVCPUVCPU

Linux Kernel

ApplicationsCIMOMAgent

Mgmt.Path

Har

dwar

e

Xen Bus

Blo

ck

LAN

FB

Xen Bus

Blo

ck

LAN

FB

VCPU VCPU

VCPU VCPU VCPU

VCPUVCPUVCPU

VCPU

VCPU




and Qemu

00:0

8.0



N H

yper

viso

r

CPU CPU

00:0

1.0

00:0

2.0

00:0

3.0

00:0

4.0

00:0

5.0

00:0

6.0

00:0

7.0

00:0

8.0

PCI Bus

Xen Bus

00:0

1.0

00:0

2.0

00:0

3.0

00:0

4.0

00:0

5.0

00:0

6.0

00:0

7.0

00:0

8.0

Abstracted PCI Bus

Physical Drivers


ParavirtualDriver

Backend


xend

xenstore

00:0

1.0

00:0

2.0

00:0

3.0

00:0

4.0

00:0

5.0

00:0

6.0

00:0

7.0

PCI Bus

Linux Kernel

Paravirtual Machine

ParavirtualDriver

Frontend

PCI Bus

VCPU VCPU VCPU

VCPUVCPUVCPU

Linux Kernel

Applications

PhysicalDrivers

Paravirtual Machine

ParavirtualDriver

Frontend

Other OS Kernel


Mgmt.Path

Har

dwar

e

Xen Bus

Blo

ck

LAN

FB

Xen Bus

Blo

ck

LAN

FB

Xen Bus

Blo

ck

LAN

FB

VCPU VCPU VCPU VCPU

VCPUVCPU

VCPU VCPU VCPU

VCPUVCPUVCPU

VCPU

VCPU




and Qemu00

:00.

0

PCI Bus



N H

yper

viso

r

CPU CPU

00:0

1.0

00:0

2.0

00:0

3.0

00:0

4.0

00:0

5.0

00:0

6.0

00:0

7.0

00:0

8.0

PCI Bus

Xen Bus

00:0

1.0

00:0

2.0

00:0

3.0

00:0

4.0

00:0

5.0

00:0

6.0

00:0

7.0

00:0

8.0

Abstracted PCI Bus

Physical Drivers


ParavirtualDriver

Backend


xend

xenstore

00:0

1.0

00:0

2.0

00:0

3.0

00:0

4.0

00:0

5.0

00:0

6.0

00:0

7.0

PCI Bus

Linux KernelPhysical Drivers

Full-virtual Machine

ParavirtualDriver

Frontend

00:0

1.0

00:0

2.0

00:0

3.0

00:0

4.0

00:0

5.0

00:0

6.0

00:0

7.0

00:0

8.0

PCI Bus

Other OS Kernel


Mgmt.Path

Har

dwar

e

Xen Bus

Blo

ck

LAN

FB

Xen Bus

Blo

ck

LANVCPU VCPU VCPU

VCPU VCPU VCPU

VCPUVCPUVCPU

VCPU

VCPU




and Qemu

QemuEmulated

DriverBackend



N H

yper

viso

r

CPU CPU

00:0

1.0

00:0

2.0

00:0

3.0

00:0

4.0

00:0

5.0

00:0

6.0

00:0

7.0

00:0

8.0

PCI Bus

Xen Bus

00:0

1.0

00:0

2.0

00:0

3.0

00:0

4.0

00:0

5.0

00:0

6.0

00:0

7.0

00:0

8.0

Abstracted PCI Bus

Physical Drivers


ParavirtualDriver

Backend


xend

xenstore

00:0

1.0

00:0

2.0

00:0

3.0

00:0

4.0

00:0

5.0

00:0

6.0

00:0

7.0

PCI Bus

Linux Kernel

Paravirtual Machine

ParavirtualDriver

Frontend

PCI Bus

VCPU VCPU VCPU

VCPUVCPUVCPU

Linux Kernel

Applications

Physical Drivers

Paravirtual Machine

ParavirtualDriver

Frontend

Other OS Kernel

Applications

Physical Drivers

Full-virtual Machine

ParavirtualDriver

Frontend

00:0

1.0

00:0

2.0

00:0

3.0

00:0

4.0

00:0

5.0

00:0

6.0

00:0

7.0

00:0

8.0

PCI Bus

Other OS Kernel


Mgmt.Path

Har

dwar

e

Xen Bus

Blo

ck

LAN

FB

Xen Bus

Blo

ck

LAN

Xen Bus

Blo

ck

LAN

FB

Xen Bus

Blo

ck

LAN

FB

VCPU VCPU VCPUVCPU VCPU

VCPUVCPU

VCPU VCPU VCPU

VCPUVCPUVCPU

VCPU

VCPU




and Qemu

QemuEmulated

DriverBackend

00:0

0.0

PCI Bus


Additional Technical Information:

• SUSE® Linux Enterprise Server 11 Virtualization Technology Support Whitepaper:

– Supported operating system platforms– Hardware limits– Feature support

• http://www.novell.com/rc/docrepository/public/37/basedocument.2009-08-13.0610322648/SLES_Virt_Tech_Support_f_en.pdf

Or simply visit: http://bit.ly/adqJ2U

• Appendix slides provide vital statistics

http://bit.ly/adqJ2U

Product Demo


Appendix SUSE® Linux Enterprise Server 11 Virtualization Support

Hardware Limits – SLES11 XEN

VM Supported Configuration Limits – SLES11 XEN

Unpublished Work of Novell, Inc. All Rights Reserved.This work is an unpublished work and contains confidential, proprietary, and trade secret information of Novell, Inc. Access to this work is restricted to Novell employees who have a need to know to perform tasks within the scope of their assignments. No part of this work may be practiced, performed, copied, distributed, revised, modified, translated, abridged, condensed, expanded, collected, or adapted without the prior written consent of Novell, Inc. Any use or exploitation of this work without authorization could subject the perpetrator to criminal and civil liability.

General DisclaimerThis document is not to be construed as a promise by any participating company to develop, deliver, or market a product. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. Novell, Inc. makes no representations or warranties with respect to the contents of this document, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. The development, release, and timing of features or functionality described for Novell products remains at the sole discretion of Novell. Further, Novell, Inc. reserves the right to revise this document and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes. All Novell marks referenced in this presentation are trademarks or registered trademarks of Novell, Inc. in the United States and other countries. All third-party trademarks are the property of their respective owners.

Download - Migrating P2V: SUSE Linux Enterprise Server with Xen

Top Related