1

2
3
4
•
•
•
•

5
https://docs.vmware.com/en/VMware-vSphere/index.html

6
7
•
•
•

8
9
10
11
https://docs.vmware.com/en/VMware-vSphere/index.html

https://www.vmware.com/resources/compatibility

12
 •
—
—
—
—
—
•
•
•

•
•

•The VMware Tools service: This service synchronizes the time in the guest operating system
with the time in the host operating system.
•A set of VMware device drivers, with additional Perfmon monitoring options.
•A set of scripts that helps you automate guest operating system operations: You can
configure the scripts to run when the VM's power state changes.

•Faster graphical performance

•Shared folders between host and guest file systems
•Copying and pasting text, graphics, and files between the virtual machine and the host or
client desktop
•Scripting that helps automate guest operating system operations

13
 windows.iso

• linux.iso
• open-vm-tools
yum apt rpm

https://docs.vmware.com/en/VMware-
Tools/index.html

14
https://docs.vmware.com/en/VMware-Tools/index.html

15
 •

https://marketplace.cloud.vmware.com

16
•
—
—
—
•
—
—

17
18
19
20
•
•
•
•

21
22
•
•
•
•
•

23
•

24
 <VM_name>
•A configuration file (.vmx).
•If the VM is converted to a template, a VM template configuration file (.vmtx) replaces the
VM configuration file (.vmx).
•Swap files (.vswp) used to reclaim memory during periods of contention.
•A file containing the VM's BIOS or EFI settings (.nvram).
•A VM's current log file (.log) and a set of files used to archive old log entries (-#.log).
In addition to the current log file, vmware.log, up to six archive log files are maintained at
one time. For example, -1.log to -6.log might exist at first.
The next time an archive log file is created, for example, when the VM is powered off and
powered back on, the following actions occur: The -6.log is deleted, the -5.log is recalled
to -6.log, and so on. Finally, the previous vmware.log is recalled to the -1.log.
•One or more virtual disk files. The first virtual disk has files VM_name.vmdk and VM_name-
flat.vmdk.
If the VM has more than one disk file, the file pair for the subsequent disk files is called
VM_name_#.vmdk and VM_name_#-flat.vmdk. # is the next number in the sequence,
starting with 1. For example, if the VM called Test01 has two virtual disks, this VM has the
Test01.vmdk, Test01-flat.vmdk, Test01_1.vmdk, and Test01_1-flat.vmdk files.

https://docs.vmware.com/8.0/TBD

25
•Datagrams: Connectionless and similar to UDP queue pairs
•Connection oriented: Similar to TCP

https://docs.vmware.com/en/VMware-vSphere/index.html

26
https://configmax.vmware.com

26
https://docs.vmware.com/en/VMware-vSphere/index.html

https://kb.vmware.com/s/article/1003746

27
•
•

28
https://configmax.vmware.com/

29
 •
•
•
•
•
•

•BusLogic Parallel: The Mylex (BusLogic) BT/KT-958 compatible host bus adapter.
•LSI Logic Parallel: The LSI Logic LSI53C10xx Ultra320 SCSI I/O controller is supported.
•LSI Logic SAS: The LSI Logic SAS adapter has a serial interface.
•VMware Paravirtual SCSI: A high-performance storage adapter that can provide greater
throughput and lower CPU use.
•AHCI SATA controller: Provides access to virtual disks and CD/DVD devices. The SATA
virtual controller appears to a VM as an AHCI SATA controller.
•Virtual NVMe: NVMe is a protocol for attaching and accessing flash storage devices to the
PCI Express bus. NVMe is an alternative to existing block-based server storage I/O access
protocols.

30
•

31
 •

•
unmap

•
•
•

unmap

unmap https://docs.vmware.com/en/VMware-vSphere/index.html

32
• •

– •
–
•

33
34
 •
•
•
•

https://docs.vmware.com/en/VMware-
vSphere/index.html.

35
•VM compatibility level (or hardware version), which depends on the host that created or most
recently updated it. For example, the VMXNET3 virtual NIC requires hardware version 14 or
later.
•Whether the VM compatibility is updated to the latest version for the current host.
•Guest operating system

