convergence 08 virtualization trends, challenges and solutions naresh sehgal, ph.d., mba lead sw...
TRANSCRIPT
Convergence 08
Virtualization Trends, Virtualization Trends, Challenges and SolutionsChallenges and Solutions
Naresh Sehgal, Ph.D., MBANaresh Sehgal, Ph.D., MBALead SW ArchitectLead SW Architect
Enterprise Platforms and Services DivisionEnterprise Platforms and Services DivisionIntel Corp, BangaloreIntel Corp, Bangalore
Email: [email protected]: [email protected]
Convergence 08
Robert X. Cringely on Computers…Robert X. Cringely on Computers…
"If the automobile had followed the same "If the automobile had followed the same development cycle as the computer… development cycle as the computer…
A Rolls-Royce would today cost $100, A Rolls-Royce would today cost $100,
get a million miles per gallon, and get a million miles per gallon, and
explode once a year, killing everyone explode once a year, killing everyone inside.” inside.”
Convergence 08
Physical Host Hardware
Hardware Virtual Machines (VMs)Hardware Virtual Machines (VMs)
GFX
MemoryProcessors
Keyboard / Mouse
Graphics
StorageNetwork
Operating System
...App App App
Without VMs: Single OS owns all hardware resources
VM1VM0
Guest OS0
App AppApp ...
... Guest OS1
App ...
VM Monitor (VMM)
Physical Host Hardware
With VMs: Multiple OSes share hardware resources
A newA newlayer oflayer of
software...software...
AppApp
Virtualization enables multiple operating systems to run on the same platform
Virtualization enables multiple operating systems to run on the same platform
Convergence 08
How long has virtualization been around?How long has virtualization been around?
1.1. Recent development: ~5 yearsRecent development: ~5 years
2.2. A while: 10 yearsA while: 10 years
3.3. Older than Microsoft: 30 yearsOlder than Microsoft: 30 years
4.4. A lot longer…..>40 yearsA lot longer…..>40 years
Would you believe ~45 - 50 years?Would you believe ~45 - 50 years?
Convergence 08
IBM & MIT: IBM & MIT: Compatible Compatible Time Time Sharing SystemSharing System
Strachey: Strachey: Time Sharing in Large Fast Time Sharing in Large Fast ComputersComputers
IBM: M44/44X IBM: M44/44X ProjectProject
MIT: Project MIT: Project MACMAC
Goldberg: Goldberg: Survey of Virtual Machines Survey of Virtual Machines ResearchResearch
Connectix is Connectix is foundedfounded
VMWare VMWare is is foundedfounded
Microsoft acquires Microsoft acquires ConnectixConnectix
Open source Open source Xen Xen is releasedis released
1950 1960 1970 1980 1990 2000 Today
Intel introducesIntel introducesIntel Virtualization Intel Virtualization
TechnologyTechnology
VirtualizationVirtualization
Convergence 08
Virtualization ChallengesVirtualization ChallengesComplexityComplexity
CPU virtualization requires binary translation or CPU virtualization requires binary translation or paravirtualizationparavirtualizationMust emulate I/O devices in softwareMust emulate I/O devices in software
FunctionalityFunctionalityParavirtualization may limit supported guest OSesParavirtualization may limit supported guest OSesGuest OSes “see” only simulated platform and I/O devicesGuest OSes “see” only simulated platform and I/O devices
Reliability and ProtectionReliability and ProtectionI/O device drivers run as part of host OS or hypervisorI/O device drivers run as part of host OS or hypervisorNo protection from errant DMA that corrupts memoryNo protection from errant DMA that corrupts memory
PerformancePerformanceOverheads of address translation in softwareOverheads of address translation in softwareExtra memory required (e.g., translated code, shadow tables)Extra memory required (e.g., translated code, shadow tables)
Convergence 08
With VTWith VTVM0
WinXP
Apps
VMn
Linux
Apps
CPUn
Processorswith
VT-x (or VT-i)
VT-x
CPU0
Processor VirtualizationProcessor Virtualization
Without VTWithout VT
VMM
CPUn
Processors(Standard
IA-32 or IPF)CPU0
VM0
Legacy OS
Apps
1 RingDeprivileging
Ring 3
Ring 1
Ring 0Binary Translation
Cache
Binary Translator
2 BinaryTranslation
Ring 3
Ring 0
VMXRootMode H/W VM Control
Structure (VMCS)
VMM
Memory and I/OVirtualization
Ring
Compression
VMEntry
VMExit
Guest OSes run at intended rings
VMCSConfiguration
3Para-Virtualization
VMn
Modified OS
Apps
Convergence 08
IntelIntel®® Virtualization Technology (VT) Virtualization Technology (VT)
IntelIntel®® VT VT
First to market with native virtualization support
Broadest HW and SW ecosystem support
CoreTM 2 Microarchitecture based systems
Significant increase in performance and improved VT performance overall segments
Mobile - Intel® Core™2 Duo Mobile Processor for Intel® Centrino® Duo Mobile Technology
Desktop - Intel® Core™2 Duo Desktop Processor E6000 sequence -
Server Dual-Core Intel® Xeon® Processor 5100 series
Get More Done On Every ServerGet More Capabilities On Client
Processors with Intel® Virtualization Technology
Virtual Machine Monitor
..…OSOS
AppApp
OSOS
AppApp
OSOS
AppApp
OSOS
AppApp
and others …
11stst VT base SW VT base SW SolutionsSolutions
Convergence 08
Today’s Uses – Servers Today’s Uses – Servers Virtualization addresses today’s IT concernsVirtualization addresses today’s IT concerns
10:1 in many cases10:1 in many cases Enables rapid deploymentEnables rapid deployment
Server ConsolidationServer Consolidation
HWnHWn
……
HW0HW0
VM1VM1 VMnVMn
OSOS
AppApp
OSOS
AppApp ……
HWHW
VM1VM1 VMnVMn
VMMVMM
OSOS
AppApp
OSOS
AppApp
Test and DevelopmentTest and DevelopmentVM1VM1
HWHW
VMMVMM
OSOS
AppApp
OSOS
AppApp
Virtualization increases server utilization, Virtualization increases server utilization, simplifies legacy software migrationsimplifies legacy software migration
Convergence 08
Emerging Server Usage ModelsEmerging Server Usage ModelsTrue “Lights Out” DatacenterTrue “Lights Out” Datacenter
HWHW
VMMVMM
HW HW
VMMVMM
Balancing utilization Balancing utilization with head room with head room
Dynamic Load BalancingDynamic Load BalancingVM1aVM1a
OSOS
AppApp11
VM2aVM2a
OSOS
AppApp22
VM1bVM1b
OSOS
AppApp33
VM2bVM2b
OSOS
AppApp44
Disaster RecoveryDisaster RecoveryVM1VM1
HWHW
VMMVMM
OSOS
AppApp ……
VMnVMn
OSOS
AppApp
HWHW
VM1VM1
VMMVMM
OSOS
AppApp ……
VMnVMn
OSOS
AppApp
IntelIntel®® Virtualization Technology will play an Virtualization Technology will play anintegral role on the next generation of VMMsintegral role on the next generation of VMMs
Upholding high-levels Upholding high-levels of business continuityof business continuity
CPU Usage30%
CPU Usage90%
CPU Usage62%
CPU Usage63%
Convergence 08
Emerging Business Usage ModelsEmerging Business Usage Models
Intel Platform SoftwareIntel Platform Software
ProfessionalProfessionalBusinessBusinessPlatformPlatform
ProactiveProactiveSecuritySecurity
Energy Efficient Energy Efficient PerformancePerformance
Built-in Management
Convergence 08
vProvProTMTM Key Features Key Features
RemotelyRemotely Manageability - Manageability - Repair down systemsRepair down systems
Securely update systemsSecurely update systemsAudit powered-down PCsAudit powered-down PCs
Prevents malicious packets Prevents malicious packets from entering the OSfrom entering the OS
Supported by over 45 OEMs, ISVs, & IT Outsourcers
HP OpenView
More details in the IDF vProTM tracks
Convergence 08
IntelIntel®® Virtualization and Virtualization and IntelIntel®® vPro™ technology vPro™ technology
Uses IntelUses Intel®® VT for creating a separate VT for creating a separate independent hardware-based independent hardware-based environment inside of the PC environment inside of the PC
Service PartitionService Partition – –
Allowing IT administrators to create Allowing IT administrators to create a dedicated and tamper resistant a dedicated and tamper resistant service environment or partition service environment or partition where tasks can run independently where tasks can run independently and isolated from the main and isolated from the main operating system as well as from operating system as well as from the end userthe end user
User partition -User partition -
OS and applicationOS and application
.
Intel® architecture PlatformIntel® architecture Platform
Lightweight VMM (LWVMM)Lightweight VMM (LWVMM)
User Partition Service Partition
VM0 VM1
User OS (Win2K, XP)
App0 App1 AppnService OS
(WinCE or Linux)
“Firewall”Application
“Management” Application
Intel, the Intel logo, and Intel architecture are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries.
VTAMT
Help desk or console access even when user partition is “down”
Stack owned and managed by IT dept… protected from users
Convergence 08
Intel® Virtualization Technology Intel® Virtualization Technology EvolutionEvolution
VMMSoftwareEvolution
PastNo Hardware
SupportVMM software evolution over time with hardware support
Software-only VMMs• Binary translation• Paravirtualization
Simpler and more Secure VMM through foundation of virtualizable ISAs
Vector 3:I/O Focus
Standards for IO-device sharing:• Multi-context I/O devices• Endpoint device translation caching• Under definition in the PCI-SIG* IOV
Vector 1:Processor Focus
Vector 2:Platform Focus
Establish foundation for virtualization in the IA-32 and Itanium architectures…
VT-x
VT-i
… followed by on-going evolution of support:• Micro-architectural (e.g., lower VM switch times)• Architectural (e.g., extended page tables, EPT)
Hardware support for IO-device virtualization:• Device DMA remapping• Direct assignment of I/O devices to VMs• Device-independent control over DMA
VT-d
Increasingly better CPU and I/O virtualization Performance and Functionality as I/O devices and VMMs exploit infrastructure provided by VT-x, VT-i, VT-d
*Other names and brands may be claimed as the property of others
Today
PCI-SIG
Convergence 08
Options for I/O VirtualizationOptions for I/O Virtualization
Pro: High Pro: High PerformancePerformance
Pro: I/O Device Pro: I/O Device SharingSharing
Pro: VM MigrationPro: VM Migration
Con: Large Con: Large HypervisorHypervisor
Pro: Higher Pro: Higher PerformancePerformance
Pro: Rich Device Pro: Rich Device FeaturesFeatures
Con: Limited SharingCon: Limited Sharing
Con: VM Migration Con: VM Migration LimitsLimits
Hypervisor
SharedDevices
I/O Services
Device Drivers
VM0
Guest OSand Apps
VMn
Guest OSand Apps
Hypervisor Model
AssignedDevices
Hypervisor
VM0
Guest OSand Apps
DeviceDrivers
VMn
Guest OSand Apps
DeviceDrivers
Pass-through Model
Pro: Higher SecurityPro: Higher Security
Pro: I/O Device Pro: I/O Device SharingSharing
Pro: VM MigrationPro: VM Migration
Con: Lower Con: Lower PerformancePerformance
SharedDevices
I/O Services
Hypervisor
Device Drivers
Service VMs
VMn
VM0
Guest OSand Apps
Guest VMs
Service VM Model
VT Goal: Support all 3 ModelsVT Goal: Support all 3 Models
Convergence 08
VT-d OverviewVT-d Overview
VT-d provides infrastructure for I/O virtualizationVT-d provides infrastructure for I/O virtualizationDefines architecture for DMA and interrupt remappingDefines architecture for DMA and interrupt remapping
Common architecture across IA platformsCommon architecture across IA platforms
Will be supported broadly across IntelWill be supported broadly across Intel®® chipsets chipsets
CPU CPU
DRAM
South Bridge
System Bus
PCI Express
PCI, LPC, Legacy devices, …
IntegratedDevices
North Bridge
VT-d
PCIe* Root Ports
*Other names and brands may be claimed as the property of others
Convergence 08
How VTd works?How VTd works?
Each VM thinks it is Each VM thinks it is 0 address based0 address based
GPA (Guest Physical GPA (Guest Physical Address)Address)
But mapped to a But mapped to a different address in different address in the system memorythe system memory
HPA (Host Physical HPA (Host Physical Address)Address)
VTd does the VTd does the address mapping address mapping between GPA and between GPA and HPAHPA
Catches any DMA Catches any DMA attempt to cross VM attempt to cross VM memory boundarymemory boundary
VM2
VM0
VM1
0
100
0
100
0
100
10 260
30050
0
600
1000
100
200
250
350
700
Convergence 08
Memory-resident Partitioning & Translation Structures
Device Assignment Structures
Address Translation Structures
Device D1
Device D2
Address Translation Structures
DMA Remapping: Hardware Overview
DMA Requests
Device ID Virtual Address Length
Memory Access with Host Physical Address
DMA RemappingEngine
Translation Cache
Context Cache
Fault Generation
…Bus 255
Bus 0
Bus N
Dev 31, Func 7
Dev P, Func 1
Dev 0, Func 0
Dev P, Func 2
4KBPage
Frame
4KB Page Tables
Convergence 08
VT-d Applied to Hypervisor Model
Pro: Higher PerformancePro: I/O Device SharingPro: VM MigrationCon: Larger Hypervisor
Hypervisor
SharedDevices
I/O Services
Device Drivers
VM0
Guest OSand Apps
VMn
Guest OSand Apps
Hypervisor ModelHypervisor ModelImproved Reliability and ProtectionHypervisor programs remap tables
Errant DMA is detected by hardware and reported to hypervisor / device driver
Bounce Buffer SupportLimited DMA addressability in I/O devices limits access to high memory
“Bounce buffer” is a software technique to copy I/O buffers into high memory
VT-d eliminates need for “bounce buffer”
Above equally useful for standard OSesVT-d does not require a VMM to function
Convergence 08
VT-d Applied to Service VM Model
Pro: High SecurityPro: I/O Device SharingPro: VM MigrationCon: Lower Performance
SharedDevices
I/O Services
Hypervisor
Device Drivers
Service VMs
VMn
VM0
Guest OSand Apps
Guest VMs
Service VM ModelService VM ModelDevice Driver Deprivileging
Device drivers run above hypervisor as part of a “Service OS”
Guest device drivers program devices in DMA-virtual address space
Service VMForwards DMA API calls to hypervisor
Hypervisor sets up DMA-virtual to host-physical translation
Further Improvements in ProtectionGuest device driver cannot compromise hypervisor code or data
Convergence 08
VT-d Applied to Pass-through Model
Pro: Highest PerformancePro: Smaller HypervisorPro: Device-assisted sharingCon: VM Migration Limits
AssignedDevices
Hypervisor
VM0
Guest OSand Apps
DeviceDrivers
VMn
Guest OSand Apps
DeviceDrivers
Pass-through ModelPass-through ModelDirect Device Assignment to Guest OS
Guest OS directly programs physical device
For legacy guests, hypervisor sets up guest- to host-physical DMA mapping
For remapping aware guests, hypervisor involved in map/unmap of DMA buffers
PCI-SIG I/O Virtualization Working GroupActivity towards standardizing natively sharable I/O devices
IOV devices provide virtual interfaces, each independently assignable to VMs
Convergence 08
DMA Remapping: IOTLB Scaling
Address Translation Services (ATS) extensions to PCIe* enable IOTLB scaling
ATS endpoint implements ‘Device IOTLBs’
Device-IOTLBs can be used to improve performanceE.g., Cache only static translations (e.g. command buffers)
Pre-fetch translations to reduce latency
Minimizes dependency on root-complex caching
Support device-specific demand I/O paging*Other names and brands may be claimed as the property of others
Convergence 08
Root Complex
Tra
nsla
tion
Req
uest
Endpoint Device
Remap Hardware IOTLB
Address Translation Services (ATS)
Device IOTLB
Translate Address
Tra
nsla
ted
DM
A R
eque
st
DMA using Translated Address
Tra
nsla
tion
Res
pons
e
ATS Translation FlowsDevice issues Translation Requests to root-complex
Root-complex provides Translation Response
Device caches translation locally in ‘Device IOTLB’
Devices can issue DMA with translated address
Translated DMA from enabled devices bypass address translation
*Other names and brands may be claimed as the property of others
VT-d supports per-device control of ATSVT-d supports per-device control of ATS
Convergence 08
Invalidation Architecture
Invalidation enforces consistency of cachesRequired when software updates translation structures
Invalidation primitivesGlobal, domain-selective, and page-range invalidationsSupport for Device-IOTLB invalidation (through ATS)
Invalidation software interfacesSynchronous interface through MMIO registersQueued interface through invalidation queue
Convergence 08
Inva
lidat
ion
Res
pons
e
ATS Invalidations
Endpoint Device
Root Complex
Remap Hardware IOTLB
Device IOTLB
Inva
lidat
ion
Req
uest
ATS Invalidation FlowRoot-complex issues invalidation request to device
Device invalidates specified mappings from Device IOTLB
Device issues Invalidation response
Invalidation detailsInvalidation request contains unique Invalidation Tag
Invalidation Responses may be coalesced*Other names and brands may be claimed as the property of others
Invalidate Device-IOTLB
Convergence 08
Mapping to VMM Software ChallengesMapping to VMM Software Challenges
CPUn
VM0
MemoryProcessors I/O Devices
Processor Virtualization Memory Virtualization I/O Device Virtualization
Higher-level VMM Functions:Resource Discovery / Provisioning / Scheduling / User Interface
CPU0
Storage
Network
…VirtualMachines
(VMs)
VMM(a.k.a.,
hypervisor)
PhysicalPlatform
Resources
VM1
OS
Apps
VM2 VMn
OS
Apps
BinaryTranslation
RingDeprivileging
Page-tableShadowing
I/O DMARemapping
InterruptRemapping
I/O DeviceEmulation
VM0 VM2
OS
Apps
OS
Apps
CPUn
CPU0
Virtual CPUConfiguration
EPTConfiguration
DMA and Interrupt Remapping Configuration
I/O DeviceSharing
VT-x
VT-x2 VMDq
VT-d2
PCI SIGVT-d
Convergence 08
Example 6: Virtualization overhead on IntelExample 6: Virtualization overhead on Intel®® experimental client experimental client
VMM* (vs. Native OS)VMM* (vs. Native OS)
85.69%
97.88%93.90%
83.44%
99.67%
0.00%
10.00%
20.00%
30.00%
40.00%
50.00%
60.00%
70.00%
80.00%
90.00%
100.00%
System CPU Memory Graphic HDD
PCMark Performance Indicator
• Relatively low Virtualization overheads for client benchmark•Targeting <10% overhead with improved SW techniques
• Further VMM SW optimization and Next generation VT features to reduce virtualization overheads
* Pre beta version Source: Intel Corporation Projections and technical specifications are based on internal analysis and
subject to change
Convergence 08
Summary: A better IA platformSummary: A better IA platform
Performance HeadroomPerformance Headroom
Intel® Xeon® processors have Intel® Xeon® processors have key performance featureskey performance features for for virtualization: dual-core, hyper-threading, I/O, memory, and larger virtualization: dual-core, hyper-threading, I/O, memory, and larger caches caches
First to Market & Massive Ecosystem Support:First to Market & Massive Ecosystem Support:
Better Platform Reliability:Better Platform Reliability:
Critical for more applications on the same serverCritical for more applications on the same server
More reliability features More reliability features
Proven Platform Architecture - almost 40X more Proven Platform Architecture - almost 40X more IA based servers than AMD based since 1996IA based servers than AMD based since 199611
Whitepaper on Virtualization benefits: http://www.intel.com/business/bss/products/server/virtualization_wp.pdf
“Choose the right basket”
RobustRobust: First x86 hardware assisted virtualization technology (Intel VT): First x86 hardware assisted virtualization technology (Intel VT)
InnovationInnovation: common specification = enhanced virtualization on x86 and will : common specification = enhanced virtualization on x86 and will set the standard set the standard
FlexibilityFlexibility: Leverage Intel® Xeon® processor-based servers widely deployed : Leverage Intel® Xeon® processor-based servers widely deployed infrastructure for advanced failover and dynamic load balancinginfrastructure for advanced failover and dynamic load balancing
ChoiceChoice: Broadest virtualization software support in the industry : Broadest virtualization software support in the industry
1 – source: Q4’05 IDC server Tracker, 1996-2005 total system shipped
Convergence 08
Backup
Q & A
Convergence 08
Example 1: SysBench Running Example 1: SysBench Running with VMware*’s ESX Server*with VMware*’s ESX Server*
SysBench normalized results graph
0.00
0.20
0.40
0.60
0.80
1.00
1.20
1.40
1.60
1.80
4 VM 2 VM 1 VM
Number of virtual machines
No
rma
liz
ed
sc
ore
s
Dual-Core AMD Opteron285-based server
Dual-Core Intel Xeonprocessor 5160-basedserver
Figure 1: Normalized SysBench results for the two test servers in the one, two, and four virtual machine environments. Higher numbers are better.
*Source: Principled Technologies (PT) performance report http://www.principledtechnologies.com/clients/reports/Intel/VMSysBench0706.pdf
Significant perfo
rmance
lead over competition
System configuration in backup foils
Convergence 08
Example 2: SPECjbb Running Example 2: SPECjbb Running with VMware*’s ESX Server**with VMware*’s ESX Server**
Figure 2: Normalized SPECjbb2005 results for the two test servers in the one, two, and four virtual machine environments. Higher numbers are better.
SPECjbb2005 normalized results graph
0.00
0.20
0.40
0.60
0.80
1.00
1.20
1.40
1.60
1.80
4 VM 2 VM 1 VM
Number of virtual machines
No
rma
liz
ed
sc
ore
s
Dual-Core AMD Opteron285-based server
Dual-Core Intel Xeonprocessor 5160-basedserver
* *Other names and brands may be claimed as the property of others
**Source: Principled Technologies (PT) performance report
Comparing Dual-Core AMD Opteron 285 with Dual-Core Intel®® Xeon ®® Processor 5160
perform
ance le
ad over c
ompetition
Convergence 08
Example 3:Example 3:Microsoft* Virtual Server*Microsoft* Virtual Server*
Source: Intel Corporation Projections and technical specifications are based on internal analysis and subject to change
VMM – Microsoft* Virtual Server* 2005 R2 SP1 Java JFT workload
Guest OS - Windows 2003* Enterprise Edition R2 (32 bit)
Benchmark - JVM BEA WebLogic x`® (build R26.0.0-188-52875-1.5.0_04-2005110-0920-linux-x86_64)
Systems –
HP DL385 2 AMD Opteron 2.6GHz 2x1MBIntel®® Dual-Core Intel ®® Xeon®® Processor 3.0G SuperMicro SDP 16x1GB
*Other names and brands may be claimed as property of others. System Configuration details in backup. Performance tests and ratings are measured using specific computer systems and/or components and reflect the approximate performance of Intel products as measured by those tests. Any difference in system hardware or software design or configuration may affect actual performance. Buyers should consult other sources of information to evaluate the performance of systems or components they are considering purchasing. For more information on performance tests and on the performance of Intel products, visit http://www.intel.com/performance/resources/limits.htm or call (U.S.) 1-800-628-8686 or 1-916-356-3104.
1
1.53
0
0.2
0.4
0.6
0.8
1
1.2
1.4
1.6
HP DL385 with 2*AMDOpteron 2.6GHz
SuperMicro SDP with 2* Dual-Core Intel ®
Xeon Processor3.0GHz
Java Performance with 4 VMs - JVM BEA WebLogic JRockit® on Microsoft* Virtual Server
Up to 53%
gain
Convergence 08
Example 4: Example 4: Energy Efficient PerformanceEnergy Efficient Performance
IntelIntel® Core CoreTMTM 2 Duo based system provide Energy Efficient Performance (EEP ) Leadership in virtualized environment
Source: Intel Corporation Projections and technical specifications are based on internal analysis and subject to change
1
1.6
0
0.2
0.4
0.6
0.8
1
1.2
1.4
1.6
HP DL385 with 2*AMDOpteron 2.6GHz
SuperMicro SDP with 2*Dual-Core Intel ® Xeon
Processor 3.0GHz
Performance/Watt - - JVM BEA WebLogic JRockit® on Microsoft* Virtual Server
Convergence 08
Example 5: MS VS SpecJBB 2005*Example 5: MS VS SpecJBB 2005*
IntelIntel® ®
XEONXEON®® SW Virtualized guest performance is 1.66x of Opteron SW Virtualized guest performance is 1.66x of Opteron
Host OSHost OS Microsoft* Server 2003 X64 Microsoft* Server 2003 X64 Enterprise Edition SP1 RTM Enterprise Edition SP1 RTM
VirtualizationVirtualization
Microsoft* Virtual Server* R2 Beta Microsoft* Virtual Server* R2 Beta SP1 ver. 1.1.512.0 EESP1 ver. 1.1.512.0 EE
Drop B1036 vmm.sysDrop B1036 vmm.sys
Microsoft* Virtual Machine Microsoft* Virtual Machine Windows* Guest Editions ver. Windows* Guest Editions ver. 13.70513.705
Guest OSGuest OS RedHat V9 2.4.20-8 kernel (32-bit)RedHat V9 2.4.20-8 kernel (32-bit)
WorkloadWorkload SpecJBB 2005SpecJBB 2005
Source: Intel Corporation Projections and technical specifications are based on internal analysis and subject to change
8408
13938
16404
0
2000
4000
6000
8000
10000
12000
14000
16000
18000
Bops
Opteron 1P RH32Guest (SW)
Intel ® XEON 5100series (SW)
Intel ® XEON 5100series (VT)
SpecJBB 2005 Microsoft VS R2 SP1 (RH32 Guests)
1.66X
1.18X
1.95X
Intel® XEON® VT performance is 1.18x of Software (no VT) Intel® XEON®
Intel® XEON® VT performance is 1.95x of Opteron SW (no Pacifica)