Module 7 Lesson 5: Modifying Virtual Machines - VMware vSphere 4.1 Study Flash Cards

All virtual machine configuration is done in the Virtual Machine Properties dialog box.

• 1. Right-click the virtual machine in the inventory.
• 2. Select Edit Settings.

• 1. Hardware
• 2. Options
• 3. Resources

False. Some hardware changes can be made while powered on. All changes can be made while powered off.

• 1. Virtual hardware changes
• 2. Various virtual machine options
• 3. Resources settings/allocations. CPU, Memory etc...

The list of devices that you are allowed to add depends on whether the virtual machine is powered on or powered off.

• 1. USB controllers
• 2. Ethernet adapters
• 3. hard disks

False. CPU and Memory can be added while a virtual machine is powered on. This feature is called the CPU hot-plug and memory hot-add option. These options are disabled by default.

False. These options are disabled by default. To use these hot-plug features:

• VMware Tools must be installed
• Virtual machine version must be 7 or higher
• The VM guest OS must support CPU and memory hot-plug functionality.
• The hot-plug options must be enabled in the Options tab of the VM properties dialog box.

• VMware Tools must be installed.
• Virtual machine version must be 7 or higher.
• The VM guest OS must support CPU and memory hot-plug functionality.
• The hot-plug options must be enabled in the Options tab of the VM properties dialog box.

True.

You can increase the size of a virtual disk belonging to a virtual machine if it is a flat virtual disk in persistent mode and the virtual machine does not have snapshots.

• 1. Right-click the virtual machine in the inventory and click Edit Settings.
• 2. Select the hard disk in the Hardware list.
• 3. In the Disk Provisioning panel, enter the new size for the hard disk.

After you increase the size of a virtual disk, use the appropiate tool in the guest operating system itself to allow the file system on the disk to use the newly allocated disk space. e.g. Diskpart utility, Windows Disk Management

A raw device mapping (RDM) is a file on a VMware vStorage VMFS datastore with a .vmdk extension (the file contains only disk information describing the mapping to a LUN) that points to a raw LUN.

When you create a raw device mapping, vCenter Server creates a file in the specified VMFS volume that points to a raw LUN.

Encapsulating disk information in the file (RDM) allows the VMkernel to lock the LUN so that only one virtual machine can write to it.

The data is stored on the LUN.

An RDM supports two compatibility modes:

• 1. Physical compatibility mode.
• 2. Virtual compatibility mode.

RDM Physical compatibility mode allows the guest operating system to access the hardware directly.

True.

False. The inability to take a native Vmware snapshot of a pRDM also means that features that depend on Vmware snapshots (the vStorage API’s for Data Protection, Vmware Data Recovery, and Storage vMotion) don’t work with pRDMs. With Physical compatibility mode a VM can access a LUN directly. This is generally used when the application inside VM wants to directly access LUN. However when using physical compatibility mode you lose the option to clone a VM, make it a template or migrate it if it involves copying the disk.

Virtual compatibility mode allows a RDM LUN to behave as if it were a virtual disk and therefore allows the virtual machine to use VMware shapshots and other storage advanced functionality e.g. storage VMotion.

When you clone the disk, make a template out of it, or migrate it (if the migration involves copying the disk).

• 1. VM display name
• 2. Guest operating system type

• 1. .vmx file - VM configuration file
• 2. VM directory - VM working location

False. When a virtual machine is first created, the file names and the directory name associated with the VM are based on its display name. But changing the display name later does not modify the file and directory names.

• 1. Virtual Machine Name
• 2. Virutal Machine Configuration File
• 3. Virtual Machine Working Location
• 4. Guest Operating System

• 1. Microsoft Window
• 2. Linux
• 3. Novell Netware
• 4. Solaris
• 5. Other

• 1. Display name
• 2. Guest operating system type

False. When a virtual machine is first created, the file names and the directory name associated with the virtual machine are based on its display name. But changing the display name later does not modify the file and directory names.

• 1. Power Controls
• 2. Run VMware Tools Scripts
• 3. Advanced

• 1. Check and update VMware Tools automatically when a newer version becomes available.
• 2. Synchronize guest time with the host.

• 1. Power On Boot Delay
• 2. Force BIOS Setup
• 3. Failed Boot Recovery