Spice - Red Hat ENTERPRISE VIRTUALIZATION FOR DESKTOPS Solution Manual

Red Hat Enterprise Virtualization for Desktops

SPice

one of the main reasons that the user experience on virtual desktop systems is inferior to that on a physical
desktop is that today's connection protocols are poorly designed and not custom built for virtual desktop
environments. for example, RDp was designed in the terminal services era when graphics and multimedia
were not a core enterprise computing requirement.
In addition, RDP is inefficient from a CPU consumption perspective regarding a virtual desktop architecture.
RDp requires graphics to be processed inside each and every virtual desktop. processing graphics inside
every virtual machine requires several memory copy operations that are extremely expensive and inefficient
from a cpu perspective. this limits the density of virtual desktops on a given server, and negatively impacts
the economics of the overall solution.
further, RDp does not support another essential component of the user-experience—namely, bi-directional
audio and video. as multimedia becomes a bigger part of the corporate workload (training videos, cEo and
executive broadcasts, product launches, announcements, etc.), traditional connection protocols start falling
short, and require enterprises to compromise on user experience. Enterprise Virtualization for Desktops
overcomes these problems with its revolutionary remote rendering protocol, spicE (simple protocol for
independent computing Environments).
SPice
spicE is an open source, adaptive remote rendering
technology that is custom-built for virtual
environments and designed to provide the same
experience to users as with a traditional physical pc.
SPICE has three components. The first is a driver that
resides inside the guest (virtual desktop). the second
is a virtual graphics device that resides in the host.
the third is the spicE client that resides in the client.
the three components work in tandem, determining
the most efficient place to process the graphics in
order to maximize the user experience and minimize
the system load. if the client is powerful enough,
spicE sends the graphics commands to the client,
and processes them at the client level, significantly
reducing the load on the server. on the other hand, if
the client is not powerful enough, spicE processes
the graphics at the host level (where graphics
processing is a lot less expensive from a cpu
perspective) rather than at the virtual desktop level.
spicE is an adaptive remote rendering technology
that maximizes the user experience and minimizes
the system load.
12 www.redhat.com
Virtual
Desktop
Enterprise
Virtualization
Hypervisor
Thin
client/
browser
Driver
Device
Client