FusionCompute V100R005C00 Virtualization

FusionCompute
Computing
Virtualization
www.huawei.com
Copyright © 2014 Huawei Technologies Co., Ltd. All rights reserved.

Objectives
Upon completion of this course, you will be able to:
 Understand the development background and working

principles of the computing virtualization technology.
 Understand the working principles, deployment, and

configuration of FusionCompute computing virtualization
features.
Copyright © 2014 Huawei Technologies Co., Ltd. All rights reserved. Page 2
Contents
 Introduction to Computing Virtualization
• Development Background
• Working Principles
 Introduction to FusionCompute Computing Virtualization

Features
What Is Virtualization?
Before After
App App App App App App App App App App App App
App App App
Win Linux Win Linux Win Linux Win Linux Win Linux Win Linux
Windows Linux Linux

Virtualization
Resource pool
Virtualization layer Virtualization layer Virtualization layer
Server 1 Server 2 Server 3
 IT resources are isolated.  Resources are virtualized to form

 The OS and hardware are shareable resource pools.
closely coupled.  The OS is decoupled from
hardware, and resources are
allocated from the resource pools.
Origin
 The virtualization technology applied on mainframe computers in 1960s.
 Logic partition was used on midrange computers in 1999.

History
 The x86 platform virtualization technology began to appear in 2000.
 The x86 platform virtualization technology is used on servers in 2001.
 The CPU processes data much faster than that required by software.
 Intel and AMD added virtualization instructions to the CPU.

Impetus  Enterprises need to reduce costs.
 Environment protection becomes increasingly urgent.
 Service pressure consistently increases.
Virtualization can be classified into full virtualization, paravirtualization, and hardware-assisted

virtualization based on the technology architecture.
Benefits
• Hardware utilization is improved.
• Power consumption is reduced.
• IT O&M efficiency is enhanced, and therefore fewer system administrators are required.
• The OS and hardware are decoupled.
Partition Isolation
Multiple VMs can run on a single VMs that run on the same server
physical server. are isolated from one another.
Encapsulation Independent from hardware
All data of a VM is saved in files. A

VM can be moved and replicated by VMs can be migrated between hosts
moving and replicating the files. without any modifications.
Concepts
Guest OS:
Physical server VM
OS installed on a VM
Host OS Guest OS Guest OS Guest machine:
Virtual machine (VM)
VM VM Hypervisor:
(guest machine) (guest machine)
Virtualized software layer/virtual
machine monitor (VMM)
VM monitor
(Hypervisor) Host OS:
OS installed on a physical server

Hardware Hardware
(host machine) (host machine) Host machine:
Physical server
Mainstream Virtualization Types
Hosted Bare-metal Hybrid
OS virtualization
Application virtualization virtualization virtualization
Application Application Application Application Application Application
Application Application Application
OS System System
service template base template base
OS OS management
OS OS OS
Virtualization layer console
Virtual container Virtual storage
Host OS Virtualization layer Host OS Host OS

Management of
virtual hardware
Hosted Virtualization Bare-Metal Virtualization OS Virtualization Hybrid Virtualization

• Not provide redundancy
• Simple and easy to and has high performance
• VMs independent of the OS
implement (compared with hosted
Advantage Simple and easy to implement • Multiple OSs and application
• Very low management virtualization)
programs are supported.
costs • Multiple OSs are
supported.
• Installation and running of
application programs requires
• Poor isolation Underlying hardware must
that the host OS support the Difficult virtualization layer kernel
Disadvantage • Multiple containers share support virtualization
VMs. development
one OS. expansion.
• High management costs and
performance consumption
WMware ESX Server
Vendor VMware Workstation Citrix XenServer Virtuozzo Red Hat KVM
Huawei FusionSphere
Bare-metal virtualization and hybrid virtualization are the virtualization architecture development
trends.
Contents
 Introduction to Virtualization
• Development Background
• Working Principles
CPU virtualization, memory virtualization, and I/O

virtualization
 Introduction to FusionCompute Computing Virtualization

Features
CPU Virtualization
 CPU Shared by VMs
This feature uses the mechanism similar to the traditional OS, that is, timer
interrupts, to trigger the privileged instructions trapped in the VMM. Then, the
system schedules CPU resources based on the scheduling mechanism.
OS
Instruction 2 Instruction 1
VMM
Instruction (1)
Physical CPU
Memory Virtualization
 Memory virtualization centrally manages physical memory of
