Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Prerequisites and limitations when using 256 PVSCSI disks in a virtual machine (54468)

Last Updated: 6/25/2018Categories: InformationalTotal Views: 5374Language:
Chinese (Simplified)JapaneseEnglish

1 like this article

Subscribe to get an email
newsletter with new updates

1 people found this helpful Please provide article feedback:

Symptoms

This document describes the necessary information to use the 256 PVSCSI disks in a virtual machine.
To avoid the failures when using this feature, the user must aware of the below prerequisites and limitations:

Prerequisites:

To use this feature, the Virtual Machine’s hardware version must be 14 or higher.
The ESXi host must meet below recommended

performance data:

CPU: 2 CPUs with 28 cores per socket or above
Memory: 64GiB capacity or above
Physical Storage(Local Storage or Networked Storage):
IOPS Bandwidth Latency

Read >120000 >470MB/s <1080 usec

Write >110000 >470MB/s <1198 usec

Limitations:

Features not supported:

VMware vSphere Replication

Content Libraries

OVF Template Deployment/Export through UI

SRM VR mode (vSphere replication)

Features with limited supportive:

SRM only support ABR mode (Array-based replication)

Application quiesced snapshots supported for VM with less than 64 disks due to VSS limitations.

Storage vMotion and XvMotion may timeout when such large VM has snapshots.

Purpose

Best Practices, Caveats, and Interoperability when working with VM that has more than 60 VMDKs.

Resolution

Currently, there is no resolution or workaround:

VMware vSphere Replication

Content Libraries

Workaround

To work around this issue:

OVF Template Deployment/Export through UI:

Workaround: Use PowerCLI Export-VApp/Import-VApp cmd-lets for templates export or Import.

SRM VR mode (vSphere replication):

Workaround: Use the Array-based replication mode when performing SRM operations.

Storage vMotion and XvMotion timeout issue:

Workaround: Delete the snapshots before Storage vMotion and XvMotion.

Note: Please make sure all data has been backed up before deleting the snapshots.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
Download and Install VMware Fusion (2014097)

KB
•
ESX/ESXi ホスト上の物理ネットワーク アダプタの整合性の確認 (1003686)

Results 1-3 of 3

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSphere ESXi

Related Versions:

VMware vSphere ESXi 6.7

Take Our Survey

Support Assistant