Skip to content

Added workaround for vm name sequence error #208

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
yadvr merged 2 commits into from
Apr 22, 2021
Merged

Added workaround for vm name sequence error #208

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
7b72cac
Added workaround for vm name sequence error
Spaceman1984 Apr 15, 2021
72201d7
Update source/installguide/hypervisor/vsphere.rst
Spaceman1984 Apr 20, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions source/installguide/hypervisor/vsphere.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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:
^^^^^^^^^^^^^^^^^^^^^^
Expand Down