physical servers and allocates the memory resources to multiple
VMs.
Guest virtual memory
VM1 VM2 VM3 VM4
1
2
3
4
5
Virtual machine monitor (VMM)
5
1
2
3 4
Machine physical memory
I/O Virtualization
VMs reuse limited peripheral
Domain 0 Domain U resources:
 The VMM intercepts the access request
User Control
sent by the guest OS to the device and
mode panel User mode simulates device's actions using
software.
 The front-end drive forwards data to the
Kernel Kernel back-end drive through the VMM's
interface.
Device Back-end Front  The back-end drive processes VM data
drive drive drive
in different time segments and
channels.
Domain U is an ordinary VM that runs on the Xen

VMM hypervisor.
Domain 0, a modified Linux kernel, functions as a

privileged VM running on the Xen hypervisor.
Physical hardware (processor, memory, and I/O Domain 0 can access physical I/O resources and
interwork with other VMs running in the system.
device)
Domain 0 must starts before other domains.
Virtualization Supported by Intel
Hardware (Extensions)
VT-x: Virtualization Technology for IA-32
For example, GPU passthrough
VT-d: Virtualization Technology for Directed I/O
For example, USB emulation

and CD/DVD-ROM mounting
VT-c: Virtualization Technology for Connectivity
For example, NIC passthrough
TXT- Trusted Execution Technology
The hardware kernel and

subsystems are used to prevent
VMs from security threats.
Contents
 Introduction to FusionCompute Computing

Virtualization Features
• Across-CPU VM Live Migration
• VM HA
• CPU QoS
• Memory overcommitment
• Remote CD/DVD-ROM Drive Mounting
• Dynamic Resource Adjustment
• Computing Resource Scheduling
• FusionCompute V100R005C00 New Features
Working Principles of VM Live Migration
 Definition:
 VM live migration is to migrate a running VM to a specified host on the same
site.
 Working principles:
 Transmits VM configurations and device information to the target host.
 Transmits VM memory.
 Synchronizes the initial memory and memory defragmentation upon the
memory migration to the target host.
 Pauses the original VM and transmits the VM status.
 Pauses the VM to be migrated on the original host.
 Transmits latest memory changes to the target host.
 Resumes the target VM.
 Resumes the VM on the target host and stops the VM on the original host.
Across-CPU VM Live Migration
 Background:
 Live migration requires that CPUs of the original and target physical servers have the
same features or are compatible with each other. Otherwise, the live migration fails. The
Across-CPU VM Live Migration feature is introduced to resolve the compatibility issue.
 Based on the Intel Flex Migration technology, the hypervisor intercepts and modifies
CPUID instructions and returns responses. By doing so, the VM cannot sense changes of
CPUs in the same cluster. Therefore, the VM can be migrated to any host within the
cluster.
 Application suggestions:
 In the host list, you can view the IMC mode with the highest level supported by each host.
Users can specify the across-CPU migration mode in the cluster configuration or try from
the highest to the lowest levels. When a mode level passes the verification, this level is
the highest mode level supported by the cluster.
 The cluster can only be set to a mode with a lower level. Therefore, the CPU generation
support capability between nodes cannot be too high during the cluster planning.
Otherwise, the overall performance deteriorates and resources are wasted.
Across-CPU VM Live Migration
Application and Configuration
 In the advanced settings of the
cluster, an option for enabling the
Incompatible Migration Cluster
(IMC) is provided.
 The following five baselines are

supported:
 Merom
 Penryn
 Nehalem
 Westmere
 Sandy Bridge
 Ivy Bridge
Contents

• VM HA
• CPU QoS
• Memory overcommitment
VM HA
 Definition: If a server or a VM fails, the system automatically restarts the
VM on another available server.
• Physical server faults: host power-off, restart, and breakdown
• VM OS faults: Windows blue screen of death (BSOD) and Linux panic
1. A VM or a host is faulty.
2. The management node queries the VM status and detects that the VM is faulty.
3. The management node finds that the faulty VM has the HA function enabled and starts
the VM on an available host based on the stored VM information (specifications and
volume).
4. After receiving the HA request, the host starts the VM on another host based on the VM
specifications and volume information.
5. The host attaches the original VM disks (including user disks) to the destination host.
Automatic Service Recovery
3. Selects a host based on 2. Detects faults at

