VMware 4817V62 Administration Guide - Page 188

SSE3 Considerations, About Enhanced VMotion Compatibility, EVC Requirements

Page 188 highlights

vSphere Basic System Administration SSE3 Considerations Within the Intel P4 and AMD Opteron processor families, VMware places a restriction between processors that do support the SSE3 instructions and processors that do not support the SSE3 instructions. Because they are application level instructions that bypass the virtualization layer, these instructions could cause application instability if mismatched after a migration with VMotion. SSSE3 Considerations Within the Intel P4 and Intel Core processor families, VMware places a restriction between processors that do support the SSSE3 instructions and processors that do not support the SSSE3 instructions. Because they are application level instructions that bypass the virtualization layer, these instructions could cause application instability if mismatched after a migration with VMotion. SSE4.1 Considerations Within the Intel Core 2 processor family, VMware places a restriction between processors that do support the SSE4.1 instructions and processors that do not support the SSE4.1 instructions because they are application level instructions that bypass the virtualization layer, and could cause application instability if mismatched after a migration with VMotion. About Enhanced VMotion Compatibility You can use the Enhanced VMotion Compatibility (EVC) feature to help ensure VMotion compatibility for the hosts in a cluster. EVC ensures that all hosts in a cluster present the same CPU feature set to virtual machines, even if the actual CPUs on the hosts differ. Using EVC prevents migrations with VMotion from failing because of incompatible CPUs. Configure EVC from the cluster settings dialog box. When you configure EVC, you configure all host processors in the cluster to present the feature set of a baseline processor. EVC leverages AMD-V Extended Migration technology (for AMD hosts) and Intel FlexMigration technology (for Intel hosts) to mask processor features so that hosts can present the feature set of an earlier generation of processors. The baseline feature set must be equivalent to, or a subset of, the feature set of the host with the smallest feature set in the cluster. EVC masks only those processor features that affect VMotion compatibility. Enabling EVC does not prevent a virtual machine from taking advantage of faster processor speeds, increased numbers of CPU cores, or hardware virtualization support that might be available on newer hosts. EVC cannot prevent virtual machines from accessing hidden CPU features in all circumstances. Applications that do not follow CPU vendor recommended methods of feature detection might behave unexpectedly in an EVC environment. VMware EVC cannot be supported with ill-behaved applications that do not follow the CPU vendor recommendations. For more information about creating well-behaved applications, search the VMware Knowledge Base for the article Detecting and Using New Features in CPUs. EVC Requirements Hosts in an EVC cluster must meet certain requirements. To enable EVC on a cluster, the cluster must meet the following requirements: n You must be running vCenter Server 2.5 Update 2 or later. n All virtual machines in the cluster that are running on hosts with a feature set greater than the EVC mode you intend to enable must be powered off or migrated out of the cluster before EVC is enabled. (For example, consider a cluster containing an Intel Xeon Core 2 host and an Intel Xeon 45nm Core 2 host, on which you intend to enable the Intel Xeon Core 2 baseline. The virtual machines on the Intel Xeon Core 2 host can remain powered on, but the virtual machines on the Intel Xeon 45nm Core 2 host must be powered off or migrated out of the cluster.) n All hosts in the cluster must have CPUs from a single vendor, either AMD or Intel. n All hosts in the cluster must be running ESX/ESXi 3.5 Update 2 or later. 188 VMware, Inc.

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276
  • 277
  • 278
  • 279
  • 280
  • 281
  • 282
  • 283
  • 284
  • 285
  • 286
  • 287
  • 288
  • 289
  • 290
  • 291
  • 292
  • 293
  • 294
  • 295
  • 296
  • 297
  • 298
  • 299
  • 300
  • 301
  • 302
  • 303
  • 304
  • 305
  • 306
  • 307
  • 308
  • 309
  • 310
  • 311
  • 312
  • 313
  • 314
  • 315
  • 316
  • 317
  • 318
  • 319
  • 320
  • 321
  • 322
  • 323
  • 324
  • 325
  • 326
  • 327
  • 328
  • 329
  • 330
  • 331
  • 332
  • 333
  • 334
  • 335
  • 336
  • 337
  • 338
  • 339
  • 340
  • 341
  • 342
  • 343
  • 344
  • 345
  • 346
  • 347
  • 348
  • 349
  • 350
  • 351
  • 352
  • 353
  • 354
  • 355
  • 356
  • 357
  • 358
  • 359
  • 360
  • 361
  • 362
  • 363
  • 364

