Module 03 - Virtualized Data Center - Compute Flashcards

1
Q

First step towards building a cloud infrastructure

A

Virtualization

(3.3)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Logical entity that looks and behaves like a physical machine

A

Virtual Machine (VM)

(3.5)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Layer which resides between hardware and VM OS’s

A

Virtualization Layer

(3.5)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Another name for the virtualization layer

A

Hypervisor Layer

(3.5)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Technique of masking or abstracting the physical compute hardware and enabling multiple OSs to run concurrently on a single or clustered physical machine(s).

A

Compute Virtualization

(3.5)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Software that allows multiple OSs to run concurrently on a physical machine and to interact directly with the physical hardware.

A

Hypervisor

(3.7)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Two components of a hypervisor

A

1) Kernel 2) Virtual Machine Monitor (VMM)
(3. 7)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Designed specifically to support multiple virtual machines and to provide core functionalities, such as resource scheduling, I/O stacks, etc.

A

Hypervisor kernel

(3.7)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Abstracts hardware to appear as a physical machine with its own CPU, memory, and I/O devices. Executes commands on the CPUs and performs Binary Translation.

A

Virtual Machine Monitor (VMM)

(3.7)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Two types of hypervisors

A

1) Bare-metal hypervisor 2) Hosted hypervisor
(3. 8)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Type of hypervisor that is directly installed on the x86 based hardware.Has direct access to the hardware resources.

A

Bare-metal Hypervisor

(3.8)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Type of hypervisor installed and run as an application on top of an OS. Supports broadest range of hardware configurations.

A

Hosted Hypervisor

(3.8)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Type of hypervisor most predominantly used within the Virtualized Data Center (VDC)

A

Bare-Metal Hypervisor

(3.8)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Benefits of Compute Virtualization

A

1) Server Consolidation 2) Isolation 3) Encapsulation 4) Hardware Independence 5) Reduced Cost
(3. 9)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Four levels of privilege of the x86 architecture

A

Ring 0, 1, 2, 3

(3.11)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Most privileged level of the x86 architecture where OS runs.

A

Ring 0

(3.11)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

At what privilege level do most user applications run in x86 architecture?

A

Ring 3

(3.11)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
18
Q

Three techniques for handling privileged instructions to virtualize the CPU on x86 architectures

A

1) Full Virtualization 2) Paravirtualization 3) Hardware Assisted Virtualization
(3. 11)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
19
Q

VMM runs in the privileged Ring 0. VMM decouples guest OS from the underlying physical hardware. Each VM is assigned a VMM. Guest OS is NOT aware of being virtualized.

A

Full Virtualization

(3.12)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
20
Q

Guest OS knows that is is virtualized. Guest OS runs in Ring 0. Modified guest OS kernel is required. Only works for open source OS’s such as Linux and OpenBSD. Not supported by unmodified guest OS’s such as MS Windows.

A

Paravirtualization

(3.13)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
21
Q

Technique uses virtualization capabilities of equipped CPU’s to assist with virtualization. Reduces virtualization overhead in the hypervisor layer. CPU and memory virtualization support is provided in hardware.

A

Hardware Assisted Virtualization

(3.14)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
22
Q

From a hypervisor’s perspective, a Virtual Machine is a discrete set of ___________.

A

files

(3.16)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
23
Q

What files are contained in a Virtual Machine file set as seen by the Hypervisor?

A

1) Virtual BIOS File, 2) Virtual Swap File, 3) Virtual Disk File, 4) Log File, 5) Virtual Config File
(3. 16)

24
Q

Two file systems supported by hypervisors

A

1) Virtual Machine File System (VMFS), 2) Network File System (NFS)
(3. 18)

25
Q

Cluster file system that allows multiple physical machines to perform read/write on the same storage device concurrently.Deployed on Fiber Channel (FC) and iSCSI storage apart from local storage.

A

Virtual Machine File System (VMFS)

(3.18)

26
Q

Enables storing VM files on a remote file server (NAS device). Client built into hypervisor.

A

Network File System (NFS)

(3.18)

27
Q

True or False: All virtual machines have standardized hardware.

A

True

(3.19)

28
Q

Provides mouse, keyboard, and screen functionality, power change alerts, access to VM BIOS.

A

Virtual Machine Console

(3.21)

29
Q

Process of allocating resources from physical machine or clustered physical machines to virtual machines (VMs) to optimize the utilization of resources.

A

Resource Management

(3.23)

30
Q

Goals of Resource Management

A

1) Controls utilization of resources, 2) Prevent VMs from monopolizing resources, 3) Allocates resources based on priority
(3. 23)

31
Q

For resources to be managed centrally, they must be ___________.

A

Pooled