the scheduling algorithm and a scheduled time.
starts a VM on the node.
5 6
1 2 3 4 5 6
3' 4' 1. A physical

6'
4. Attaches the original server is faulty.

storage volume to this
node and starts the VM.
Contents

• VM HA
• CPU QoS
• Memory Overcommitment
CPU QoS
 The hypervisor schedules CPUs in time-based sharing mode based on
configured CPU QoS parameters. By doing so, the hypervisor controls
the percentage of physical computing resources allocated to each VM,
ensuring service QoS.
 CPU QoS parameters
 Limit (MHz): specifies the maximum CPU resources that can be allocated to a VM. For
example, if a VM has one CPU and this parameter is set to 2000, a maximum of 2000
MHz CPU resources can be allocated to the VM.
 Reserved (MHz): specifies the minimum CPU resources required by a VM. For example, if
a VM has one CPU and this parameter is set to 1000, the VM requires a minimum of 1000
MHz CPU resources.
 Quota: specifies the CPU quota a VM can obtain in resource contention. The quota
indicates the relative priority or importance of a VM. For example, if the CPU quota of a
VM is twice that of another VM, this VM has the priority to consume the CPU resources as
twice as that of the other VM.
CPU QoS Application and Configuration
CPU QoS: upper limit, quota, and reservation
Contents

• VM HA
• CPU QoS
Definition of Memory Overcommitment
The Memory Overcommitment feature allows VMs running on a host to use
more memory than the physical server has available through virtualization
technologies (such as memory ballooning, zero page sharing, and memory
swapping), improving VM density and reducing the cost of a single VM. For
different VMs, such as the management VMs and service VMs, this feature
provides different QoS policies to meet customer's service requirements.
Windows VM (6 GB) Linux VM (6 GB)
Virtualization
Host
Physical memory (8 GB)
Working Principle of Memory
Overcommitment
Memory overcommitment: The memory ballooning, zero page sharing, and memory swapping
technologies employed by memory overcommitment enable a VM to promptly respond to memory
access requests through proper scheduling, reducing the performance overheads of the VM with
memory overcommitment enabled.
VM1 VM2
Idle
Idle
Memory
ballooning
Used
Used
Zero page sharing: Memory ballooning: Memory swapping:

The zero page memory of multiple VMs is The hypervisor uses the memory When a VM is high memory pressure, the
combined in the physical memory to ballooning technology to release memory of memory page is swapped to the disk to
release more physical memory for VMs to idle VMs for VMs with high memory usage release memory.
use. to use, improving VM memory utilization. After the memory page of the VM is
swapped to the disk, the VM performance
The memory ballooning technology has
obviously deteriorates.
small adverse impact on the VM
performance. However, users can sense
the memory reduction.
Memory Overcommitment
Configuration
Memory overcommitment can be configured for a cluster.
 By default, memory overcommitment is disabled for a cluster. You can enable this function for
the cluster.
 If the memory overcommitment function is disabled for a cluster, this function does not take
effect for all hosts in the cluster.
QoS Configuration for Memory
Overcommitment
QoS configuration for VM memory includes the following:
 Reserved (MB): indicates the minimum memory reserved for a VM. If Reserved (MB) is set
to 0, the system reserves the minimum required memory resources for the VM.
 Quota: specifies the CPU quota a VM can obtain in resource contention. The quota
indicates the relative priority or importance of a VM. For example, if the CPU quota of a VM
is twice that of another VM, this VM has the priority to consume the CPU resources as twice
as that of the other VM.
 Size: specifies the maximum memory resource required by a VM.
Relationship Between VM QoS and
Host Memory
Relationship between the VM
memory QoS and host memory
specifications:
 The total memory reserved for VMs
on a host is less than or equal to the
Windows VM (6 GB) Linux VM (6 GB) host memory specifications.
 The total limited memory for VMs on
a host can be greater than the host
Virtualization
memory specifications.
 The quota for VMs on a host is not
Host limited.
Physical memory (10 GB)
Contents

• VM HA
• CPU QoS
Remote CD/DVD-ROM Drive
Mounting
With this feature, the local CD/DVD-ROM drive or ISO image mounted to a server can
be remotely accessed by VMs running on the server over a network.
Working Principle of Remote
CD/DVD-ROM Drive Mounting
CD/DVD-ROM Drive Mounting provides virtual USB CD/DVD drives and allows
local media, such as the CD/DVD-ROM drive and ISO file, to be remotely accessed
over a network.
Contents

