-
Notifications
You must be signed in to change notification settings - Fork 109
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.
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
Add note on the Vmware to KVM instances guest OS #377
Conversation
@blueorangutan docbuild |
@nvazquez a Jenkins job has been kicked to build the document. I'll keep you posted as I make progress. |
QA-Doc build preview: https://qa.cloudstack.cloud/builds/docs-build/pr/377. (QA-JID 200) |
@@ -115,6 +115,8 @@ When importing a Virtual Machine from VMware to KVM, CloudStack performs the fol | |||
|
|||
.. note:: As mentioned above, the migration/conversion process uses an external tool, virt-v2v, which supports most but not all the operating systems out there (this is true for both the host on which the virt-v2v tool is running as well as the guest OS of the instances being migrated by the tool). Thus, the success of the import process will, almost exclusively, depend on the success of the virt-v2v conversion. In other words, the success will vary based on factors such as the current OS version, installed packages, guest OS setup, file systems, and others. Success is not guaranteed. We strongly recommend testing the migration process before proceeding with production deployments. | |||
|
|||
.. note:: The resulting imported VM is converted from VMware considering the source guest OS but it uses the default import template in CloudStack: CentOS 4/5. This does not mean that the converted VMs are CentOS VMs, it is simply a link to the default import template as it is not currently possible to select a template from which to import the VM. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is default import template - CentOS 4 or CentOS 5 (or both - picks based on guest OS)?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it's not the "template" - it's the guest OS type (the template is some dummy default template)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We need the same for the Import QCOW2 from Local/Shared storage (or remote KVM) - I think in all cases, the guest OS is not specified, so it defaults to CentOS 4.5
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The guest OS comes from the template, and for these kind of imports we are using the default import template which has the CentOS 4.5 OS type
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@sureshanaparti @andrijapanicsb are your concerns addressed?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not OK with that. Irrelevant of what "template" we assign the VM to (this is low level stuff that customer does not need to care about) - this is about asking user to change the "OS Type" - and we need to explain that fact - "you have to change the OS type after the import"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks guys, fixed
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
@blueorangutan docbuild |
@nvazquez a Jenkins job has been kicked to build the document. I'll keep you posted as I make progress. |
QA-Doc build preview: https://qa.cloudstack.cloud/builds/docs-build/pr/377. (QA-JID 206) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Quick note extending the docs added on PR: #342
📚 Documentation preview 📚: https://cloudstack-documentation--377.org.readthedocs.build/en/377/