div8cn opened a new issue #4245:
URL: https://github.com/apache/cloudstack/issues/4245


   <!--
   Verify first that your issue/request is not already reported on GitHub.
   Also test if the latest release and master 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.
   -->
   ~~~
   KVM 
   UEFI
   ~~~
   
   ##### CLOUDSTACK VERSION
   <!--
   New line separated list of affected versions, commit ID for issues on master 
branch.
   -->
   
   ~~~
   4.14.0.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
   -->
   Hypervisor:  CentOS7.6
   Compiled against library: libvirt 4.5.0
   Using library: libvirt 4.5.0
   Using API: QEMU 4.5.0
   Running hypervisor: QEMU 2.12.0
   
   OVMF: OVMF-20180508-6.gitee3198e672e2.el7.noarch
   
   ##### SUMMARY
   <!-- Explain the problem/feature briefly -->
   
   
   Under KVM Hypervisor
   In UEFI LEGACY mode, the VM cannot enter the system normally, and "Guest has 
not initialized the display (yet)." is displayed in the console.
   
   
![image](https://raw.githubusercontent.com/div8cn/image/master/202008/centos7-kvm-uefi-1.png)
   VM starts normally in UEFI Secure mode
   
   
   After comparison, we found that:
   **In UEFI LEGACY mode, the VM uses pc-i440f chip,**
   **In UEFI Secure mode, the Q35 chip is used.**
   
   
   After I switched the VM chip from pc-i440fx-rhel7.6.0 to pc-q35-rhel7.6.0 
(manually modify the configuration file), the VM can enter the system normally.
   
   **so. UEFI under CentOS7 should run under Q35 chip (UEFI LEGACY AND UEFI 
SECURE)**
   
   ##### 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.
   -->
   
   <!-- Paste example playbooks or commands between quotes below -->
   ~~~
   1.Deploy VM through template, boot type select UEFI.Boot Mode select LEGACY 
   2.After the VM runs successfully, open the console
   
   ~~~
   
   <!-- You can also paste gist.github.com links for larger files -->
   
   ##### EXPECTED RESULTS
   <!-- What did you expect to happen when running the steps above? -->
   
   ~~~
   The console displays guest OS information, or UEFI shell.
   ~~~
   
   ##### ACTUAL RESULTS
   <!-- What actually happened? -->
   
   <!-- Paste verbatim command output between quotes below -->
   ~~~
   Guest has not initialized the display (yet).
   ~~~
   


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

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to