Virtualization And Its Impact On interoperability between Windows and Linux

1

• Virtualization And Its ImpactOn interoperability
  between Windows and Linux

Tom Hanrahan Director of Linux Interoperability Mi
crosoft hanrahat_at_microsoft.com
2
Windows And Linux Interoperability

• Why interoperability?
• The market for heterogeneous solutions is growing
  rapidly
• Two platforms will continue to dominate the x86
  datacenter Windows and Linux
• Why now?
• Customers are asking
• Microsoft-Novell Technical Collaboration
  Agreementis a unique opportunity
• Why virtualization now Around since the 70s?
• Process virtualization
• System virtualization

3
Process Virtualization
4
Process Virtual Machines

• Runtime environments

• Examples
• Java
• Java VM
• .Net
• Common LanguageRuntime (CLR)?
• Mono
• CLR

Application
VMM
Host OS
Hardware
5
CLR And Interoperability

• CLR Projects
• Novell
• Silverlight/Moonlight
• Interoperability Projects
• PHP Community
• Fast CGI, PHP-sql server driver, PEAR/ADODB
  support
• MySQL Community
• Visual Studio Connector
• Apache Foundation
• Technology transfers
• Eclipse Foundation
• C authoring support

6
Interoperability By Design

• Application interoperability

W I S N
W I S P
W I M P
W A S P
W A M P
L A M P
Windows
Linux
7
System Virtualization
8
Virtualization Terminology

• Optimizations
• Full virtualization (no optimizations)?
• Paravirtualization
• Enlightenment
• Hardware-enabled Virtualization
• Intel-VT
• AMD-V

9
Virtual Machines

• System Virtual Machines (Type-2)?

• Examples
• Virtual PC
• Virtual Server
• VMWare GSX

Guest 2
Guest 1
VMM
Host OS
Hardware
10
Virtual Machines

• System Virtual Machines (Type-1)?

• Examples
• Hyper-V
• Xen
• VMWare ESX

Parent
Guest 1
Guest 2
VMM
Hardware
11
Windows Hyper-V Architecture
Interoperablity Component
Parent Partitions
Child Partitions
Windows Applications
Linux Applications
VM Worker Processes
UserMode
Wsv-EnabledLinux Kernel
Windows Server 2008
Windows Server 2008
KernelMode
Windows Hyper-V
Virtualization-enabled Hardware
12
Optimizations

• Windows Hyper-V Enlightenments
• Optimized specifically for WS 2008 on Hyper-V
• Designed for WS 2008 to run unmodified as a host
  on HW ora guest in a VM dynamic binary
  switching (bi-modal approach)?
• Designed for enlightenment optimizations tobe
  deployed dynamically when Hyper-V
  detectsvirtualization-assisted hardware
• Integration components designed to optimizeLinux
  running on Hyper-V

13
Interoperability By Design

• Stack Interoperability

System Center
W I S N
W I S P
W I M P
W A S P
W A M P
W I S N
W I S P
W I M P
W A S P
W A M P
L A M P
Windows
Hyper-V
14
Xen Architecture
Interoperablity Component
Dom O
Dom U
Dom U
Windows Applications
Linux Applications
VMM Services
UserMode
SLES 10
SLES 10
Windows Server 2008
Win Kernel
Win Kernel
KernelMode
Xen/Windows ABI
Xen (hypervisor)?
Hardware
15
Optimizations

• Xen and Linux Paravirtualization
• Includes an API designed to encourage
  open-sourcehypervisors and drivers
• Allows Linux to run as a guest on both
  virtualization-assistedand non-virtualization-ass
  isted hardware
• Began as a modification to the Linux Kernel that
  required re-compilation now moving to a
  bi-modal approach with paravirt_ops

16
Interoperability By Design

• Stack Interoperability

Orchestrator
L A M P
W I S N
W I S P
W I M P
W A S P
W A M P
L A M P
Linux
Xen
17
Managing Virtual Environments
18
Standards-Based SystemManagement of virtual
machines
Novell Solution
Microsoft Solution
Zen Orchestrator
System Center
Updt Mgr
VM Mgr
Exc Mgr
Ops Mgr
Conf Mgr
ws-man binding
CIMOM
ws-man binding
P r o v
P r o v
P r o v
P r o v
P r o v
WMI
Linux
Windows
19
Interoperability By Design