• VM HA
• CPU QoS
Working Principle of Dynamic
Resource Adjustment
 Dynamic resource adjustment
 Dynamic resource adjustment allows the number
of resources used by a VM to be changed
without affecting VM services.
 Resources that can be adjusted include
the following:
 Number of CPUs, memory size, number of NICs,
and number of disks
Offline Online Adjustment and Online Adjustment and
Resource Type
Adjustment Effective upon Restart Effective Immediately
Supported in the competition
CPU Supported Supported
tests
Supported in the competition
Memory Supported Supported
tests
Common NIC Supported N/A Supported
iNIC Supported Not supported Not supported
Number of disks Supported N/A Supported
Disk size
(used in virtualization scenarios, Partially supported (for details,
Supported Supported
and the disk size can only be see the following remarks)
increased)
Dynamic Resource Adjustment and
Configuration
You can adjust VM resources on the Hardware tab under VM and Template.
Contents

• VM HA
• CPU QoS
Introduction to Computing Resource
Scheduling
 What is computing resource scheduling?
 Computing resource scheduling automatically adjust VM placement on
computing nodes by leveraging the VM live migration technology.
 What functions does computing resource scheduling provide?
 Load balancing for computing nodes
 Automated power management: The system automatically powers off hosts
when the system has a lot of idle resources and powers on the hosts when
resources in the system are insufficient.
 VMs can be set to mutually exclusive on a host and to be prohibited from
running on certain hosts.
 What policies can be configured for computing resource scheduling?
 Load balancing
 Automated power management
 Advanced scheduling rules
Computing Resource Scheduling:
Load Balancing
 Based on policies configured by users, the system balances CPU usages and
memory usages of nodes that can properly communicate with the management
node and are not isolated through VM live migration.
 The load-balancing is performed at an interval of 50 minutes.
Load Balancing Workflow
Collect CPU and memory usages of each node in the cluster.
(for 10 collection periods)
Is the standard load

deviation of the node for at least
five sampling points and the last
No
sampling point greater than the
initial threshold?
Yes
Collect CPU and memory usages for VMs that can be
scheduled in the cluster.
Calculate the change of standard load deviations for each VM

migrated to other nodes in the cluster.
Does the standard deviation caused

by the migration is less than 0?
No
Yes
Sort out migrations with largest reduction of the standard
deviation and update the standard deviation.
Yes
Is the number of such migrations
greater than 40?
No
Add such migrations to the migration queue. Complete
the scheduling of this cluster and start a next one.
Automated Power Management
Before automated power After the automated power
management is enabled management is enabled
VM 1
VM 2 VM 2
VM 1 VM 3 VM 3
Host 1 Host 2 Host 1 Host 2
Automated Power Management
 The system implements the automated power management for hosts based on
policies configured by users.
 When the loads on hosts in a cluster are light, the system automatically migrates
all VMs from the hosts and powers off the hosts. When the loads on hosts in a
cluster are heavy, the system automatically powers on the some hosts.
 Automated power management is performed at an interval of 10 minutes.
Computing Resource Scheduling: Automated
Power Management Workflow
Start
Collect CPU and memory usages of each node in

Check whether the sampling point is overloaded,
the cluster.
light, or normal due to CPU or memory.
(for 10 collection periods)
Calculate the light-loaded score of CPU and Is the node heavy-loaded?

memory usages for each sampling point.
Yes
No
Calculate the heavy-loaded score of CPU and Is the node light-loaded? Power on the host
memory usages for each sampling point. No and select an
appropriate node to
Yes migrate VMs.
Select an appropriate node, migrate VMs to the

node, and power off the original node.
End
Advanced Scheduling Rules
 What are advanced scheduling rules?

 After computing resource scheduling is enabled, the system schedules VMs
based on the configured advanced scheduling rules.
 The scheduling interval is 50 minutes.
 What are the advanced scheduling rules?
 Mutually exclusive: A group of VMs, each two of which must run on different
hosts.
 VMs to hosts: A group of VMs that must run on a specified group of hosts
 Relationship between advanced scheduling rules and load-balancing as
well as automated power management, respectively
 The priority of advanced scheduling rules is higher than that of load balancing
and lower than that of the automated power management.
Computing Resource Scheduling: Advanced
Scheduling Rule Configuration — Mutually
Exclusive
 Select a cluster, choose Set Computing Resource Scheduling > Rule
