[Bug 1723927] Re: Linux or windows guest boot failed by uefi on CPU of Intel Xeon X5675

2020-08-12 Thread Laszlo Ersek (Red Hat)
Closing due to almost 3 years of inactivity. ** Changed in: qemu Status: New => Invalid -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1723927 Title: Linux or windows guest boot failed by

[Qemu-devel] [Bug 1723927] Re: Linux or windows guest boot failed by uefi on CPU of Intel Xeon X5675

2017-10-17 Thread Laszlo Ersek (Red Hat)
"-bios /usr/share/qemu-kvm/OVMF_CODE.fd" is *never* a correct option to boot OVMF. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1723927 Title: Linux or windows guest boot failed by uefi on CPU

[Qemu-devel] [Bug 1723927] Re: Linux or windows guest boot failed by uefi on CPU of Intel Xeon X5675

2017-10-16 Thread chan
I success to capture the OVMF debug log. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1723927 Title: Linux or windows guest boot failed by uefi on CPU of Intel Xeon X5675 Status in QEMU:

[Qemu-devel] [Bug 1723927] Re: Linux or windows guest boot failed by uefi on CPU of Intel Xeon X5675

2017-10-16 Thread chan
Ersek, thank you very much! I set up correctly in "/etc/libvirt/qemu.conf", so command -bios /usr/share/qemu-kvm/OVMF_CODE.fd also boot UEFI guest. Current, my question only in the platform in server of ProLiant BL460c G7, the same ovmf firmware. How can capture the OVMF debug log? I use your