andrijapanicsb commented on code in PR #377: URL: https://github.com/apache/cloudstack-documentation/pull/377#discussion_r1478039816
########## source/adminguide/virtual_machines/importing_vmware_vms_into_kvm.rst: ########## @@ -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. Review Comment: 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" -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@cloudstack.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