Management, click Add, and choose Keep VMs mutually exclusive for Type.
The following dialog box is displayed.
Advanced Scheduling Rules
Configuration — VMs to Hosts
 Preparations: A host group and a VM group have been created.
 Procedure: Select a cluster, choose Set Computing Resource Scheduling >
Rule Management, click Add, and choose VMs to hosts for Type. The following
dialog box is displayed.
Example of Advanced Scheduling Rules
Effect of the combined application of load balancing and energy

saving policies
VM 1
VM 2 VM 3 VM 1 VM 8
VM 4 VM 5 VM 6 VM 7 VM 8
Host 1 Host 2 Host 3
Contents

• VM HA
• CPU QoS
VRM-Independent HA
 Function description
 A master node is elected in a cluster to monitor
status of hosts in the cluster and maintains the VM
lists. If a host fails, the master node restarts all VMs
running on the host on other hosts.
 Users can choose to enable or disable the VRM-
independent HA function. If this function is disabled,
the VRM node implements the HA function. If this
function is enabled, a master node is elected to
implement the HA function.
 Restriction
 The VRM-independent HA supports only virtualized
storage because VIMS is required for storing the
storage heartbeats and configuration data.
VRM-Independent HA
 VRM module function
 Distributes configuration data, such as host configuration data, VM
compatibility information, and heartbeat storage data.
 Receives the topology reported by HAD.
 Coordinates and maintains network rules saved on data stores for VM
startup.
 HAD module function VNA HAD VNA HAD VNA HAD

Master node Slave node Slave node
 Elects the master node based on node configuration.
 The master node monitors the management and storage heartbeats of all
slave nodes to check status of all slave nodes.
 If the master node detects that a slave node is faulty, the master node
restarts all affected VMs on other nodes.
VRM
 Identifies the current status of nodes, such as network partitioned or
isolated and resumes the hosts after the network becomes normal. If the
master node is faulty, elects another node as the master node.
 VNA module function

 Saves VM configuration data and network configuration information on
shared storage.
 Starts VMs on nodes using the configuration data.
 Allows the HAD module to query the running VM list.
Enhanced DRS and DPM Functions
 In FusionCompute V100R005C00, the
DRS and DPM scheduling algorithms
are optimized to improve the
scheduling efficiency and reduce the
number of scheduling operations
required.
 The migration and power

management thresholds include
conservative, slightly conservative,
medium, slightly radical, and radical.
 FusionCompute V100R005C00 adds

support for DRS scheduling baseline
configuration.
OVF Template
 Open Virtualization Format (OVF) is a packaging standard introduced by Distributed Management Task
Force (DMTF) for VM and virtual application (vApp) publishing and deployment. The OVF specification
defines two specific ways of grouping files: OVF package and OVA package (OVF in the TAR format). A
standard OVF package includes:
• One OVF descriptor with extension .ovf. It is an XML file that defines the components of a VM or vApp
and the features and resource requirements of each component.
• Zero or one OVF manifest with extension .mf
• Zero or one OVF certificate with extension .cert
• Zero or more disk image files with extension .vmdk , .vhd, or others
• Zero or more additional resource files with extension .iso
 A Huawei OVF template encapsulates only one VM and supports both the OVF and OVA packages. A
Huawei OVF package includes:
• One OVF descriptor with extension .ovf
• One or more disk image files with extension .vhd. The file format is the compression format used by
Huawei for stream transmission.
Enhanced Template Importing and
Exporting Functions
 FusionCompute V100R005C00
introduces support for the HTTP and
HTTPS protocols during OVF
template importing and exporting.
 Users can directly browse and select

a local directory during template
importing and exporting. They do not
need to share the template and
configure the username and password
for accessing the template.
Antivirus Virtualization
• Compared with the traditional antivirus VM user
Administrator
function, the antivirus virtualization function Host
Secure User VM (SVM) Secure Guest VM (GVM)

requires no antivirus software to be installed Antivirus application Antivirus software
User mode
management
Antivirus Virus signature Kernel mode Antivirus light agent
on user VMs and does not consume Antivirus application
deployment
engine database
Centralized
computing resources on user VMs, leaving configuration Security VM API
Scan Security service program

Security API module
sufficient storage and computing resources Real-time
monitoring
On-demand scan File traversing
REST File processing

Processing Cache/Filter
for user VMs. interface File monitoring driver
cache/filter
PV driver Security agent Security agent

