All of lore.kernel.org
 help / color / mirror / Atom feed
* qemu/kvm tianocore restart stuck
@ 2021-04-22 20:04 VoidCC
  2021-04-23  9:51 ` Philippe Mathieu-Daudé
  2021-04-23 10:30 ` Laszlo Ersek
  0 siblings, 2 replies; 3+ messages in thread
From: VoidCC @ 2021-04-22 20:04 UTC (permalink / raw)
  To: qemu-devel; +Cc: Laszlo Ersek

[-- Attachment #1: Type: text/plain, Size: 922 bytes --]

Hello,

I'm hitting a hard wall with qemu and efi.
I'm running multiple windows server 2019 vms which usually reboot on
updates.

The issue is, efi breaks on reboot.
It randomly(race condition?, does not occur consistently) ends up in a
blackscreen: no bootloader, no efi screen and the only way to get out of
that state is to destroy the vm.
moving the host mouse cursor above the console in virt-manager results in a
flashing mouse cursor.
there are no physical devices attached and there is currently no virtio
attachment in use (os has virtio drivers installed)


Machine is Q35 with tianocore/ovmf efi.
I managed to reproduce the same behaviour on rhel 8.3 as well as
voidlinux (kernel 5.11)

gdb output of qemu is showing nothing worrisome, else ive compiled ovmf
manually for debug output.
libvirt logs don't show any issues.

root · Slexy.org Pastebin <https://slexy.org/view/s2w8CdNBx5>

[-- Attachment #2: Type: text/html, Size: 1176 bytes --]

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: qemu/kvm tianocore restart stuck
  2021-04-22 20:04 qemu/kvm tianocore restart stuck VoidCC
@ 2021-04-23  9:51 ` Philippe Mathieu-Daudé
  2021-04-23 10:30 ` Laszlo Ersek
  1 sibling, 0 replies; 3+ messages in thread
From: Philippe Mathieu-Daudé @ 2021-04-23  9:51 UTC (permalink / raw)
  To: VoidCC, qemu-devel; +Cc: Laszlo Ersek

On 4/22/21 10:04 PM, VoidCC wrote:
> Hello,
> 
> I'm hitting a hard wall with qemu and efi.
> I'm running multiple windows server 2019 vms which usually reboot on
> updates.
> 
> The issue is, efi breaks on reboot.
> It randomly(race condition?, does not occur consistently) ends up in a
> blackscreen: no bootloader, no efi screen and the only way to get out of
> that state is to destroy the vm.
> moving the host mouse cursor above the console in virt-manager results
> in a flashing mouse cursor.
> there are no physical devices attached and there is currently no virtio
> attachment in use (os has virtio drivers installed)
> 
> 
> Machine is Q35 with tianocore/ovmf efi.
> I managed to reproduce the same behaviour on rhel 8.3 as well as
> voidlinux (kernel 5.11)
> 
> gdb output of qemu is showing nothing worrisome, else ive compiled ovmf
> manually for debug output.
> libvirt logs don't show any issues.
> 
> root · Slexy.org Pastebin <https://slexy.org/view/s2w8CdNBx5>

I tried to help you yesterday on IRC mentioning SMM / EPT
but then you didn't reply. See:
https://bugzilla.redhat.com/show_bug.cgi?id=1348092#c24

Regards,

Phil.



^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: qemu/kvm tianocore restart stuck
  2021-04-22 20:04 qemu/kvm tianocore restart stuck VoidCC
  2021-04-23  9:51 ` Philippe Mathieu-Daudé
@ 2021-04-23 10:30 ` Laszlo Ersek
  1 sibling, 0 replies; 3+ messages in thread
From: Laszlo Ersek @ 2021-04-23 10:30 UTC (permalink / raw)
  To: VoidCC, qemu-devel

On 04/22/21 22:04, VoidCC wrote:
> Hello,
> 
> I'm hitting a hard wall with qemu and efi.
> I'm running multiple windows server 2019 vms which usually reboot on
> updates.
> 
> The issue is, efi breaks on reboot.
> It randomly(race condition?, does not occur consistently) ends up in a
> blackscreen: no bootloader, no efi screen and the only way to get out of
> that state is to destroy the vm.
> moving the host mouse cursor above the console in virt-manager results in a
> flashing mouse cursor.
> there are no physical devices attached and there is currently no virtio
> attachment in use (os has virtio drivers installed)
> 
> 
> Machine is Q35 with tianocore/ovmf efi.
> I managed to reproduce the same behaviour on rhel 8.3 as well as
> voidlinux (kernel 5.11)
> 
> gdb output of qemu is showing nothing worrisome, else ive compiled ovmf
> manually for debug output.
> libvirt logs don't show any issues.
> 
> root · Slexy.org Pastebin <https://slexy.org/view/s2w8CdNBx5>
> 

Please capture the firmware debug log. It's possible that you have
rebooted the VM many times, and the variable store got fragmented, at
the "Fault Tolerant Write" level. During one of these boots, an FTW
"reclaim" (a kind of "defrag") may run, and that's time consuming, if
you're not used to it. The firmware log could help. See the
OvmfPkg/README file for QEMU command line options, for capturing the
OVMF debug log.

Please include your QEMU command lines too, in the issue report.

Thanks
Laszlo



^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2021-04-23 10:31 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-04-22 20:04 qemu/kvm tianocore restart stuck VoidCC
2021-04-23  9:51 ` Philippe Mathieu-Daudé
2021-04-23 10:30 ` Laszlo Ersek

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.