daviftorres commented on issue #12041:
URL: https://github.com/apache/cloudstack/issues/12041#issuecomment-3548200556

   It seems there is a contradiction in the recommended/default disk controller 
for VMware.
   
   The global setting shows `ide` as the default, and `ide` is listed as a 
valid option.
   
   <img width="839" height="74" alt="Image" 
src="https://github.com/user-attachments/assets/5788ecee-c891-4d1c-a5e7-931be4bbd75a";
 />
   
   <img width="1013" height="55" alt="Image" 
src="https://github.com/user-attachments/assets/7f17bccd-0542-41fc-8c01-1f4448fc75a8";
 />
   
   However, when an instance is created without specifying a controller, the 
guest OS actually sees a SCSI controller, even though the instance details 
still show `ide`.
   
   <img width="717" height="161" alt="Image" 
src="https://github.com/user-attachments/assets/c8f1310a-380a-4944-a2da-85b7f44e537b";
 />
   
   On the other hand, when resizing a volume, the workflow appears to prefer 
`ide`, and that always fails claiming `ide` is not supported.
   
   <img width="446" height="339" alt="Image" 
src="https://github.com/user-attachments/assets/fd815035-614d-4891-9fe4-0b907a083713";
 />
   
   Looking at the code, it first checks for `scsi`, then for `ide`, and falls 
back to `osdefault` otherwise. That makes it look like `scsi` or `osdefault` is 
the effective default. In another part of the code, it even explicitly returns 
`scsi` as the default.
   
   <img width="1211" height="258" alt="Image" 
src="https://github.com/user-attachments/assets/9d0554f2-8c4b-4dcc-8fde-5920105ef659";
 />
   
   <img width="718" height="174" alt="Image" 
src="https://github.com/user-attachments/assets/47195b93-de4f-4447-ae48-01472e3c5b6f";
 />
   
   So at this point I am unsure what the intended or recommended default 
actually is, but it seems clear that using `ide` does not work in my tests.


-- 
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]

Reply via email to