You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
VM cannot run normally in kvm UEFI LEGACY mode #4245
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
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.
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
1.Deploy VM through template, boot type select UEFI.Boot Mode select LEGACY
2.After the VM runs successfully, open the console
EXPECTED RESULTS
The console displays guest OS information, or UEFI shell.
Activity
DaanHoogland commentedon Aug 5, 2020
@div8cn do you have resources to work on this?
should we set a milestone yet?
div8cn commentedon Aug 5, 2020
I have resources to provide testing
@DaanHoogland
DaanHoogland commentedon Aug 5, 2020
ok, we might have to postpone to 4.16 than as development work will be required i guess
yadvr commentedon Dec 14, 2020
@DaanHoogland can you triage and advise if this is a bug or config issue, we can ask @Spaceman1984 to look into this
kvm: Use Q35 chipset for UEFI x86_64 (#4576)
yadvr commentedon Feb 1, 2021
Fixed in #4576