Virtualization Notes - GTC CPT 257

Client-Side Virtualization (1 of 2)

  • One physical machine provides virtual environments for applications using:
    • Application virtualization: an application is made available to users without having to install the application on the user’s computer.
    • Desktop virtualization: also called client-side virtualization.
    • One computer provides multiple desktops for users.
    • Each virtual desktop is contained in its own virtual machine.

Client-Side Virtualization (2 of 2)

  • Example: Two virtual machines running on a Windows 10 host, each with its own virtual hardware and OS (Windows 10 and Ubuntu Linux).
  • Figure 10-1 referenced.

Type 1 and Type 2 Hypervisors (1 of 2)

  • Hypervisor software can be a Type 1 or Type 2. Main difference is whether the host computer has its own OS.
  • Hypervisors:
    • Type 1 – installs on a computer before an OS (bare-metal hypervisor); partitions hardware computing power into multiple VMs.
    • Type 2 – installs in host OS as an application; not as powerful as Type 1 because it is dependent on the host OS; sometimes called a hosted hypervisor.

Type 1 and Type 2 Hypervisors (2 of 2)

  • Ways that client-hosted VMs created by Type 2 hypervisors might be used:
    • Developers often use VMs to test applications.
    • Help-desk technicians use VMs so they can easily switch from one OS to another.
    • Honeypots are single computers or a network of computer that lure hackers to protect the real network; VMs can be used to create honeypots.
    • Students use VMs to install and practice using and supporting different OSs.

Setting Up Client-Side Virtualization (1 of 6)

  • First step is to make sure the workstation can support the hypervisor and VMs.
  • Customize a Virtualization Workstation:
    • Maximum CPU cores.
    • The motherboard BIOS/UEFI – HAV (hardware-assisted virtualization) must be enabled in BIOS/UEFI setup.
    • Maximum RAM.
    • Lots of storage space.
    • Network requirements – NIC supports Gigabit Ethernet.
    • Emulator requirements.

Setting Up Client-Side Virtualization (2 of 6)

  • A UEFI setup screen to enable hardware virtualization. Figure 10-3 referenced.

Setting Up Client-Side Virtualization (3 of 6)

  • Install and Configure a Type 2 Hypervisor:
    • A hypervisor offers a way to configure each VM.
    • Example: when you launch Oracle VirtualBox, the VirtualBox Manager window appears.
    • See Figures 10-5 through 10-7 referenced.

Setting Up Client-Side Virtualization (4 of 6)

  • Example: Emulated (virtual) hard drives and an optical drive are installed in a VM on VirtualBox. Figure 10-5 referenced.

Setting Up Client-Side Virtualization (5 of 6)

  • Configure motherboard settings in the VM to change the boot order. Figure 10-6 referenced.

Setting Up Client-Side Virtualization (6 of 6)

  • Configure up to four network adapters for a VM in Oracle VirtualBox. Figure 10-7 referenced.

Securing a Virtual Machine

  • Securing the resources in the VM:
    • Secure the VM within the VM.
    • VMs should be isolated for best security.
    • Secure the files that hold a VM.
    • Secure the host computer.

Cloud Computing

  • Cloud computing: when a vendor or corporation makes computer resources available over the Internet.
  • Can provide many other types of resources:
    • Applications
    • Network services
    • Websites
    • Database servers
    • Specialized developer applications
    • Virtual desktops in VMs

Application Virtualization (1 of 2)

  • Application virtualization: an application is made available to users by a virtualization server; does not need to be installed on the user’s computer.
  • Two options for application virtualization:
    • Cloud-based applications: software resides on a server in the cloud and the user accesses the software through a browser.
    • Application streaming: a cross between cloud-based applications and installed applications; parts of the applications are downloaded on the local device only when needed; other parts of the application might continue to run in the cloud from a distant server.

Setting Up Client Computers To Use Cloud Resources (1 of 3)

  • When a hypervisor on a server in the cloud presents a virtual desktop to a client computer: the technology is called Virtual Desktop Infrastructure (VDI).
  • Thick Client and Thin Client concepts:
    • Thick client (fat client): regular desktop computer or laptop.
    • Thin client: computer has a regular OS but comparatively little computer power.
    • Zero client: sometimes called a dumb terminal and does not have an OS and just provides a user interface (keyboard, mouse, monitor).

Setting Up Client Computers To Use Cloud Resources (2 of 3)

  • VDI Virtual Desktop Accounts:
    • Persistent VDI: the user owns the virtual desktop, which can be customized for the user and saved for future use.
    • Nonpersistent VDI: the user receives a desktop from a pool of desktops; each time the user signs on, she gets a desktop that reverts to its original state.

Setting Up Client Computers To Use Cloud Resources (3 of 3)

  • Using VDI, a hypervisor serves up virtual desktops. Figure 10-10 referenced.

Chapter Summary

  • Client-side virtualization is done by creating multiple virtual machines, each with its own virtual desktop, on a physical machine using a hypervisor.
  • A Type 1 hypervisor installs before an OS and is called a bare-metal hypervisor.
  • A Type 2 hypervisor is an application that installs in an OS.
  • When customizing a virtualization workstation, maximize the available budget for CPU cores and the amount of installed RAM.
  • Application virtualization makes an application available to remote users from a virtualization server and does not install the application on the user’s system.