kricud opened a new issue #5932:
URL: https://github.com/apache/cloudstack/issues/5932


   <!--
   Verify first that your issue/request is not already reported on GitHub.
   Also test if the latest release and main branch are affected too.
   Always add information AFTER of these HTML comments, but no need to delete 
the comments.
   -->
   
   ##### ISSUE TYPE
   <!-- Pick one below and delete the rest -->
    * Bug Report
   
   ##### COMPONENT NAME
   <!--
   Categorize the issue, e.g. API, VR, VPN, UI, etc.
   -->
   ~~~
   ACS
   ~~~
   
   ##### CLOUDSTACK VERSION
   <!--
   New line separated list of affected versions, commit ID for issues on main 
branch.
   -->
   
   ~~~
   4.15.2.0
   ~~~
   
   ##### CONFIGURATION
   <!--
   Information about the configuration if relevant, e.g. basic network, 
advanced networking, etc.  N/A otherwise
   -->
   
   
   ##### OS / ENVIRONMENT
   <!--
   Information about the environment if relevant, N/A otherwise
   -->
   ESXi 6.7 and Windows
   
   ##### SUMMARY
   <!-- Explain the problem/feature briefly -->
   
   
   ##### STEPS TO REPRODUCE
   <!--
   For bugs, show exactly how to reproduce the problem, using a minimal 
test-case. Use Screenshots if accurate.
   
   For new features, show how the feature would be used.
   -->
   
   **UEFI/SECURE works in general:**
   Create new instance with UEFI/SECURE
   
![image](https://user-images.githubusercontent.com/30048481/152498235-7112ed7e-a24e-4f17-a917-300f85017a11.png)
   
   Works us expected
   
![image](https://user-images.githubusercontent.com/30048481/152498260-a22f782d-f917-4929-a8a5-49ef75147de3.png)
   
   **Problem with template prepared for UEFI/SECURE:**
   Upload ova template that has been created to boot with UEFI/SECURE
   
![image](https://user-images.githubusercontent.com/30048481/152498321-1f12ff95-dc71-42b4-ace9-b9082cf25ff3.png)
   
   Edit template settings to add support for UEFI/SECURE boot
   
![image](https://user-images.githubusercontent.com/30048481/152498374-18d6600f-4a57-496f-af6a-86af138f0bde.png)
   
   Create instance from template
   (Advanced settings are not used from template)
   
![image](https://user-images.githubusercontent.com/30048481/152498411-2be2c4c7-eee9-4ac2-b287-3bb63a840d0b.png)
   
   Deployed instance contains settings for UEFI/SECURE
   
![image](https://user-images.githubusercontent.com/30048481/152498451-080d141c-1534-47f7-96fe-dea12ec8bd65.png)
   
   Hypervisor settings are for BIOS – VM will not boot as its prepared for 
UEFI/SECURE boot.
   
![image](https://user-images.githubusercontent.com/30048481/152498488-053cbc55-9039-41dc-a0b1-f959a8f08441.png)
   
   **Workaround is to “Read VM settings from OVA”**
   With this approach end user cannot edit settings as they are controlled by 
OVA. I think that its correct behavior as “Read VM settings from OVA” where 
implemented for appliances that could contain some not standard things.
   
![image](https://user-images.githubusercontent.com/30048481/152498518-67ef14bd-e5fa-4ebf-8649-80ad9b8b256e.png)
   
![image](https://user-images.githubusercontent.com/30048481/152498521-f8953c05-fa84-4842-80e3-5c1bf6fa1cea.png)
   
![image](https://user-images.githubusercontent.com/30048481/152498530-037ee0bb-c89a-4b7f-8f34-d24770c2a8d8.png)
   
   
   <!-- Paste example playbooks or commands between quotes below -->
   ~~~
   
   ~~~
   
   <!-- You can also paste gist.github.com links for larger files -->
   
   ##### EXPECTED RESULTS
   <!-- What did you expect to happen when running the steps above? -->
   
   ~~~
   Instance created from template with UEFI/SECURE boots
   ~~~
   
   ##### ACTUAL RESULTS
   <!-- What actually happened? -->
   
   <!-- Paste verbatim command output between quotes below -->
   ~~~
   Instance is not booting as its configured for BIOS/Legacy boot
   ~~~
   


-- 
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: commits-unsubscr...@cloudstack.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


Reply via email to