This is an automated email from the ASF dual-hosted git repository.
rohit pushed a commit to branch 4.15
in repository https://gitbox.apache.org/repos/asf/cloudstack-documentation.git
The following commit(s) were added to refs/heads/4.15 by this push:
new f89f386 Added workaround for vm name sequence error (#208)
f89f386 is described below
commit f89f386c76abdb8a3e65bb1d8ecbeec3b84b2e78
Author: Spaceman1984 <[email protected]>
AuthorDate: Thu Apr 22 11:16:16 2021 +0200
Added workaround for vm name sequence error (#208)
* Added workaround for vm name sequence error
* Update source/installguide/hypervisor/vsphere.rst
Co-authored-by: dahn <[email protected]>
Co-authored-by: dahn <[email protected]>
---
source/installguide/hypervisor/vsphere.rst | 11 +++++++++++
1 file changed, 11 insertions(+)
diff --git a/source/installguide/hypervisor/vsphere.rst
b/source/installguide/hypervisor/vsphere.rst
index af95ddc..9061e06 100644
--- a/source/installguide/hypervisor/vsphere.rst
+++ b/source/installguide/hypervisor/vsphere.rst
@@ -51,6 +51,17 @@ Software requirements:
Apply All Necessary Hotfixes. The lack of up-do-date hotfixes can lead to
data corruption and lost VMs.
+.. note::
+
+ When using vSphere and vCenter versions 6.0 and 6.5 there is a limitation on
+ instance names with a sequence number between 99999 and 1000000. For
example if you take
+ a snapshot of a VM, the expected filename will be different to what
cloudstack expects.
+ It is advisable to set the sequence number to 1M to prevent issues by
executing the
+ following script on your cloudstack database:
+
+ UPDATE cloud.sequence
+ SET value = 1000000
+ WHERE name = 'vm_instance_seq';
Hardware requirements:
^^^^^^^^^^^^^^^^^^^^^^