VRM User mode Shared memory driver PV driver
access interface Shared memory
UVP memory
driver access
sharing driver
• Compared with the online antivirus function, Kernel mode
UVP memory sharing driver interface
the antivirus virtualization function provides UVP
Ivshm device emulation Ivshm server

higher performance because the system
uses host physical memory swapping to Modules: Interfaces:
Light red: New modules provided by antivirus vendors Blue: Interfaces for interconnection between Huawei and antivirus vendor
Yellow: New or changed modules provided by Huawei modules
scan, monitor, and remove viruses, and Blue-gray: Huawei legacy modules Pink: Interfaces for interconnection between internal modules provided by
antivirus vendors
Green: Interfaces for interconnection between Huawei internal modules
does not require network resources on user

VMs.
VNC Login Optimization
• FusionCompute V100R005C00 introduces support for
the HTML5-based noVNC function. Compared TightVNC
supported by earlier versions, noVNC offers the following
benefits:
 No JRE plug-in is required for the browser.
 More smooth operations using a mouse.
 The system responds quickly and smoothly
to operations performed using the mouse
and keyboard.
• HTML5 has requirements on browser versions. The
browser versions highlighted in green in the figure
located in the upper-right corner are those that support
HTML5.
• After a user clicks VNC Login, the system displays a
dialog box for users to select a VNC login mode if it
detects that noVNC is supported. If the system does not
support noVNC, the system enables the user to directly
log in to the VM using TightVNC.
Thank you
www.huawei.com

FusionCompute V100R005C00 Virtualization

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

FusionCompute V100R005C00 Virtualization

Загружено:

Авторское право:

Доступные форматы

FusionCompute

Copyright © 2014 Huawei Technologies Co., Ltd. All rights reserved.

 Understand the development background and working

 Understand the working principles, deployment, and

 Introduction to FusionCompute Computing Virtualization

Windows Linux Linux

Server 1 Server 2 Server 3

 IT resources are isolated.  Resources are virtualized to form

 Logic partition was used on midrange computers in 1999.

 The x86 platform virtualization technology is used on servers in 2001.

 Intel and AMD added virtualization instructions to the CPU.

 Environment protection becomes increasingly urgent.

 Service pressure consistently increases.

Virtualization can be classified into full virtualization, paravirtualization, and hardware-assisted

Encapsulation Independent from hardware

All data of a VM is saved in files. A

Host OS Guest OS Guest OS Guest machine:

Virtual machine (VM)

OS installed on a physical server

Host OS Virtualization layer Host OS Host OS

Hosted Virtualization Bare-Metal Virtualization OS Virtualization Hybrid Virtualization

CPU virtualization, memory virtualization, and I/O

 Introduction to FusionCompute Computing Virtualization

Domain U is an ordinary VM that runs on the Xen

Domain 0, a modified Linux kernel, functions as a

For example, GPU passthrough

VT-d: Virtualization Technology for Directed I/O

For example, USB emulation

VT-c: Virtualization Technology for Connectivity

For example, NIC passthrough

TXT- Trusted Execution Technology

The hardware kernel and

 Introduction to FusionCompute Computing

 The following five baselines are

 Introduction to FusionCompute Computing

• VM OS faults: Windows blue screen of death (BSOD) and Linux panic

3. Selects a host based on 2. Detects faults at

3' 4' 1. A physical

4. Attaches the original server is faulty.

 Introduction to FusionCompute Computing

CPU QoS: upper limit, quota, and reservation

 Introduction to FusionCompute Computing

Windows VM (6 GB) Linux VM (6 GB)

Zero page sharing: Memory ballooning: Memory swapping:

Physical memory (10 GB)

 Introduction to FusionCompute Computing

 Introduction to FusionCompute Computing

 Introduction to FusionCompute Computing

Is the standard load

Calculate the change of standard load deviations for each VM

Does the standard deviation caused

Host 1 Host 2 Host 1 Host 2

Collect CPU and memory usages of each node in

Calculate the light-loaded score of CPU and Is the node heavy-loaded?

Select an appropriate node, migrate VMs to the

 What are advanced scheduling rules?

Effect of the combined application of load balancing and energy

Host 1 Host 2 Host 3

 Introduction to FusionCompute Computing

 HAD module function VNA HAD VNA HAD VNA HAD

 VNA module function

 The migration and power

 FusionCompute V100R005C00 adds