(3.23)

32
Q

Three resource allocation parameters used to control the resources consumed by resource pools or VMs:

A

1) Share, 2) Limit, 3) Reservation
(3. 24)

33
Q

Relative amount of CPU & memory a VM or a child resource pool can have with respect to other peer child pools or VMs.

A

Share

(3.26)

34
Q

Amount of CPU and memory reserved for a VM or a child resource pool.

A

Reservation

(3.26)

35
Q

Maximum amount of CPU and memory a VM or a child resource pool can consume.

A

Limit

(3.26)

36
Q

Makes a physical CPU appear as two or more logical CPUs.

A

Hyper-threading

(3.27)

37
Q

True or False: VMs can be configured with more memory than physically available.

A

True .Referred to as memory overcommitment.

(3.31)

38
Q

Three memory management techniques:

A

1) Transparent Page Sharing, 2) Memory Ballooning, 3) Memory Swapping
(3. 31)

39
Q

Hypervisor detects identical memory pages of VMs and maps them to same physical page.For writes, hypervisor treats the shared pages as copy-on-write.Attempt to write on a shared page generates a minor page fault and CREATES A PRIVATE COPY after write and remaps the memory.

A

Transparent Page Sharing

(3.32)

40
Q

Makes the guest OS free some of the virtual machine memory.

A

Ballooning

(3.33)

41
Q

Technique where memory contents are temporarily stored on disk. Last option because it causes notable performance impact.

A

Memory swapping

(3.34)

42
Q

How is the size of a VM swap file calculated?

A

Swap file size is equal to the DIFFERENCE between the MEMORY LIMIT and the VM MEMORY RESERVATION

(3.34)

43
Q

Defines that multiple VM’s should be run on the same hypervisor, or must be run on different hypervisors.

A

VM to VM Affinity (anti-Affinity)

(3.35)

44
Q

Defines that a particular VM should or should not be run on a particular hypervisor.

A

VM to Server Affinity (anti-Affinity)

(3.35)

45
Q

Process through which physical machines are converted into VMs.

A

Physical to Virtual (P2V) Conversion

(3.38)

46
Q

3 Key Components of P2V Converter

A

1) Converter Server2) Converter Agent3) Converter Boot CD
(3. 39)

47
Q

Responsible for controlling conversion process.Used for hot conversion only (when source is running its OS).Pushes and installs agent on the source machine.

A

P2V Converter Server

(3.40)

48
Q

Responsible for performing the conversion.Used in hot mode only.Installed on physical machine to convert it to a VM.

A

P2V Converter Agent

(3.40)

49
Q

Bootable CD contains its OS and converter application.Converter application is used to perform cold conversion.

A

P2V Converter Boot CD

(3.40)

50
Q

Occurs while physical machine is running.Performs synchronization; copies blocks that were changed during the initial cloning period.Performs power off at source and power on at target VM.Changes IP address and machine name of the selected machine, if both machines must exist on the same network.

A

Hot Conversion

(3.41)

51
Q

Occurs while physical machine is NOT running OS and application.Boots the physical machine using converter boot CD.Creates consistent copy of the physical machine.

A

Cold Conversion

(3.41)

52
Q

Describe the Hot Conversion Process Steps

A
  1. Converter server prepares the source machine for the conversion by installing the agent on the source physical machine.2. Agent takes a snapshot of the source volume.3. Converter server creates a VM on the destination machine.4. Agent clones the physical disk of the source machine (using snapshot) to the virtual disk of the destination virtual machine.5. Agent synchronizes the data and installs the required drivers to allow the OS to boot from a VM and personalize the VM.6. VM is ready to run on the destination server.
    (3. 42 & 3.43)
53
Q

Describe the Cold Conversion Process

A
  1. Boot source machine from the converter boot CD and use the converter software to define conversion parameters and start the conversion.2. Converter application creates a new VM on the destination physical machine.3. Converter app copies volumes from the source machine to the destination machine.4. Converter app installs the required drivers to allow the OS to boot in a VM and personalizes the VM.5. VM is ready to run on the destination server
    (3. 44 & 3.45)
54
Q

Infrastructure virtualization suite that provides virtualization, resource mgmt & optimization, HA, and operational automation.

A

VMware vSphere

(3.48)

55
Q

Key vSphere Components

A

1) VMware ESXi, 2) VMware vCenter Server, 3) VMware vCenter Client, 4) VMware vStorage VMFS
(3. 48)

56
Q

Converts physical machines to VMs.Supports conversion of VM created third party software to VMware VM.Lets users convert Windows and Linux-based physical machines to VMware virtual machines.Converts VMs between VMware platoforms.

A

VMware vCenter Converter

(3.49)