•E1000E: Emulated version of the Intel 82574 Gigabit Ethernet NIC. E1000E is the default
adapter for Windows 8 and Windows Server 2012.
•E1000: Emulated version of the Intel 82545EM Gigabit Ethernet NIC, with drivers available in
newer guest operating systems, including Windows XP and later and Linux versions 2.4.19
and later.
•Flexible: Identifies itself as a Vlance adapter when a VM starts, but initializes itself and
functions as either a Vlance or a VMXNET adapter, depending on which driver initializes it.
With VMware Tools installed, the VMXNET driver changes the Vlance adapter to the higher
performance VMXNET adapter.
•Vlance: Emulated version of the AMD 79C970 PCnet32 LANCE NIC, an older 10 Mbps NIC
with drivers available in 32-bit legacy guest operating systems. A VM configured with this
network adapter can use its network immediately.
•VMXNET3: A paravirtualized NIC designed for performance. VMXNET3 offers all the features
available in VMXNET2 and adds several new features, such as multiqueue support (also
known as Receive Side Scaling in Windows), IPv6 offloads, and MSI/MSI-X interrupt delivery.
•With PVRDMA, multiple guests can access the RDMA device by using verbs API, an
industry-standard interface. A set of these verbs was implemented to expose an RDMA-
capable guest device (PVRDMA) to applications. The applications can use the PVRDMA
guest driver to communicate with the underlying physical device. PVRDMA supports RDMA,

36
providing the following functions:
—OS bypass
—Zero-copy
—Low latency and high bandwidth
—Less power use and faster data access
•SR-IOV pass-through: Representation of a virtual function on a physical NIC with
SR-IOV support. This adapter type is suitable for VMs that require more CPU
resources or where latency might cause failure. If VMs are sensitive to network delay,
SR-IOV can provide direct access to the virtual functions of supported physical NICs,
bypassing the virtual switches and reducing overhead.
SR-IOV pass-through is available for Red Hat Enterprise Linux 6 and later, and
Windows Server 2008 R2 with SP2. An operating system release might contain a
default virtual function driver for certain NICs. For others, you must download and
install it from a location provided by the NIC or host vendor.

36
 •

•
•
•

•
•

https://blogs.vmware.com/vsphere/2020/03/vsphere-7-assignable-hardware.html

37
•
•
•
•
•
•
•

https://docs.vmware.com/en/VMware-vSphere/8.0/TBD

38
•The Web console displays the VM console in a separate browser tab.
•The remote console requires downloading the VMware Remote Console (VMRC) standalone
application, which opens in a separate window. The VMware Remote Console standalone
application lets you connect to client devices and launch virtual machine consoles on remote
hosts.

39
40
•
•
•
•
•

41
42
•
•
•

43
•
–

•
–

•
•

44
 •

•
•

•You must install VMware Tools.

•The VM must use hardware version 11 or later.
•The guest operating system in the VM must support CPU and memory hot-plug features.
•The hot-plug features must be activated in the CPU or Memory settings on the Virtual
Hardware tab.

45
•

46
.vmdk

47
.vmx

48
http://kb.vmware.com/kb/1318 http://kb.vmware.com/kb/1006427

49
50
51
•
•
•

52
53
•
•
•
•

54
•
•
•

55
•Same format as source
•Thin-provisioned format
•Thick-provisioned lazy-zeroed format
•Thick-provisioned eager-zeroed format

56
.vmx .vmtx

57
58
•

59
60
 •
•

•When you deploy many VMs from a template, all the VMs start with the same base image.
Cloning many VMs from a running VM might not create identical VMs, depending on the
activity happening within the VM when the VM is cloned.
•VM templates use disk space, so you must plan your disk space requirements accordingly.
•Deploying a VM from a template is quicker than cloning a running VM, especially when you
must deploy many VMs at a time.

61
•
•
•
•
•
•
•

62
•
•

63
https://docs.vmware.com/en/VMware-vSphere/index.html

64
65
•
•
•
•

66
67
•
•
•
•

68
69
•

•
•
•
•

70
•
•
•

71
72
73
 • •

• •
•
•
•
•

•If you convert the VM template in the vCenter inventory to a VM, the corresponding VM
template library item is deleted.
•If you rename the VM template in vCenter inventory, the corresponding VM template library
item is also renamed, and vice versa.
•If you delete the VM template in the vCenter inventory, the corresponding VM template library
item is also deleted.

https://docs.vmware.com/en/VMware-vSphere/index.html

74
75
76
•
•
•
•
•

77
78
79
•
•
•
•

80
81
•
•

82
83
84
•

85
86
87
88
•Both published and subscribed libraries reside on a datastore.
•Both published and subscribed libraries reside on an NFS file system mounted on the
vCenter instances.
•The published library resides on an NFS file system, whereas the subscribed library resides
on a datastore.

•If this number matches the one in the published and subscribed libraries, no synchronization
is required.
•If a discrepancy is found, the version number of each item in the library is checked.
•If discrepancies are found, only items with such discrepancies are synchronized.

89
90
91
92
•
•

93
94
•

95
 •

•You can monitor the changes that have been made by privileged users.
•You can patch or modify VMs while the template is being used to deploy VMs.
•You can view the history of changes made to a VM.

96
97
98
99
100
•Who made the updates
•When the updates were made
•Notes or information added during the updates

101
•
•

102
103
•

104
•

•
•

105