• Platform Interoperability

Orchestrator
System Center
L A M P
W I S N
W I S P
W I M P
W A S P
W A M P
L A M P
W I S N
W I S P
W I M P
W A S P
W A M P
W I S N
W I S P
W I M P
W A S P
W A M P
L A M P
Linux
Xen
Windows
Hyper-V
20
Testing Virtualization For Interoperability
21
Microsoft-Novell Interoperability Lab
22
Microsoft-Novell Interoperability Lab

• Jointly staffed by Microsoft and Novell
• 2500 square feet of lab and office space
• 80 servers running Intel dual- and quad-coreand
  AMD dual-core technology
• 2 TB Storage Area Network
• Designed to represent state-of-the-art data center

23
Challenges

• Why is Virtualization Interoperability hard to
  test?

Two operating system technologies to understand
Heterogeneous environments to test
Integration components to test
Two development organizations to work with to
analyze and fix defects
Kernel-level debugging skills required in both
Both operating systems to test across
all environments
Linux VSC, Windows PV Drivers, Xen/Windows
ABI, Hypercalladapter
Single-core, dual-core, multi-core CPUs
Different engineering cultures
Intel-VT andAMD-V processors
24
Linux On Hyper-V Testing

• Functional Testing
• Boot tests
• SLES 10.1 64-bit/32-bit
• Installation tests
• Pass-through CD/DVD, ISO files, PXE boot
• Migration tests
• From Virtual PC SLES 10.1 32-bit
• Integration Components
• Set up, Localization, Storage VSC, Network VSC

25
Linux On Hyper-V Testing

• Stress Testing
• Kernbench
• CPU and memory
• Bash-shared-mapping
• Memory
• Reaim
• IO (network, disk) and CPU
• Tiobench
• IO (disk)?
• Netperf
• IO (network)

26
Linux On Hyper-V Testing

• Performance Testing
• LM Bench
• CPU and memory performance
• Dbench
• Filesystem performance
• Netperf
• Network performance
• Tiobench
• IO performance
• SPEC JBB 2005
• Three-tier client/server performance

27
Windows 2008 On Xen Testing

• Functional Testing
• Install and boot
• Pause/unpause
• Suspend/relocate/resume
• Live migration
• Dynamic allocation (vCPU and memory)?
• HAL Timer Tests
• PCI hardware compliance test for systemsrunning
  Windows Vista
• SMBIOS HCT
• AC3 Test Server
• Cardbus Bridge Register Assertion

28
Windows 2008 On Xen Testing

• Stress Testing
• Disk Stress
• Common Scenario Stress with IO
• LoadGen Server Stress

29
Standards-Based System ManagementOf virtual
machines

• Virtual machine management
• Standards-based system management tools
• Distributed Management Task Force (DMTF)?
• Web-Based Enterprise Management (WBEM)?
• Web Services for Management protocol
  (ws_management)?

30
Compliance Versus Interoperability

• Compliance

Interoperability
SUT2
Control and observation
TestSystem
SUT
SUT1
SUT n
WS-Man Spec
31
Compliance Tool Requirements

• Compliance test tool for WinRM of the DMTF
  specification for the ws-man protocol
• Objective
• Verify that WS2008/ws-man can talk to
  Linux/ws-man
• Tool requirements
• Rule engine for protocol conformance
• Ability to set up ws-man sessions between WS2008
  and Linux
• Ability to identify conformance/interop failures
• Identify which rule from the specification is
  violated
• Open source for wide audience and availability

32
PIVOTProtocol Independent Verify Operation Tool

• Server-Side Conformance Test

33
PIVOTProtocol Independent Verify Operation Tool

• Client-Side Conformance Test

34
In Summary

• Process virtualization leads to application
  interoperability
• System virtualization leads to stack
  interoperability
• Standards-based virtual machine management
  leadsto platform interoperability

35
(No Transcript)