daviftorres opened a new issue, #12041: URL: https://github.com/apache/cloudstack/issues/12041
### problem ## Environment - CloudStack: 4.20.2 - VMware: 7.0.3 ## Issue When a VMware zone is deployed, the default CloudStack template does not define the disk controller. <img width="1004" height="255" alt="Image" src="https://github.com/user-attachments/assets/12030e7e-0f54-4534-9a22-db00ece8fe1f"; /> As a result, new instances get `rootDiskController=ide` and `dataDiskController=osdefault`. <img width="863" height="316" alt="Image" src="https://github.com/user-attachments/assets/c21e48b3-c34f-48e9-b209-bf2d461020a0"; /> However, inside the guest OS, the disk actually appears as SCSI, since VMware defaults to SCSI. <img width="716" height="161" alt="Image" src="https://github.com/user-attachments/assets/fc8ee2bc-359b-47fc-81a6-560fd89d7531"; /> ## Problem If you try to "Override root disk size" or "Override root disk offering" during instance creation, it fails. This happens because CloudStack “guesses” the controller type as IDE, as it’s not defined in the template. <img width="347" height="350" alt="Image" src="https://github.com/user-attachments/assets/6dc1de6f-318c-482c-bff0-5d9d85d48671"; /> <img width="542" height="461" alt="Image" src="https://github.com/user-attachments/assets/b285fdcc-f137-4b76-aa89-97f62ba6ae23"; /> <img width="1611" height="552" alt="Image" src="https://github.com/user-attachments/assets/cf533ede-32b0-4d7d-8636-0df684ccea4b"; /> ## Solution Add a custom setting to define the controller explicitly `rootDiskController=scsi`. <img width="1623" height="212" alt="Image" src="https://github.com/user-attachments/assets/bfd0656b-0ec2-4e21-a989-599d412b0348"; /> After this, new instances will be created successfully, with the correct controller automatically applied. <img width="849" height="294" alt="Image" src="https://github.com/user-attachments/assets/f7c78623-de3c-463d-b67b-58f26dca0ddd"; /> ## Notes Inside the guest, disks still appear as SCSI, confirming that VMware uses SCSI by default. <img width="717" height="161" alt="Image" src="https://github.com/user-attachments/assets/1ee07f35-961f-4c84-989f-6ccc85a5ecbe"; /> ## Additionally The default template (which uses LVM and ext3) does not automatically expand to match the resized volume. <img width="762" height="345" alt="Image" src="https://github.com/user-attachments/assets/01b6d3ae-8308-4c1c-bb88-c3f6b6ca3cca"; /> <img width="671" height="179" alt="Image" src="https://github.com/user-attachments/assets/8ffd08a0-2056-45b4-8e9f-684e59bbaacc"; /> To simplify administration I would recommend a new template to be the default pulled one: - Debian (like the System VMs) instead of CentOS. - Avoid LVM because it adds complexity for basic tasks (like expanding the root filesystem). - Swap files can replace swap partitions with similar performance. - Swap partitions at the end of the disk make resizing filesystem a real pain. For generic templates, consider omitting swap entirely and users can add it later if needed. ### versions The versions of ACS, hypervisors, storage, network etc.. ### The steps to reproduce the bug 1. 2. 3. ... ### What to do about it? _No response_ -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