SSE3 Considerations
Within the Intel P4 and AMD Opteron processor families, VMware places a restriction between processors that
do support the SSE3 instructions and processors that do not support the SSE3 instructions. Because they are
application level instructions that bypass the virtualization layer, these instructions could cause application
instability if mismatched after a migration with VMotion.
SSSE3 Considerations
Within the Intel P4 and Intel Core processor families, VMware places a restriction between processors that do
support the SSSE3 instructions and processors that do not support the SSSE3 instructions. Because they are
application level instructions that bypass the virtualization layer, these instructions could cause application
instability if mismatched after a migration with VMotion.
SSE4.1 Considerations
Within the Intel Core 2 processor family, VMware places a restriction between processors that do support the
SSE4.1 instructions and processors that do not support the SSE4.1 instructions because they are application
level instructions that bypass the virtualization layer, and could cause application instability if mismatched
after a migration with VMotion.
About Enhanced VMotion Compatibility
You can use the Enhanced VMotion Compatibility (EVC) feature to help ensure VMotion compatibility for the
hosts in a cluster. EVC ensures that all hosts in a cluster present the same CPU feature set to virtual machines,
even if the actual CPUs on the hosts differ. Using EVC prevents migrations with VMotion from failing because
of incompatible CPUs.
Configure EVC from the cluster settings dialog box. When you configure EVC, you configure all host processors
in the cluster to present the feature set of a baseline processor. EVC leverages AMD-V Extended Migration
technology (for AMD hosts) and Intel FlexMigration technology (for Intel hosts) to mask processor features so
that hosts can present the feature set of an earlier generation of processors. The baseline feature set must be
equivalent to, or a subset of, the feature set of the host with the smallest feature set in the cluster.
EVC masks only those processor features that affect VMotion compatibility. Enabling EVC does not prevent
a virtual machine from taking advantage of faster processor speeds, increased numbers of CPU cores, or
hardware virtualization support that might be available on newer hosts.
EVC cannot prevent virtual machines from accessing hidden CPU features in all circumstances. Applications
that do not follow CPU vendor recommended methods of feature detection might behave unexpectedly in an
EVC environment. VMware EVC cannot be supported with ill-behaved applications that do not follow the
CPU vendor recommendations. For more information about creating well-behaved applications, search the
VMware Knowledge Base for the article
Detecting and Using New Features in CPUs
.
EVC Requirements
Hosts in an EVC cluster must meet certain requirements.
To enable EVC on a cluster, the cluster must meet the following requirements:
n
You must be running vCenter Server 2.5 Update 2 or later.
n
All virtual machines in the cluster that are running on hosts with a feature set greater than the EVC mode
you intend to enable must be powered off or migrated out of the cluster before EVC is enabled. (For
example, consider a cluster containing an Intel Xeon Core 2 host and an Intel Xeon 45nm Core 2 host, on
which you intend to enable the Intel Xeon Core 2 baseline. The virtual machines on the Intel Xeon Core 2
host can remain powered on, but the virtual machines on the Intel Xeon 45nm Core 2 host must be powered
off or migrated out of the cluster.)
n
All hosts in the cluster must have CPUs from a single vendor, either AMD or Intel.
n
All hosts in the cluster must be running ESX/ESXi 3.5 Update 2 or later.
vSphere Basic System Administration
188
VMware, Inc.